Medical Device Integration, IEEE 11073 PHD, FHIR R4 Observations, Drone AED Dispatch, and Smart Equipment Bay IoT

Overview#

Bedside monitors capture every vital sign an ambulance crew needs, yet most of those numbers still reach the patient record by being read off a screen and typed in by hand during the worst moments of a resuscitation.

The Medical Device Integration capability closes that gap for ambulance services and emergency medical organisations. It manages a multi-tenant fleet of clinical-grade devices, streams their readings straight into the patient care record using recognised healthcare coding, coordinates drone-delivered defibrillators for cardiac arrest, and keeps every vehicle's equipment bay stocked through real-time sensor tracking. Four interlinked services share one tenant-isolated data model, so a service gains zero-transcription vital-sign capture, standards-compliant hospital handover, faster time to defibrillation, and dependable stock readiness from a single platform rather than four separate integrations.

Last Reviewed: 2026-05-26 Last Updated: 2026-05-29

Key Features#

• Multi-Tenant Clinical Device Fleet: Enrol defibrillators, ECG monitors, pulse oximeters, blood-pressure cuffs, glucose meters, capnographs, thermometers, and multiparameter monitors by serial number and IEEE 11073 device type, with each record fully isolated to its owning organisation.

• Vehicle and Tablet Pairing: Pair every device to a vehicle or a field tablet using a BLE address or tablet identifier, so a reading always carries the context of where and on what it was taken.

• Calibration-Due Alerting: Surface active devices whose last calibration has aged past a configurable threshold, helping a service keep its clinical kit inside its quality and assurance window.

• Standards-Based Vital-Sign Ingestion: Accept Personal Health Device readings carrying MDC codes and map them to recognised clinical codes for nine vital-sign types, including oxygen saturation, heart rate, systolic and diastolic blood pressure, respiratory rate, temperature, glucose, end-tidal carbon dioxide, and ECG heart rate.

• Zero-Transcription Encounter Population: When an active patient care encounter is present, a device reading auto-populates the encounter vital-signs record marked as device-sourced, removing manual re-entry during resuscitation.

• FHIR R4 Observation Export: Serialise every stored reading as a standard healthcare Observation resource, complete with clinical code, quantity, unit system, device reference, and effective timestamp, ready for hospital and national-dataset handover.

• Drone AED Dispatch Coordination: Request an unmanned defibrillator launch for cardiac arrest, persist the dispatch with GPS coordinates and rolling telemetry, guide bystanders with automated CPR text messages, and hand the case off to the arriving crew through encounter linkage.

• Smart Equipment Bay IoT: Track equipment-bay contents through RFID and BLE sensor events, maintain per-shelf and per-slot item state with drug codes and expiry dates, generate pre-shift readiness checklists against the registered bay layout, and restock consumables automatically when they fall below threshold.

Use Cases#

Ambulance Services and Emergency Medical Organisations#

• Resuscitation Documentation: A crew connecting a multiparameter monitor sees oxygen saturation, heart rate, blood pressure, and end-tidal carbon dioxide flow straight into the patient record without anyone pausing care to write numbers down.

• Standards-Compliant Hospital Handover: A receiving emergency department or a national clinical dataset receives the field observations as recognised healthcare resources, so handover needs no bespoke translation layer.

• Out-of-Hospital Cardiac Arrest: A control room requests a drone-delivered defibrillator the moment cardiac arrest is suspected, while the nearest bystander is texted clear chest-compression guidance and then talked through using the unit when it lands.

• Pre-Shift Vehicle Check: A crew starting a shift opens a readiness checklist that compares the live bay contents against the expected layout, flagging anything missing, low, or expired before the vehicle leaves the station.

• Consumable Restock: When adrenaline or defibrillation pads drop below their reorder point during a job, a restock request is raised automatically against the hospital medicines management workflow rather than waiting for a post-shift stock count.

Quality and Fleet Management#

• Calibration Governance: A fleet manager reviews which devices are due for calibration across every vehicle, keeping clinical equipment inside its assurance window.

• Device Provenance: Every reading is traceable to the specific enrolled device and pairing that produced it, supporting clinical audit and post-incident review.

Integration#

• Patient Care Encounter Record: Device readings link to the active encounter and auto-populate its vital-signs record marked as device-sourced, so the encounter remains the single system of record for the patient episode.

• FHIR R4 Clinical Exchange: Stored readings export as standard Observation resources, letting a service share field data with receiving hospitals and national datasets through the healthcare model they already expect, with no separate translation layer to build.

• REST and GraphQL Surfaces: Both a REST interface (under paths such as /api/v1/devices and /api/v1/medical-devices) and a typed GraphQL schema expose enrolment, observation ingestion, drone dispatch, and equipment-bay operations, so a customer can plug in whichever style suits their estate.

• Webhook-Style Event Intake: Drone telemetry posts and equipment-bay sensor events arrive over service-to-service calls and are tenant-scoped on receipt, letting external drone operators and IoT bay sensors stream updates without holding broad platform access.

• OAuth2 and JWT Authorisation: Access is governed by delegated tokens and authenticated GraphQL fields, so partner devices, drone operators, and bay sensors connect under standard, revocable credentials.

• Drone Operator Connector: An external drone operator interface is called over an authenticated connection to launch a unit and receive its identifier and estimated arrival, and dispatches are persisted only after the real operator accepts the request.

• Telephony Connector for Bystander Guidance: A multi-provider telephony connector sends bystander chest-compression and defibrillator-use messages, while a dispatch is never failed because a message could not be delivered.

• Hospital Medicines Management Connector: Bay consumables that fall below threshold raise a restock request through the hospital medicines management workflow, closing the loop from item removal to replenishment.

• Normalised Observation and Inventory Models: Readings from different device classes and events from different bay sensors are normalised into one observation model and one inventory model, so downstream consumers act on every device and every shelf in a consistent shape.

Open Standards#

• IEEE 11073 (Personal Health Device, MDC nomenclature): clinical devices are enrolled by their standard device type and emit readings tagged with MDC nomenclature codes, the recognised language of bedside medical-device data exchange.

• HL7 FHIR R4 (Observation resource): every stored reading serialises to a standard Observation resource with status, coded concept, valued quantity, device reference, and effective time, ready for healthcare interoperability.

• LOINC: incoming device codes map to LOINC clinical-observation codes for the nine supported vital-sign types, giving each reading a globally recognised clinical meaning.

• UCUM (Unified Code for Units of Measure): each observation quantity carries its unit under the http://unitsofmeasure.org system, so values are machine-comparable across devices and receiving systems.

• BNF (British National Formulary drug codes): equipment-bay medication items carry BNF drug codes, aligning bay inventory and automatic restock with the recognised United Kingdom medicines reference.

Security & Compliance#

• Multi-Tenant Data Sovereignty: Every table carries an organisation identifier, and every read and write is scoped to the owning organisation, so one service can never see another's devices, observations, dispatches, or stock.

• Fail-Closed External Calls: When the drone operator interface is unreachable or unconfigured, no dispatch row is created and the result is reported as unavailable rather than simulated, keeping the record an honest reflection of what actually launched.

• Auditable Event History: Equipment-bay sensor events are written to an append-only log and drone telemetry is retained as a rolling record, supporting post-incident review and clinical governance.

• Scoped Service Credentials: Drone and bay event intake is authenticated and tenant-resolved on receipt, so external operators and sensors stream updates without holding broad access to the wider platform.