LoginGet started

Healthcare communication templates

Clinically Appropriate Thank-You Notes for Patients, Donors & Staff

A library of scenario-based templates, tone presets, and prompt patterns you can adapt for email, patient portal messages, SMS, printed postcards, and donor acknowledgements. Designed to reduce clinician drafting time, avoid PHI in reusable templates, and support plain-language and bilingual variants.

Browse TemplatesSee Pricing

Ready-to-use examples

Templates organized by clinical scenario

Use these scenario templates as a starting point. Each includes subject and preheader suggestions for email, recommended placeholders to avoid embedding PHI in the template, and channel-specific guidance for portal messages, postcards, and SMS.

Post-discharge follow-up (email)

Three-paragraph thank-you email that balances reassurance and next-step reminders.

  • Prompt pattern: "Write a 3-paragraph thank-you email to [PatientFirstName] after discharge from [UnitName] on [DischargeDate]. Tone: compassionate. Include: reason to call if symptoms return, next appointment placeholder [NextAppointmentDate], clinician sign-off [ClinicianName]. Keep clinical details generic—do not include PHI."
  • Subject suggestion: "Thank you for your care at [HospitalName] — next steps"
  • Use the template in secure patient portals or EHR messaging; store only as a reusable template with placeholders

Surgery thank-you (postcard)

Handwritten-style short note for mailed postcards or printed discharge packets.

  • Prompt pattern: "Compose a short, 40–60 word handwritten-style thank-you for a postcard to a patient who had [ProcedureType]. Tone: warm, mention follow-up placeholder [FollowUpDate], sign with clinician's first name. Avoid medical specifics."
  • Keep language plain and avoid condition names; suitable for patients with low literacy

Telehealth visit (portal message)

Concise portal note with next steps as simple bullet points.

  • Prompt pattern: "Generate a concise portal message thanking [PatientFirstName] for their telehealth visit with [ClinicianName]. Include next steps in bullet form (meds, tests, referrals) as placeholders, and a plain-language sentence about how to reach the clinic for urgent concerns."
  • Use short bullets and link to patient resources rather than including test results in the message

Donor acknowledgement (email)

Grateful, specific acknowledgement for fundraising and development communications.

  • Prompt pattern: "Draft a heartfelt acknowledgement to an individual donor who supported [ProgramName]. Tone: grateful and specific about program impact without medical promises. Include tax-letter sentence placeholder and invitation to an upcoming donor event."
  • Include suggested language for tax receipts and non-promissory descriptions of program impact

Referring physician (professional email)

Concise, collegial message for referring clinicians with an offer to coordinate care.

  • Prompt pattern: "Write a short professional thank-you to Dr. [ReferringLastName] for referring [PatientFirstName]. Include appreciation, a one-line summary of service provided (non-diagnostic), and an offer to coordinate follow-up. Tone: collegial and concise."
  • Avoid diagnostic detail and patient identifiers in templates; use placeholders for coordination steps

Staff recognition (internal)

Short internal notes and newsletter headlines to recognize behaviour and impact.

  • Prompt pattern: "Create a 2–3 sentence recognition note for a nurse who led a successful discharge improvement. Tone: appreciative and specific about the behavior. Provide a short headline suitable for an internal newsletter."
  • Include a one-line impact statement and suggested approval workflow before publishing internally

Volunteer appreciation (letter)

Longer-format letter for long-term volunteers with anecdote and invitation details.

  • Prompt pattern: "Compose a thank-you letter to a long-term volunteer, include mention of years of service placeholder, a highlighted anecdote placeholder, and an invitation to a volunteer appreciation event. Tone: warm and community-focused."
  • Use non-clinical language and ask permission before sharing volunteer anecdotes publicly

Lab/diagnostic (SMS-safe)

Short SMS confirming sample receipt or appointment details without PHI.

  • Prompt pattern: "Write an SMS-safe thank-you after a lab draw: 160 characters max, confirm sample received, include follow-up portal link placeholder, and a line noting to contact patient services if questions. No clinical results or PHI in the message."
  • Example constraint: Keep under 160 characters and avoid results or identifiers

Mental health follow-up (sensitive tone)

Compassionate messages with crisis resources and extra review flags.

  • Prompt pattern: "Generate a compassionate follow-up message thanking the patient for attending therapy, include brief self-care resource placeholders, crisis contact instructions if needed, and a note to contact the clinic to reschedule. Flag for additional review when messaging high-risk patients."
  • Recommend clinical leadership review and explicit escalation processes for high-risk notes

Bilingual Spanish variant

Plain-language Spanish version and subject line suggestions.

  • Prompt pattern: "Provide a Spanish version of this thank-you: [Insert English note]. Keep tone and length consistent; use plain language and culturally appropriate phrasing. Add a short subject line and a Spanish signature line."
  • Include a brief translator note and check local language preferences before sending

Safe wording patterns

Tone presets, placeholders, and PHI safety

Choose a tone preset and use standardized placeholders to keep templates reusable and free of PHI. Store only template shells; merge patient-specific fields at send time using the EHR or CRM's secure merge fields.

  • Tone presets: Clinical (concise, professional), Compassionate (warm, empathetic), Administrative (brief, action-oriented)
  • Safe placeholders: [PatientFirstName], [VisitDate], [ClinicianName], [UnitName], [NextStep], [FollowUpDate], [ProgramName]. Avoid direct identifiers like MRN or specific diagnosis in templates.
  • PHI guidance: Never keep PHI in reusable templates. Use secure merge fields at send-time and limit access to approved users.

Format guidance for email, portal, SMS, and printed mail

Channel-ready variants

Different channels require different lengths and content rules. Use the same template family but adapt tone, length, and privacy content per channel.

  • Email: Subject + preheader + 1–3 short paragraphs. Include links to portal resources rather than inserting results.
  • Patient portal: Short, direct messages with clear next steps and contact instructions; portal is preferred for protected information.
  • SMS: 160 characters max, do not include test results or PHI; include a portal link and clear contact number.
  • Print/postcard: Keep language warm and non-clinical; use handwritten-style lines for personal feel and avoid clinical jargon.

Make notes easy to read

Accessibility, plain language & translation

Write at an 8th-grade reading level, use active voice, short sentences, and one action per sentence. Provide translation prompts and cultural guidance for bilingual variants.

  • Plain-language rewrite pattern: remove jargon, replace multi-syllable words with common alternatives, provide one clear next step (e.g., "Call [PhoneNumber] if symptoms return").
  • Formatting tips: use bullets for next steps, bold or highlight appointment dates, and include a short phone line for questions.
  • Translation prompt: "Translate to Spanish keeping tone and length; use plain language and culturally appropriate phrasing." Always verify translations with a medical translator when possible.

Workflow guidance

Governance & approvals

Establish a lightweight approval workflow for templates before they are published in EHR, CRM, or volunteer systems.

  • Recommended approvers: clinical leadership, legal/compliance (for donor wording and regulatory disclaimers), and patient-experience teams.
  • Version control: label templates with version and owner, include 'last reviewed by' date, and archive superseded templates.
  • Consent & preferences: check messaging consent recorded in the EHR or CRM before sending patient-facing notes.

How to use the prompt library

Prompt patterns for rapid customization

Use the included prompt clusters to generate short, medium, and long variants of each scenario. Each pattern contains placeholders and sending constraints to preserve privacy and appropriateness.

  • Template personalization pattern: Provide three length variants (short, medium, long) with subject line and preheader for email; include placeholders: [PatientFirstName], [VisitDate], [ClinicianName], [NextStep].
  • Accessibility rewrite pattern: "Rewrite this thank-you note to 8th-grade reading level, remove jargon, use active voice, and include one short sentence explaining next steps."
  • Deployment note: keep prompt patterns and example outputs in a central team library so staff can copy approved wording without draft changes.

FAQ

Is it safe to use templates that include patient identifiers?

No—reusable templates should not include patient identifiers. Use standardized placeholders (e.g., [PatientFirstName], [VisitDate]) in templates and let the EHR or CRM insert PHI at send time. Limit template editing permissions and document an approval workflow to prevent accidental PHI in shared templates.

When is the best time to send a thank-you message after discharge or a visit?

Timing depends on the scenario: a post-discharge check-in is typically sent within 24–72 hours; a donor acknowledgement should be sent promptly after a gift is processed; referring-physician thanks can be sent within a few days to maintain collegial coordination. Align timing with clinical workflows and patient communication preferences recorded in the EHR.

How do I choose tone and length for patients vs. referring physicians vs. donors?

Use compassionate, plain-language messages for patients with clear next steps. For referring physicians, keep tone professional and concise with coordination offers. For donors, use grateful and specific language about program impact without making medical promises. Provide short, medium, and long variants so senders can choose based on channel and audience.

What wording is appropriate for sensitive situations (serious diagnosis, bereavement, mental health)?

For sensitive situations, use a restrained, empathetic tone and avoid clinical detail in templates. Include crisis contacts and escalation instructions where relevant. Always route messages through clinical leadership and legal/compliance for review, and consider an individualized, clinician-signed note rather than a template for bereavement or high-risk cases.

Can these notes be used for SMS and what must be avoided?

Yes, but SMS messages must be concise (ideally ≤160 characters) and must not include PHI or clinical results. Use SMS to confirm receipt, give appointment reminders, or link to secure portal pages for private information. Verify consent for text messaging before sending.

How should templates be localized and translated for non-English-speaking patients?

Create culturally appropriate translations using medical translators when possible. Use plain-language prompts for automated translations and then have native-speaking staff review. Store language preferences in patient records and select the correct template variant at send-time.

How do we record consent for messaging and respect patient communication preferences?

Record and check communication consents in the EHR or CRM before sending. Build templates and send flows that respect opt-out preferences and default to secure patient-portal messaging for protected information.

What are plain-language and accessibility best practices for patient-facing thank-you notes?

Write at an 8th-grade level, use short sentences, active voice, and one clear next step. Use bullets for actions, avoid jargon and acronyms, and include contact options (phone and portal link). Ensure sufficient contrast and readable fonts for printed materials.

How can we scale personalization without manually editing each note?

Use placeholders and secure merge fields from the EHR or CRM to insert patient-specific values at send-time. Maintain a central library of approved templates and teach staff how to select the appropriate template variant for channel and audience.

Who should approve templates: clinical leadership, legal/compliance, and patient-experience teams?

Yes—establish a cross-functional approval process that includes clinical leadership for medical appropriateness, legal/compliance for regulatory and donor wording, and patient-experience for tone and plain language.

Are there examples for donor acknowledgements that meet nonprofit acknowledgment rules?

Provide donor acknowledgements that include the donor name placeholder, gift date, program supported, and a tax receipt sentence placeholder. Avoid guaranteeing outcomes or medical benefits; include contact details for the development office and a link to the gift receipt.

What is a safe approach for bereavement or condolence messages from a clinical team?

Bereavement messages should be brief, compassionate, and come from an identified clinician or team member. Avoid clinical detail, offer practical next steps or support contacts, and route any templated condolence through clinical leadership and legal review. Consider handwritten or individualized notes rather than automated templates.

Related pages