Clinical System Downtime Escalation Checklist
Mobilize Tier 3 technical support and preserve patient care workflows during critical health tech outages.
Use this template when critical digital health software or electronic health record integrations fail in an active healthcare environment. It generates a high-urgency operational checklist for support leads and technical incident commanders.
Role: Health Informatics Critical Incident Commander
Context
- Affected Health System: {{hospital_network}}
- Impacted Clinical System: {{impacted_system}}
- Clinical Workflow Risk: {{clinical_workflow_risk}}
- Downtime Protocol Activation: {{downtime_procedure_status}}
- Executive Incident Sponsor: {{executive_stakeholder}}
- Service Level Agreement Window: {{sla_breach_threshold}}
Task
Produce an operational incident checklist to coordinate Tier 3 engineering escalation, activate business continuity procedures, and maintain patient care continuity during an acute healthcare platform outage.
Method
- Review the degradation scope of {{impacted_system}} against active clinical workflows across {{hospital_network}}.
- Evaluate patient safety risks associated with {{clinical_workflow_risk}} to establish escalation priority.
- Verify whether {{downtime_procedure_status}} has been formally initiated across clinical operational units.
- Define technical triage steps for internal engineering, vendor integrations, and database operations.
- Structure communication cadence checkpoints to update {{executive_stakeholder}} and clinical department heads.
- Track restoration milestones against the mandatory {{sla_breach_threshold}} to prevent regulatory and operational breach.
- Detail recovery validation actions, including data synchronization and post-restoration chart audits.
Constraints
- Checklist items MUST prioritize patient safety and clinical continuity before root-cause investigation.
- Technical steps MUST include specific sign-off roles (e.g., Lead Architect, Nurse Supervisor, Security Officer).
- MUST NOT recommend manual data bypasses that violate HIPAA or data protection safeguards.
- The total checklist MUST NOT exceed 16 discrete, highly actionable items.
Output format
- Incident Snapshot (2 sentences covering affected systems and operational posture)
- Immediate Clinical Safeguards Checklist (3-4 items)
- Engineering & Vendor Triage Checklist (4-5 items)
- Stakeholder Communications Checklist (2-3 items)
- System Recovery & Data Reconciliation Checklist (3-4 items)
Self-review
- Check that each action item starts with a clear imperative verb.
- Confirm that downtime procedures and data integrity checks are explicitly accounted for.
- Ensure time-critical milestones align with {{sla_breach_threshold}}.
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.