Customers
AuraScore 83/100

Medical Device Urgent Safety Notice Customer Email Specification

Develop a regulatory-grade email communication spec for notifying hospital clients about medical device field safety corrective actions.

Use this template when drafting urgent email communication frameworks for hospital procurement heads and clinical users regarding medical device alerts or recalls. It establishes compliance, risk mitigation, and confirmation tracking workflows.

Template

Role: Principal Regulatory Communications Specialist in Medical Device Post-Market Surveillance.

Context

  • Medical device model: {{device_name}}
  • Risk classification and hazard details: {{hazard_description}}
  • Impacted production batches: {{affected_lot_numbers}}
  • Customer account segmentation: {{hospital_customer_tier}}
  • Required clinical containment actions: {{clinical_remediation_steps}}
  • Reporting window and regulatory authority: {{regulatory_filing_deadline}}

Task

Author a comprehensive email communication specification for hospital customers and clinical department heads that details immediate quarantine protocols, replacement logistics, and digital acknowledgement confirmation workflows for {{device_name}}.

Method

  1. Analyze {{hazard_description}} and map patient safety risks to clinical user operational workflows.
  2. Cross-reference {{affected_lot_numbers}} to establish clear identification guidelines in the email preheader and header.
  3. Formulate the primary message architecture, prioritizing immediate quarantine directives before technical explanations.
  4. Draft the step-by-step containment protocol adapting instructions to {{hospital_customer_tier}} operational structures.
  5. Design an auditable customer acknowledgment response mechanism that meets {{regulatory_filing_deadline}} audit standards.
  6. Specify contingency routing for non-responsive healthcare accounts to maintain audit-ready post-market vigilance.
  7. Detail inventory return, replacement dispatch, and credit reconciliation email instructions.
  8. Establish precise variable injection parameters and fallback values for automated CRM dispatch.

Constraints

  • Content MUST strictly align with ISO 13485 and FDA 21 CFR Part 806 communication guidelines.
  • Tone MUST balance urgent clinical caution with objective, non-alarmist clarity.
  • MUST NOT downplay hazard severity or use speculative language regarding patient health risks.
  • Email subject line options MUST NOT exceed 60 characters and must include the official recall classification.

Output format

Generate a structured specification document containing:

  1. Campaign Metadata & Trigger Configuration (table, max 6 rows)
  2. Email Subject Line & Header Architecture (3 prioritized variants)
  3. Core Email Wireframe & Modular Copy Spec (Section-by-section breakdown: Alert Banner, Hazard Brief, Immediate Actions, Logistics, Support)
  4. Digital Response & Traceability Mechanism (Field schema and response logic)
  5. Account Escalation Protocol (3-tier reminder cadence matrix)

Self-review

  • Ensure every clinical step in {{clinical_remediation_steps}} is explicitly translated into the customer email action block.
  • Verify that the acknowledgment call-to-action is unambiguous and trackable.
  • Confirm regulatory disclaimers and reporting compliance meet {{regulatory_filing_deadline}} demands.
AuraScore breakdown
83/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.

Robustness5/5 · Strong

Quality bar, assumptions and behaviour when inputs are thin.

Observed performance1/5 · Thin

How much real usage the template has behind it.

emails
emails-customers
healthcare-life-sciences
medical-devices
post-market-surveillance
customer-communications