Escalations
AuraScore 79/100

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.

Template

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

  1. Analyze {{failure_telemetry}} to categorize the failure mode as hardware component failure, software crash, or operator interface ambiguity.
  2. Correlate the failure mode with the operational stress points of {{clinical_environment}}.
  3. Quantify the immediate clinical risk profile across the {{affected_patient_count}} units deployed at {{hospital_system}}.
  4. Determine whether {{field_action_level}} necessitates a medical device report (MDR), recall notice, or field safety advisory.
  5. Specify an immediate technical isolation and hardware swap procedure for biomedical engineering staff.
  6. Formulate root cause investigation parameters for the R&D and quality assurance engineering teams.
  7. 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?
AuraScore breakdown
79/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 engineering10/12 · Adequate

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.

support-success
support-escalations
healthcare-life-sciences
medical-devices
biomedical
hospital-systems