Executive Incident Notification for Hospital Clinical System Downtime
Draft an urgent, reassuring escalation email to hospital leadership during critical clinical system disruptions.
Use this template when mission-critical clinical software impacts care delivery workflows and requires immediate executive-level communication. It establishes containment status, safety protocols, and clear resolution timeframes.
Role: Senior Director of Critical Care Support and Clinical Incident Escalations.
Context
- Hospital network: {{hospital_network}}
- Impacted clinical application: {{affected_clinical_module}}
- Incident initiation: {{downtime_start_time}}
- Severity and clinical risk: {{patient_impact_level}}
- Floor continuity protocol: {{workaround_procedure}}
- Next milestone update: {{next_update_timestamp}}
Task
Draft an executive incident notification email to chief medical and information officers regarding an active clinical software escalation, providing immediate operational workarounds and clear recovery commitments.
Method
- Review the clinical severity based on {{affected_clinical_module}} and {{downtime_start_time}}.
- State clinical safety status clearly upfront to mitigate operational alarm across {{hospital_network}}.
- Detail the immediate containment measure and step-by-step {{workaround_procedure}} for bedside care teams.
- Describe the engineering triage actions underway without using unverified technical speculation.
- Calibrate risk transparency against the reported {{patient_impact_level}}.
- Confirm the engineering escalation chain and provide executive bridge line access.
- Establish the precise commitment window for the subsequent update at {{next_update_timestamp}}.
Constraints
- MUST state patient safety impact and active workarounds within the first two sentences.
- MUST NOT speculate on root cause until technical forensics are completed.
- Tone MUST remain calm, authoritative, and clinically responsible.
- Limit total word count to under 350 words.
Output format
Subject Line: [URGENT] Clinical Escalation | {{affected_clinical_module}} | {{hospital_network}}
Body Structure:
- Executive Situation Summary (2-3 sentences)
- Patient Safety & Clinical Workarounds (bulleted)
- Technical Containment & Recovery Actions (bulleted)
- Governance & Next Briefing Cadence (explicit timestamp: {{next_update_timestamp}})
- Incident Commander Sign-off
Self-review
- Does the draft immediately inform leadership how to maintain safe patient operations?
- Are all variables ({{hospital_network}}, {{workaround_procedure}}, etc.) seamlessly integrated without template residue?
- Is the tone suitably urgent yet disciplined and devoid of panicky language?
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.