Medical Device Field Safety Customer Notification Assessment Report
Structure an urgent, clear, and compliant safety communication strategy for healthcare providers and impacted device users following a field action.
Use this template when a medical device manufacturer needs to deploy critical safety notices, voluntary corrections, or recall updates to clinical customers. It delivers a comprehensive communication plan and message audit.
Role: Principal Medical Device Regulatory Affairs and Customer Communications Specialist
Context
- Device Identifier: {{device_model_identifier}}
- Hazard Classification: {{hazard_classification_tier}}
- Affected Customer Cohort: {{affected_patient_cohort}}
- Regulatory Window: {{regulatory_reporting_window}}
- Corrective Action Protocol: {{remediation_action_protocol}}
- Governing Standard: {{jurisdiction_compliance_standard}}
Task
Author a formal customer safety notification report and email communication strategy addressing hospital administrators, biomeds, and clinicians regarding urgent field corrections for {{device_model_identifier}}.
Method
- Assess clinical severity and operational risk implications based on {{hazard_classification_tier}} and {{jurisdiction_compliance_standard}}.
- Segment customer recipients into critical cohorts: procurement directors, clinical department leads, and biomedical engineering teams.
- Formulate clear, un-euphemistic hazard descriptions explaining the operational risk of {{device_model_identifier}} within {{affected_patient_cohort}}.
- Design a tiered email notification workflow satisfying transmission deadlines under {{regulatory_reporting_window}}.
- Draft primary Urgent Medical Device Correction / Field Safety Notice (FSN) email text tailored for healthcare providers.
- Create an auditable acknowledgment email template enabling providers to confirm inventory quarantine and receipt.
- Detail step-by-step remediation procedures matching {{remediation_action_protocol}}.
- Build an escalation protocol for non-responsive accounts to ensure total customer notification coverage.
Constraints
- MUST use clear, non-defensive technical language that strictly aligns with {{jurisdiction_compliance_standard}}.
- MUST NOT downplay risk or use ambiguous marketing terminology in safety alert emails.
- Acknowledgment mechanisms MUST provide unambiguous receipt tracking capabilities for regulatory audit trails.
- Emergency escalation timelines must fit strictly within {{regulatory_reporting_window}}.
Output format
Provide a technical report structured in the following sections:
- Executive Risk Summary & Regulatory Mandate (max 250 words)
- Customer Segmentation & Communication Dispatch Plan (table with Stakeholder, Message Focus, Delivery Timing)
- Provider Email Notification Suite (Full email text for Initial Urgent Advisory, Follow-up Reminder, and Quarantine Confirmation)
- Remediation & Device Tracking Workflow (step-by-step technical instructions for {{remediation_action_protocol}})
- Audit Trail & Regulatory Compliance Verification Checklist
Self-review
- Ensure the hazard statement is completely free of minimization or liability-shifting phrasing.
- Verify that clear instructions for device quarantine, return, or software patch are present.
- Confirm that receipt confirmation requirements satisfy {{jurisdiction_compliance_standard}}.
Explicit role, a named task, and discrete steps the model can follow.
Background, inputs and variables the model needs before it starts.
Hard boundaries — what the model must and must not do.
A named, field-level shape for the response.
Ordered work items that force analysis before an answer.
Length and structure that travel across frontier models.
Signal density — instruction weight without padding.
Documented variables so the scaffold adapts to new inputs.
Quality bar, assumptions and behaviour when inputs are thin.
How much real usage the template has behind it.