Email campaigns
AuraScore 81/100

Medical Device Field Action Urgent Notification Dispatch Checklist

Verify regulatory compliance, auditable receipt tracking, and critical safety accuracy before dispatching medical device safety emails.

Use this checklist when drafting and executing Urgent Medical Device Corrections, Field Safety Notices (FSN), or Product Recalls via email to clinical facilities. It guarantees full traceability and adherence to post-market surveillance protocols.

Template

Role: Director of Life Sciences Regulatory Email Operations & Quality Assurance

Context

  • Medical Device Classification: {{device_classification}}
  • Field Action Severity: {{field_safety_event_type}}
  • Recipient Facility Matrix: {{recipient_facility_types}}
  • Regulatory Audit Trail Mandate: {{audit_trail_requirements}}
  • Acknowledgment SLA: {{mandatory_acknowledgment_window}}
  • Clinical Escalation Roster: {{escalation_contact_matrix}}

Task

Generate an emergency email deployment and verification checklist for broadcasting an urgent Field Safety Notice (FSN) to ensure flawless deliverability, immediate risk comprehension, rapid receipt verification, and zero compliance exposure.

Method

  1. Review the email header and subject line to ensure mandatory statutory hazard identifiers reflect {{field_safety_event_type}} without dilution.
  2. Confirm accurate inclusion of specific lot numbers, serial ranges, and UDI (Unique Device Identifier) fields for {{device_classification}}.
  3. Audit the explicit clinical risk disclosure, verifying immediate patient-safety instructions are visible above the fold.
  4. Check interactive digital receipt mechanisms (secure acknowledgment button and portal) against {{mandatory_acknowledgment_window}}.
  5. Verify that facility segmentation logic accurately targets all affected stakeholders across {{recipient_facility_types}} without omission.
  6. Audit failover logic for bounced, deferred, or unacknowledged notifications to trigger {{escalation_contact_matrix}}.
  7. Validate timestamp logging and recipient proof-of-delivery infrastructure against {{audit_trail_requirements}}.
  8. Verify that direct attachments (PDF FSN) match approved regulatory agency filings with intact checksums/signatures.

Constraints

  • Checkpoints MUST enforce zero marketing tracking scripts or non-essential third-party tracking pixels.
  • Checkpoints MUST NOT allow any ambiguous language regarding mandatory quarantine or remediation actions.
  • MUST verify 100% auditable logging for every delivered, opened, and acknowledged message.
  • MUST mandate immediate secondary escalation triggers when acknowledgments are overdue.

Output format

Return a comprehensive quality assurance checklist structured in 4 chronological phases:

  1. Phase 1: Payload Accuracy & Hazard Identification (4 checks)
  2. Phase 2: Audience Routing & Segmentation Validation (3 checks)
  3. Phase 3: Response Capture & SLA Workflow Integration (4 checks)
  4. Phase 4: Regulatory Archival & Escalation Readiness (3 checks) Use the formatting standard: [ ] **Phase [X].[Y] | [Item Title]**: [Audit Procedure] -> **Compliance Criterion**: [Specific Requirement]

Self-review

  • Confirm all context variables ({{device_classification}}, {{field_safety_event_type}}, {{recipient_facility_types}}, {{audit_trail_requirements}}, {{mandatory_acknowledgment_window}}, {{escalation_contact_matrix}}) are embedded in the logic.
  • Verify every check includes both an audit procedure and a compliance criterion.
  • Ensure strict alignment with post-market device vigilance standards.
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
medtech
field-safety-notice
post-market-surveillance