Connected Medical Device Telemetry Outage Escalation Matrix
Map telemetry loss durations, physiological monitoring risks, and field biomedical engineering escalation paths across hospital sites.
Deploy this template when continuous patient monitoring devices or connected diagnostic hardware lose central server connectivity. It guides biomedical support leads to systematically triage device fleet outages and safeguard patient monitoring.
Role: Principal Medical Device Support Engineer with specialization in connected bedside telemetry, physiological signal processing, and FDA vigilance reporting.
Context
- Fleet Hardware: {{device_model}}
- Active Firmware: {{firmware_version}}
- Deployed Location: {{hospital_site}}
- Unresolved Outage Duration: {{telemetry_loss_duration}}
- Field Support Lead: {{biomedical_point_of_contact}}
- Compliance Boundary: {{fda_mdr_threshold}}
Task
Design a multi-tiered telemetry outage escalation matrix that defines hardware troubleshooting sequences, on-floor nursing alert shifts, and regulatory vigilance filing steps.
Method
- Assess hardware-level vulnerability for {{device_model}} operating on {{firmware_version}} against known network socket disconnection behaviors.
- Evaluate patient safety risks associated with {{telemetry_loss_duration}} across high-dependency versus step-down beds at {{hospital_site}}.
- Define escalation stages based on cumulative disconnection time (Immediate 0-15m, Moderate 15-60m, Severe 60m-4h, Critical >4h).
- Specify actions for {{biomedical_point_of_contact}} regarding local device buffer preservation and central telemetry server restarts.
- Establish exact triggers that necessitate shifting from automated central monitoring to bedside 1-to-1 nursing observation.
- Align each outage stage with criteria dictated by {{fda_mdr_threshold}} for reportable malfunction logging.
- Detail device quarantine procedures if hardware replacement is required.
Constraints
- Deliverable MUST center on a structured markdown triage matrix.
- MUST NOT recommend power-cycling life-support devices without explicit verification of local backup battery status.
- Every stage must specify both a biomedical engineering duty and a bedside nursing duty.
- Limit matrix entries to concise operational actions rather than narrative explanations.
Output format
- Incident Overview Header (key metadata summary, 3 bullets).
- Hardware Telemetry Escalation Matrix (markdown table containing columns: Outage Stage, Duration Threshold, Technical Remediation Action, Bedside Nursing Mitigation, Escalation Target / Notification, MDR Compliance Check).
- Device Fleet Quarantine Protocol (3 sequential technical validation steps).
Self-review
- Ensure {{device_model}} and {{firmware_version}} are directly addressed in technical remediation actions.
- Confirm {{hospital_site}} logistics and {{biomedical_point_of_contact}} duties are clear across all four outage stages.
- Check that the transition point for {{fda_mdr_threshold}} compliance is unambiguously identified.
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.