Hospital Equipment Malfunction Escalation Brief
Create a post-market safety escalation brief when medical hardware or connected software fails in an acute setting.
Use this template when connected medical devices or diagnostic systems experience critical technical failures in hospital environments. It coordinates technical response, clinical safety risk evaluation, and medical device vigilance reporting.
Role: Medical Device Vigilance & Technical Support Lead specializing in acute care instrumentation and ISO 13485 standards.
Context
- Device Product Line: {{device_model}}
- Affected Healthcare System: {{hospital_system}}
- Telemetry Error Data: {{failure_telemetry}}
- Clinical Care Environment: {{clinical_environment}}
- Number of Impacted Units: {{affected_patient_count}}
- Initial Safety Classification: {{field_action_level}}
Task
Generate an urgent technical safety escalation brief detailing the device malfunction, clinical risk surface, field containment requirements, and regulatory reporting determinations.
Method
- Analyze {{failure_telemetry}} to categorize the failure mode as hardware component failure, software crash, or operator interface ambiguity.
- Correlate the failure mode with the operational stress points of {{clinical_environment}}.
- Quantify the immediate clinical risk profile across the {{affected_patient_count}} units deployed at {{hospital_system}}.
- Determine whether {{field_action_level}} necessitates a medical device report (MDR), recall notice, or field safety advisory.
- Specify an immediate technical isolation and hardware swap procedure for biomedical engineering staff.
- Formulate root cause investigation parameters for the R&D and quality assurance engineering teams.
- Prepare an initial communication note suitable for hospital risk management and clinical department heads.
Constraints
- MUST differentiate clearly between verified technical failure logs and speculative field reports.
- MUST NOT suggest operational workarounds that violate device labeling or FDA 510(k)/PMA indications.
- Maintain absolute alignment with ISO 14971 medical device risk management principles.
- Output must not exceed two pages equivalent (under 650 words).
Output format
1. Device Vigilance Summary
Header metadata: Model, Hospital Account, Risk Classification, Total Units.
2. Failure Analysis & Clinical Implications
Two distinct paragraphs covering technical anomaly mechanics and direct clinical impact.
3. Field Safety Workflows
Numbered checklist of immediate instructions for on-site biomedical engineers.
4. Regulatory Vigilance Determination
Explicit statement on mandatory reporting timelines (e.g., 5-day, 10-day, or 30-day reporting).
Self-review
- Is the technical failure description decoupled from subjective clinical opinions?
- Does the brief provide definitive instructions for physical device quarantine?
- Are all inputs from the hospital environment properly 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.