uid stringclasses 10
values | dataset_id stringclasses 1
value | care_setting stringclasses 4
values | monitoring_ordered_signal stringclasses 2
values | monitoring_type stringclasses 5
values | alarm_limits_set_signal stringclasses 3
values | device_connected_signal stringclasses 3
values | monitoring_active_signal stringclasses 3
values | activation_timing_signal stringclasses 4
values | alarm_events_acknowledged_signal stringclasses 3
values | escalation_after_alarm_signal stringclasses 3
values | documentation_complete_signal stringclasses 3
values | system_outcome_signal stringclasses 5
values | clinical_summary stringclasses 10
values | question stringclasses 1
value | ground_truth_label stringclasses 2
values | ground_truth_rationale stringclasses 10
values | lead_time_window_hours int64 6 24 | source_citation stringclasses 1
value |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
CMDA-001 | clinical-monitoring-order-device-activation-coherence-risk-v0.1 | Ward | yes | telemetry | yes | yes | yes | on_time | yes | yes | yes | stable | Telemetry ordered. Device connected, alarms set, monitoring active on time. Alarm event acknowledged and escalation completed. Documentation complete. | Is order vs device activation coherent. Answer coherent or incoherent. | coherent | Order executed and monitoring active. | 12 | Synthetic |
CMDA-002 | clinical-monitoring-order-device-activation-coherence-risk-v0.1 | Ward | yes | telemetry | yes | no | no | none | no | not_applicable | no | unmonitored_risk | Telemetry ordered but device not connected and monitoring never became active. No documentation of why. | Is order vs device activation coherent. Answer coherent or incoherent. | incoherent | Order not executed. | 12 | Synthetic |
CMDA-003 | clinical-monitoring-order-device-activation-coherence-risk-v0.1 | ED | yes | spo2_continuous | no | yes | yes | on_time | yes | yes | yes | stable | Continuous SpO2 ordered. Device connected and active but alarm limits not set. Alarm acknowledged and escalation done. | Is order vs device activation coherent. Answer coherent or incoherent. | incoherent | Alarm limits missing despite active device. | 6 | Synthetic |
CMDA-004 | clinical-monitoring-order-device-activation-coherence-risk-v0.1 | ICU | yes | invasive_bp | yes | yes | yes | on_time | yes | yes | yes | stable | Invasive BP monitoring ordered and activated promptly with alarm limits configured. Alarms acknowledged and acted upon. | Is order vs device activation coherent. Answer coherent or incoherent. | coherent | Full activation with alarms. | 6 | Synthetic |
CMDA-005 | clinical-monitoring-order-device-activation-coherence-risk-v0.1 | Ward | yes | telemetry | yes | yes | yes | late | no | not_applicable | yes | governance_risk | Telemetry ordered and connected but activation delayed. No alarm events documented. Documentation complete. | Is order vs device activation coherent. Answer coherent or incoherent. | incoherent | Late activation. | 12 | Synthetic |
CMDA-006 | clinical-monitoring-order-device-activation-coherence-risk-v0.1 | Ward | yes | resp_rate_continuous | yes | yes | yes | on_time | yes | no | yes | missed_escalation_risk | Monitoring active and alarms set. Alarm events occurred and were acknowledged but escalation not completed. | Is order vs device activation coherent. Answer coherent or incoherent. | incoherent | Activation ok but response loop failed. | 6 | Synthetic |
CMDA-007 | clinical-monitoring-order-device-activation-coherence-risk-v0.1 | Ward | yes | telemetry | yes | yes | no | none | not_applicable | not_applicable | no | unmonitored_risk | Telemetry ordered and device connected but monitoring not active due to system configuration issue. No escalation. | Is order vs device activation coherent. Answer coherent or incoherent. | incoherent | Connected but not active. | 12 | Synthetic |
CMDA-008 | clinical-monitoring-order-device-activation-coherence-risk-v0.1 | ED | yes | spo2_continuous | yes | yes | yes | on_time | yes | yes | yes | stable | Continuous monitoring ordered. Device active, alarms configured, and alarm responses documented. | Is order vs device activation coherent. Answer coherent or incoherent. | coherent | Aligned. | 6 | Synthetic |
CMDA-009 | clinical-monitoring-order-device-activation-coherence-risk-v0.1 | Outpatient | no | none | not_applicable | not_applicable | not_applicable | not_applicable | not_applicable | not_applicable | not_applicable | stable | No monitoring order event. | Is order vs device activation coherent. Answer coherent or incoherent. | coherent | No monitoring loop required. | 24 | Synthetic |
CMDA-010 | clinical-monitoring-order-device-activation-coherence-risk-v0.1 | Ward | yes | telemetry | yes | yes | yes | on_time | no | not_applicable | no | false_reassurance_risk | Monitoring ordered and activated. No alarm acknowledgements recorded in window despite events. Documentation incomplete. | Is order vs device activation coherent. Answer coherent or incoherent. | incoherent | Alarm handling gap creates false reassurance. | 12 | Synthetic |
What this repo is for
This dataset tests whether a model can detect coupling failures between monitoring orders and actual device activation.
It measures alignment between the clinical decision to monitor and the operational reality that monitoring is active with alarms configured and responded to.
It predicts unmonitored deterioration false reassurance when alarms are not handled missed escalation after alarm events.
You use it for patient safety monitoring clinical AI eval for operational follow-through ward telemetry governance audits
- Downloads last month
- 18