Email campaigns
AuraScore 81/100

Rare Disease Patient Support Program Adherence Script

Develop an empathetic, HIPAA-compliant patient onboarding and therapy adherence email script sequence for specialty pharmaceuticals.

Use this template when designing a digital companion program for patients initiating high-complexity specialty treatments. It guides patients through specialty pharmacy coordination, injection training, copay assistance, and nurse navigator access while maintaining strict privacy standards.

Template

Role: Lead Healthcare Patient Experience Strategist and Specialty Brand Lifecycle Architect.

Context

  • Disease indication: {{indication_name}}
  • Mode of administration: {{therapy_administration_mode}}
  • Specialty pharmacy network: {{specialty_pharmacy_partner}}
  • Clinical support team: {{nurse_support_channel}}
  • First adherence milestone: {{adherence_milestone_days}}
  • Safety and adverse event pathway: {{adverse_event_reporting_protocol}}

Task

Draft a compassionate, health-literacy-optimized 4-part email onboarding journey script for newly prescribed patients, driving persistence, mitigating anxiety, and coordinating logistical hurdles without providing unapproved medical advice.

Method

  1. Establish a reading grade level (6th–8th grade) suitable for health literacy standards across all communications.
  2. Script Module 1 (Welcome & Specialty Pharmacy Navigation): De-mystify initial shipment logistics, cold-chain handling, and outreach from {{specialty_pharmacy_partner}}.
  3. Script Module 2 (Preparation & Administration Guidance): Explain administration logistics for {{therapy_administration_mode}}, introducing injection/infusion planning guides and nurse support via {{nurse_support_channel}}.
  4. Script Module 3 (Financial & Copay Support): Break down foundational access resources, copay card activation, and foundation assistance workflows.
  5. Script Module 4 (The Milestone Check-In): Celebrate reaching {{adherence_milestone_days}} on therapy, prompting refill schedules and ongoing lifestyle integration.
  6. Embed mandatory FDA-compliant Fair Balance and Black Box warnings (where applicable) alongside {{adverse_event_reporting_protocol}} across every module.
  7. Craft distinct callout boxes for caregivers and family support networks in Modules 1 and 2.
  8. Include precise opt-out mechanisms, caregiver proxy verification rules, and secure portal links.

Constraints

  • MUST be fully compliant with HIPAA privacy rules and contain zero protected health information (PHI) in subject lines.
  • MUST NOT provide individual diagnosis, dose adjustment recommendations, or symptomatic medical counsel.
  • Every script must clearly present {{adverse_event_reporting_protocol}} in an accessible footer.
  • Tone must remain empathetic, empowering, and accessible while strictly adhering to regulatory guidelines.

Output format

  • Section 1: Patient Journey Milestones & Triggers (Day 0, Day 7, Day 14, Day {{adherence_milestone_days}})
  • Section 2: Module 1 Script (Welcome & Pharmacy Fulfillment Coordination)
  • Section 3: Module 2 Script (Administration Preparedness & {{nurse_support_channel}} Access)
  • Section 4: Module 3 Script (Co-Pay Navigation & Access Optimization)
  • Section 5: Module 4 Script (Milestone Celebration & Habit Formation)
  • Section 6: Standardized Safety, Fair Balance, and Adverse Event Reporting Copy Block

Self-review

  • Ensure subject lines do not disclose specific diagnostic or clinical conditions (HIPAA de-identification standard).
  • Verify that {{adverse_event_reporting_protocol}} is prominently displayed and instructions are unmistakable.
  • Check that the language throughout is tuned to an accessible 6th–8th grade reading level.
AuraScore breakdown
81/100Provisional
Instruction clarity15/15 · Strong

Explicit role, a named task, and discrete steps the model can follow.

Context architecture12/12 · Strong

Background, inputs and variables the model needs before it starts.

Constraint engineering12/12 · Strong

Hard boundaries — what the model must and must not do.

Output specification6/14 · Thin

A named, field-level shape for the response.

Reasoning structure10/10 · Strong

Ordered work items that force analysis before an answer.

Model compatibility10/10 · Strong

Length and structure that travel across frontier models.

Token efficiency5/10 · Thin

Signal density — instruction weight without padding.

Reusability7/7 · Strong

Documented variables so the scaffold adapts to new inputs.

Robustness3/5 · Adequate

Quality bar, assumptions and behaviour when inputs are thin.

Observed performance1/5 · Thin

How much real usage the template has behind it.

marketing
marketing-email-campaigns
healthcare-life-sciences
patient-support
rare-disease
adherence