Born-Digital, Alarm-Smart: A Med-IT Playbook for Single-Room Wards

Single rooms and curved wards are fantastic for paediatric experience—but they remove line-of-sight. In Day 1 Session A, nursing lead Tracy and clinical engineering head Tony Fitzgerald showed how CHI is building a “born-digital” hospital where alarms are routed to the right person at the right time, closed-loop meds actually work, and every bed has one monitor + one pump—all without drowning staff in beeps.

The lesson for Med-IT: treat the alarm fabric and device data flows as clinical safety systems, not “nice-to-have” integrations.

The clinical brief (translated for Med-IT)

• 100% single rooms + curved corridors: staff cannot “hear” or “see” patients by default. Visibility must come from nurse-station dashboards and handhelds tied to patient assignment.
• Actionable alarms only: differentiate clinical alarms (act now) from equipment alerts (act soon); suppress noise; escalate intelligently.
• Closed-loop medicines: Wi-Fi infusion pumps with enterprise drug libraries, remote updates, and bi-directional EHR flows.
• Total-hospital monitoring: one monitor platform that follows the patient (ED → OR → ward), normalises data to the EHR, and feeds an alarm middleware layer.
• One board per station: aggregate monitors, pumps, nurse-call (and even plant alarms) into a single dashboard.

Vendors in this programme: Dräger (physio monitoring), B. Braun SpacePlus (infusion), Masimo (device connectivity + alarm management), Epic (EHR), with a trust integration engine in the middle.

Architecture that scales (and stays safe)

1) Separate data integration from alarm orchestration

• Data integration layer: normalise device telemetry and chart to the EHR (Epic) as the record of care (e.g., via FHIR/HL7). NHS expects FHIR for modern APIs; use the national catalogue and guidance to hold suppliers to it. NHS England Digital+2NHS England Digital+2
• Alarm orchestration layer: a vendor-agnostic platform (Masimo Patient SafetyNet here) that de-duplicates, prioritises and escalates alarms to nurse stations and handhelds—configurable by pod, day/night ratios, and patient assignment.

2) Standards first (so you don’t write adapters forever)

• FHIR for clinical data exchange and subscriptions-style workflows where available. NHS England DigitalNHS England
• SDC (IEEE 11073) for open, service-oriented device connectivity in high-acuity settings—so you can evolve without proprietary lock-in. ornet.orgIEEE Standards Association
• IEC 80001-1 as your governance spine for networks with medical devices: manage risk across safety, effectiveness and security, with shared accountability between IT, clinical engineering and suppliers. ISOPMC
• GS1/Scan4Safety identifiers (GSRN, GLN, GTIN/GIAI) so people/places/products align across EPR, inventory and alarm routes. Scan4Safetyhealthcare.gs1uk.org

Alarm fatigue: workflows before webhooks

Tracy’s rule is the right one: only actionable alarms should reach a human. That means:

• Set parameter bands for clinical action, not “nice-to-know.”
• Route clinical alarms differently from equipment alerts (with clear priorities).
• Build escalation ladders that reflect staffing (pods by day; ward-wide at night), and show escalation state on the handset tile.

Med-IT’s job is to make those choices enforceable in software—and visible in logs—so nursing can tune without a change ticket.

Network & cyber: the quiet work that prevents loud days

• Segment devices with NAC/VLANs; allow-list only the ports/protocols needed to EHR, integration and alarm servers.
• Broker cloud telemetry via controlled egress; time-sync everything (NTP); log at the edge and the core.
• Treat vendor remote access as privileged (short-lived credentials, session recording, no standing tunnels).
• Run IEC 80001-1 risk management as a joint process with clinical engineering; use published measure/indicator catalogues to operationalise it. ISOPMC
• Evidence your posture through the Data Security and Protection Toolkit (DSPT)—the mandated NHS self-assessment for organisations handling NHS data. NHS England Digitaldsptoolkit.nhs.uk

Governance that sticks (the socio-technical bit)

CHI formed equipment decision groups (clinician-chaired, clinical-engineering-led), then embedded clinical engineers into the IT project team and hired engineers with network/interop backgrounds. That glue mattered more than any single box.

Mirror that with our personas:

• Clinical Engineering Lead: co-chairs build/BAU huddles; owns acceptance at the bedspace; co-authors alarm policies.
• Integration Architect: enforces FHIR/SDC, event models and testable contracts; refuses pay-to-integrate clauses. NHS England
• EPR Product Owner: defines charting cadence, flowsheet targets and safety-net reconciliation.
• Pharmacy Informatics: owns the drug library; Med-IT owns rollout rings, telemetry and adoption metrics.
• Cyber/IG Lead: runs DPIA/TRA, DSPT evidence, vendor-access controls and incident playbooks. NHS England Digital

A pragmatic build sheet for Med-IT

• One monitor + one pump estate-wide: fewer drivers, simpler training, faster patching.
• One dashboard per station: alarm middleware aggregates everything (monitors, pumps, nurse-call, plant).
• Handheld mirror of the board: assignment-aware tiles; trends and waveforms; on-device acknowledge/escalation.
• Drug-library CI/CD: pharmacy edits; platform pushes after-infusion; success/failure telemetry and monthly adoption reviews.
• Observability: syslog/OTel from gateways, alarm servers, integration engine; SLOs for message latency and delivery; drill alarms regularly.
• Anchor to national direction: shared-care-record aims and FHIR expectations make this board-friendly infrastructure, not an optional project. NHS England+1

“When the big sliding door closes, you won’t hear anything in the room.”
Your alarm fabric is now part of basic life safety—treat it that way.

Conclusion

Single-room wards demand quiet networks that shout only when it matters. Use FHIR and SDC for openness, run IEC 80001-1 together with clinical engineering, make handhelds the nurse’s second pair of eyes, and push the drug library like code. Build the rails—and the wards will run on time.