Contribute for: June 6th, 2025 | DBS: Is it right for me? - Jeremy Greenlee, MD | 2025 APDA Iowa PD Conference
— then share an AI result straight back, no copy-paste
- 1Send to Gemini
- 2Let it watch
- 3Paste it back
You are turning a Parkinson's-related YouTube video into a written summary that is useful for people living with the disease and their families.
Video URL: https://www.youtube.com/watch?v=CgE1dL94ST0
Video title: June 6th, 2025 | DBS: Is it right for me? - Jeremy Greenlee, MD | 2025 APDA Iowa PD Conference
Article ID: 7vvr41wx (keep verbatim in your response)
WATCH THE VIDEO
You can ingest YouTube URLs directly. Watch the video at the URL above before writing. If parts are unclear, lean on the visible captions / spoken audio rather than guessing.
WHO READS THIS
Patients and caregivers, not researchers. Explain what the speakers actually say — what is being recommended, what study or experience it draws on, what it means for daily life — so a layperson actually understands it. Translate jargon on first use. Keep the medicine sound, but never write to impress a clinician.
BE HONEST ABOUT EVIDENCE
Name the kind of claim — peer-reviewed trial, clinician opinion, patient testimony, advocacy organisation guidance, fundraising pitch — so the reader can calibrate hope. Say WHY a tip or finding might matter and on WHAT timeline. Don't invent specifics you didn't actually see or hear in the video; if part is unclear, say so rather than guessing. If the video is purely organisational (fundraiser, anniversary, leadership change with no patient impact), say so plainly in one short paragraph and don't inflate it.
PICK TOPICS FROM THE SITE TAXONOMY
The site is organised around long-running topic pages; each contribution adds NEW information to one or more of them. Topics are two levels: a top-level CATEGORY ("exercise") and an APPROACH under it ("exercise/aerobic-training" — the "/" separates parent from child).
The taxonomy is NOT included here — FETCH it before choosing topics:
https://health.poietic.studio/topics.txt (every category, each with its scope notes)
https://health.poietic.studio/topics.txt?category=<top-level-slug> (one category, e.g. ?category=nutriments)
Pick slugs only from what that page lists, after reading the scope of each candidate. Never copy a topic's scope text into your "title" or "new_info".
Choosing well:
- Be GENEROUS: file under every topic this video genuinely adds something new to (typically 2-6, up to 8 for cross-cutting talks). The test is "does it add something here?", not "is it the main subject?".
- Be SPECIFIC: always prefer the two-level "parent/approach" slug over the bare parent. Bare top-level slugs are fallback bins.
- Never list both a parent and one of its own children — pick the most specific.
- If the right approach isn't in the taxonomy but fits an existing category, ADD it as "<existing-parent>/<new-approach-slug>" with a short noun-phrase title (3-5 words) naming the approach in general (not this video). Never invent a new top-level category.
- "title" is copied verbatim from the taxonomy (or your new short title) — never the scope text. "new_info" says what THIS video adds: a recommendation, study cited, drug, exercise, patient experience. Never the scope text.
RELATIONS (optional)
List any connection this video actually evidences between two specific topics — one affecting, treating, worsening or depending on another. Both sides must be two-level approach slugs (mint one under the right parent if needed); a link between bare categories is too coarse — drop it. Each relation has two distinct slugs — never a topic with itself, never a parent with its own child. Skip the field or send [] if there's no real between-topic link; don't manufacture relations. Cap at 10.
Watch the video, then return ONE JSON object with exactly this shape — no surrounding prose, no markdown code fences:
{
"article_id": "7vvr41wx",
"summary": "2-3 short paragraphs in plain language. Explain what the video actually says — what is shown, what is recommended, what is claimed, who the speakers are — so a layperson understands it. Then say what this implies for someone living with Parkinson's: concrete consequences, what to discuss with a clinician, what hope or caution it justifies and on what timeline. Translate jargon on first use. Markdown allowed.",
"topics": [
{
"slug": "<one of the slugs above, copied verbatim — prefer the two-level form when it fits>",
"title": "<the short title from above, copied verbatim — NOT the scope text>",
"new_info": "1-3 sentences on what THIS specific video adds to that topic for a patient or caregiver. Reference the video's actual content (a recommendation, a study cited, a patient story, an exercise demonstrated, a drug discussed). NEVER a generic textbook definition, NEVER the scope text above. Markdown allowed."
}
],
"relations": [
{
"topics": ["<slug-a>", "<slug-b>"],
"claim": "ONE sentence (≤300 chars) on the connection.",
"snippet": "A short quote or close paraphrase (≤600 chars) from the video supporting the claim."
}
]
}
Rules:
- Write everything in English; readers translate in-browser.
- New slugs are lowercase kebab-case, always "<existing-parent>/<approach>" under a parent the taxonomy lists — never a freshly invented top-level category.
- Keep the JSON valid. For inline quoting or emphasis in prose, use single quotes ('like this'), NOT double quotes — unescaped double quotes inside string values break the parser. Do not wrap in code fences. Return only the JSON.
Let the AI do the writing. Follow the steps and submit its output as-is — please don't edit it. Step in only to help it along: if it reports an error, paste that error back and ask it to fix it; if a page is paywalled or blocks bots, fetch the PDF yourself and give it to the assistant.