Healthcare & Wellness

Verified against ChatGPT · 2026-08-12

Write a patient FAQ for one specific procedure that answers the anxious questions, not just the logistical ones

Drafts a patient-facing FAQ for a specific procedure or visit type that covers the practical logistics and the quieter worry-driven questions patients don't always ask out loud, framed as a draft requiring clinical sign-off before publishing.

ChatGPT (GPT-5.1)5 fillable variables
Scope for this category: Organizational, educational and communication support only — no diagnosis, treatment recommendation, or medication guidance. Every prompt states plainly that a qualified clinician must review anything before it is acted on.

The prompt

Ready to copy — highlighted parts are example details you can swap.

You are drafting a patient FAQ page for one specific procedure or visit type offered by a practice. Patients reading this are often anxious, not just looking for logistics.

PROCEDURE OR VISIT TYPE
Outpatient colonoscopy under sedation.

WHAT PATIENTS TYPICALLY ASK THE FRONT DESK
How long is the prep, can I drive myself home, how long until I get results.

WHAT THE PRACTICE WANTS TO REASSURE PATIENTS ABOUT
Sedation means most patients don't remember the procedure itself; a nurse checks in throughout recovery before discharge.

PRACTICAL LOGISTICS
Prep starts the evening before, procedure itself takes 20-30 minutes, plan for 2-3 hours total at the facility including recovery.

QUESTIONS THIS FAQ SHOULD EXPLICITLY NOT ANSWER
Whether a specific medication needs to be paused beforehand — that's patient-specific and handled during the pre-procedure call.

RULES
Write two tiers of questions: the logistical ones patients ask out loud (how long does it take, what should I wear, can someone drive me) and the quieter ones patients often don't ask directly but are clearly worried about (will it hurt, what if something goes wrong, how will I know if I need to come back sooner) — infer the second tier from what's anxiety-adjacent to this specific procedure, don't just list generic FAQ filler. Answer each question in plain, calm language without minimizing real discomfort or risk — "most patients describe mild discomfort, not pain" is honest; "it's completely painless" is not, unless that's actually and specifically true for this procedure. For any question that would require a specific clinical judgment about an individual patient's situation (their own risk factors, what a symptom they're describing means, whether they personally should proceed), write the answer as "this depends on your specific situation — ask your care team at your visit" rather than attempting a general answer that could be wrong for someone with an atypical case. Leave the explicitly out-of-scope questions off the page entirely rather than answering them badly.

WHAT NOT TO DO
Do not state a specific complication rate, success rate, or recovery timeline as a hard number unless it was given to you above — write "ask your provider about the expected timeline for your case" instead of inventing a plausible-sounding average.

MANDATORY DISCLAIMER
Add a closing line on the FAQ page stating that this page is general information, not personalized medical advice, and that any question about a patient's own symptoms, risks, or readiness for the procedure should be directed to their care team — and open the draft to the practice with a note that clinical staff must review and approve every answer before this goes live.

OUTPUT FORMAT
1. A one-line note to the practice: "clinical review required before publishing."
2. Logistics questions and answers.
3. Anxiety-driven questions and answers.
4. The closing patient-facing disclaimer line, written exactly as it should appear on the page.

Customize

Optional — swap in your own details for the highlighted parts above.

Why this works

Most procedure FAQs are written entirely around logistics because that's what front-desk staff actually get asked, but the questions a patient is silently anxious about rarely get voiced to a receptionist and never make it into the source material — asking the model to explicitly infer a second tier of anxiety-adjacent questions specific to this procedure, rather than pulling from a generic FAQ template, produces content that addresses what's actually keeping someone up the night before, which is where a lot of patient FAQ pages fall short. The instruction against minimizing real discomfort ("most patients describe mild discomfort" versus a blanket "painless") matters because overpromising comfort is a specific, common failure in patient-facing healthcare copy that erodes trust the moment a patient's actual experience doesn't match the page, and it's also the kind of overclaim that shouldn't be published without clinical sign-off in the first place. Routing any question that depends on individual risk factors to "ask your care team" rather than attempting a general answer prevents the page from accidentally functioning as personalized medical advice — a FAQ page is read by people with wildly different health histories, and a generically correct answer for a typical patient can be actively wrong for someone with an atypical one. The ban on inventing specific complication or success rates addresses a distinct risk: a fluent model asked to write reassuring healthcare copy will sometimes produce a plausible-sounding statistic to round out an answer, and a fabricated number on a real clinical FAQ page is a credibility and safety problem, not just a stylistic one. The clinical-review note at the top exists because this is a draft for a real publishing workflow, and it should never reach a patient before someone with clinical authority has checked every answer against how the practice actually performs the procedure.

What you get back

Clinical review required before publishing. Q: Will the procedure hurt? A: Most patients under sedation don't recall the procedure at all; some describe mild bloating afterward from the air used during the exam, not pain. Q: What if I have questions about my own risk given my health history? A: That depends on your specific situation — please raise it with your care team at your pre-procedure appointment.

Verified against

ChatGPT GPT-5.1 · 2026-08-12

Changelog

  • 2026-08-12 Initial publish, verified against ChatGPT GPT-5.1.

Need this built into your business?

If a prompt isn't enough — what Scult builds, built and maintained for you — that's Scult's day job.

EXPLORE WHAT SCULT BUILDS
All Healthcare & Wellness prompts

Check your AI visibility

One URL in, a 0–100 score and the exact fixes out.

RUN THE CHECK

Browse all the tools

15 tools across six categories
13 of them never send your data anywhere

Free · No signup · No trial clock

SEE THE DIRECTORY