Medical Device Safety Notification Program Review
Analyzes safety alert email architectures for healthcare providers and institutions to ensure rapid remediation.
Deploy this template when regulatory alerts, recalls, or corrective actions require immediate customer communication. It produces an institutional response audit and message governance report.
Role: VP of Medical Device Safety and Regulatory Affairs specializing in post-market surveillance and institutional crisis communications.
Context
- Device Class & Affected Serial Batches: {{device_identifier_scope}}
- Hazard Severity & Clinical Risk: {{risk_classification_level}}
- Stakeholder Segmentation: {{affected_customer_segments}}
- Clinical Remediation & Action Steps: {{remediation_protocol}}
- Statutory Notification Window: {{notification_timeline_target}}
- Multi-Channel Fallback Architecture: {{multichannel_fallback_plan}}
Task
Produce an exhaustive Field Safety Notice (FSN) Customer Email Strategy and Governance Report that establishes transparent, legally sound, and actionable digital communication protocols for hospital procurement teams, clinical leads, and biomedical engineering departments.
Method
- Classify urgency tiers based on {{risk_classification_level}} to structure the subject line and visual hierarchy.
- Map distinct notification streams for each sub-group defined in {{affected_customer_segments}} (e.g., surgeons vs. hospital risk officers).
- Translate complex technical corrections in {{remediation_protocol}} into definitive, step-by-step clinical instructions.
- Align transmission sequencing and receipt acknowledgement workflows with the timeline in {{notification_timeline_target}}.
- Design automated follow-up sequences for non-responsive institutions to satisfy compliance mandates.
- Integrate verification protocols with the backup channels provided in {{multichannel_fallback_plan}}.
- Develop verification metrics to confirm device quarantine, software patching, or physical return rates.
Constraints
- MUST include explicit legal and regulatory disclaimers required for {{risk_classification_level}}.
- MUST NOT downplay clinical risks or use ambiguous marketing euphemisms in safety notices.
- Action steps must be executable within the time constraints of {{notification_timeline_target}}.
- Email architecture must provide an auditable acknowledgment trail for healthcare providers.
Output format
Deliver an executive-level safety notification report arranged as follows:
- Regulatory Threat Assessment & Executive Briefing (under 300 words)
- Segment-Specific Message Matrices (subject lines, headers, body directives, acknowledgments)
- Clinical Remediation Step Breakdown (bulleted protocol instructions)
- Escalation & Verification Workflow (timeline schema with non-response fallbacks)
- Post-Notice Audit & Regulatory Compliance Ledger
Self-review
- Is every technical instruction in {{remediation_protocol}} unambiguous and clinically safe?
- Have I satisfied all statutory timelines mandated in {{notification_timeline_target}}?
- Are the distinct informational needs of procurement, engineering, and clinical staff addressed?
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.