Patient Education Handout
Specifying literacy level produces appropriately simplified content. The 'when to seek help' section with red flags is clinically important and often missing from generic handouts.
Create a patient education handout about {{condition_or_procedure}}. **Patient context:** - Health literacy level: {{literacy_level}} (e.g., "low — 6th grade reading level", "average", "high — medical professional") - Language considerations: {{language_notes}} (e.g., "plain English", "avoid idioms — ESL patient") - Specific questions the patient asked: {{patient_questions}} **Include:** 1. What it is (simple explanation) 2. What to expect (timeline, symptoms, recovery) 3. What to do (specific actions, medications, follow-up) 4. When to seek help (red flags that require immediate attention) 5. Common questions and answers **Format:** Short paragraphs, bullet points, no medical jargon unless defined. Maximum 1 page when printed. Note: This is a draft for review by the treating clinician before distribution to the patient.
Variables to customize
Why this prompt works
Specifying literacy level produces appropriately simplified content. The 'when to seek help' section with red flags is clinically important and often missing from generic handouts.
Save this prompt to your library
Organize, version, and access your best prompts across ChatGPT, Claude, and Cursor.
Related prompts
Providing the full schema and relationships eliminates guesswork. Asking for comments and assumption flags makes the output reviewable and trustworthy before running against production.
Data Cleaning ScriptRequiring before/after logging and a summary report turns a cleaning script into an auditable process. Flagging rows for manual review prevents silent data loss.
Visualization RecommendationStarting from the insight rather than the chart type ensures the visualization serves the story. Asking for common mistakes prevents the most frequent data viz errors.
Statistical Analysis GuideListing confounders and asking for assumption checks prevents the common mistake of running a test on data that violates its assumptions. The plain-English interpretation ensures you understand the results.