A buyer's guide to medical device integration middleware

An ICU bed today is a small data centre: a multi-parameter monitor, a ventilator, six to ten infusion pumps, sometimes a dialysis machine and a balloon pump beside them. Each speaks its own dialect. The middleware that joins them to the chart will outlive most of the devices it connects — and most procurement processes spend less time on it than on the colour of the monitor screens. The demo always works; one bed, one monitor, clean network. The questions below are what separate a platform from a five-year integration project.

Ask how the licensing scales

There are two commercial models, and they age very differently. Per-device licensing means every connected box is a billing event: the eleventh pump on bed 14 costs money, expansion to the new wing reopens the contract, and the finance team learns to discourage connectivity. The honest model is per-protocol drivers — one driver per device family, covering every unit of that family you ever buy. A platform that already speaks the protocols of all leading manufacturers, across 200+ device models, should connect the next device of a supported family at no marginal licence cost. Ask which model you are being sold, and ask what the twentieth device on a bed costs.

Ask who keeps bed-to-patient association honest

A monitor does not know whose chest it is reading. Somewhere, the system holds the mapping between this device, this bed and this patient — and if that mapping is wrong, perfect data flows into the wrong chart, which is a clinical incident, not an IT ticket. Ask where the association lives, how it is reconciled against admission and transfer events, who confirms it at the bedside, and whether disassociation on discharge is enforced or merely hoped for. The right answer is explicit, role-controlled, visible to the nurse, and audit-logged on every change.

Ask what happens when the network fails

It will. Switches reboot, cables are kicked, a wing loses power during works. The question is whether your record gets a gap. Demand store-and-forward at the edge: the collector keeps capturing through the outage — a full day or more — and backfills automatically on reconnect, with the device’s original timestamps, never the arrival time, and with the outage itself flagged in the chart. The test is simple and worth insisting on: have the vendor pull the cable mid-demo and show you the chart an hour later.

Ask whether waveforms survive the journey

Vitals-only integration sends one number a minute. Useful, but it discards what the device actually saw: the ECG, pressure and plethysmograph waveforms running at 125 to 500 samples per second per channel. Waveforms are what let a clinician adjudicate an alarm after the fact, distinguish artefact from arrhythmia, and review the minutes before a deterioration. Ask whether waveforms are streamed, whether they are stored and for how long, and whether they can be replayed beside the numeric chart. “We can add waveforms later” usually means a different product.

Ask what happens on patient transfer

The patient goes from ICU to the operating theatre and back, or to imaging, or to another unit. Does the record follow, or does each location start a fresh chart that someone reconciles at midnight? Transfer is where bed-to-patient association, device handover and chart continuity all get tested at once. Walk the vendor through one specific journey in your own hospital and make them narrate every step.

Ask for the year-three reference, not the pilot

A 20-bed unit with ten devices per bed produces hundreds of thousands of vital-sign observations a day before a single waveform sample is counted. Pilots flatter everyone. Ask for a reference site running at the scale you will reach in year three — beds, devices, retention period — and ask what broke on the way there.

Device integration is the foundation everything else stands on: flowsheets, scores, alarms, tele-ICU. Buy it with the same seriousness. zMed’s device integration streams vitals and waveforms from 200+ device models across all leading manufacturers into one chart, with bedside-confirmed patient association and store-and-forward through outages of a day or more — see zMed Device Integration.

References

1. ANSI/AAMI/IEC 80001-1. “Application of risk management for IT-networks incorporating medical devices.” Association for the Advancement of Medical Instrumentation.
2. IHE International. “Patient Care Device (PCD) Technical Framework.” Integrating the Healthcare Enterprise.
3. ECRI Institute. “Top 10 Health Technology Hazards” (annual series; device-integration and alarm-transmission failures recur).
4. Health Level Seven International. “HL7 Version 2 Messaging Standard - ORU unsolicited observation results.” HL7.org.