Medical device integration (MDI) is the software and networking that moves readings from bedside equipment, such as patient monitors, ventilators and infusion pumps, into the electronic health record (EHR) automatically, so nurses validate the numbers instead of typing them in. Most hospitals do this through a middleware layer that collects data from many device makes, translates it into HL7 messages and links each reading to the right patient before the EHR stores it.
How bedside data gets into the record
A typical integration has four steps.
- Capture. The device produces data: heart rate, blood pressure and SpO2 from a monitor, tidal volume and FiO2 from a ventilator, or rate and volume infused from a pump. Many devices send this over the hospital network; older ones need a serial-to-network adapter at the bedside.
- Association. The system has to know which patient the device is attached to. This is usually done by scanning the patient’s wristband and the device barcode, or by linking the device to a bed that the EHR’s admission, discharge and transfer (ADT) feed has assigned to the patient.
- Translation. Middleware or a manufacturer gateway converts proprietary device output into a standard format, most often an HL7 version 2 observation message, using standard device terminology.
- Validation and filing. In general wards and many intensive care units, the readings appear in the EHR flowsheet as unverified values. A nurse reviews and accepts them, which keeps a clinician responsible for what enters the legal record.
Some traffic runs the other way. GE HealthCare’s CARESCAPE Gateway, for example, sends trended vital signs out to charting systems in HL7 2.3, 2.4 and the IHE PCD-01 format (HL7 2.6), accepts ADT data back so monitors do not need manual patient entry, and supports an HL7 query that returns a near real-time snapshot from a monitor. GE says a single gateway connects up to 512 monitoring devices on its CARESCAPE network.
The standards involved
No single standard covers the whole path. Hospitals and vendors combine messaging standards from HL7, device terminology and architecture from IEEE 11073, and integration profiles from IHE that state which options to use for a given job.
| Standard or profile | Body | What it does in MDI | Status (as of November 2026) |
|---|---|---|---|
| HL7 version 2 (ORU observation messages, ADT) | HL7 International | The message format most EHRs accept for device observations and patient admission data | Long established; still the main production format |
| IHE PCD Device Enterprise Communication (DEC), transaction PCD-01 | IHE Patient Care Device domain | Constrains HL7 v2 so device observations reach the EHR in a predictable way | Final Text |
| IHE PCD Alert Communication Management (ACM) | IHE | Sends device alarms to nurse phones, pagers and other alert systems | Final Text |
| IHE PCD Point of Care Infusion Verification (PIV) | IHE | Sends infusion parameters from the medication record to the pump | Final Text |
| IHE PCD Infusion Pump Event Communication (IPEC) | IHE | Sends pump events, such as starts, stops and rate changes, back to the EHR | Final Text |
| IEEE 11073-10101 nomenclature and 10201 domain information model | IEEE / ISO | Common codes and data model for device measurements, used inside the HL7 messages | Published |
| IEEE 11073 SDC (20701, 20702, 10207, 10700) | IEEE / ISO | Service-oriented, manufacturer-independent communication between devices and between devices and IT systems | Core standards published; device specialisations still being developed |
| HL7 FHIR Point-of-Care Device Implementation Guide | HL7 Devices work group | Represents acute-care device data as FHIR resources, with device metadata and provenance | Trial use, FHIR R4; continuous build under ballot |
Profile status comes from the IHE PCD profiles list. The IHE Patient Care Device domain also lists trial implementation profiles for point-of-care identity management and Rosetta terminology mapping.
IEEE 11073 SDC
Service-oriented device connectivity (SDC) is the IEEE 11073 family designed for networked, multi-vendor device communication, including in operating theatres. Its core parts are 11073-20702 (the web services communication profile), 11073-10207 (the domain information and service model) and 11073-20701 (the architecture and protocol binding). IEEE added IEEE 11073-10700-2022, approved on 8 November 2022 and published on 15 September 2023, because the protocol alone does not show that a function combining several devices is safe, effective and secure. It sets out responsibilities for each participant in an SDC system, and an ISO/IEEE version followed in 2024.
FHIR
FHIR is spreading through EHR interfaces, but bedside device feeds still run mostly on HL7 v2. The HL7 Point-of-Care Device Implementation Guide says it supplements HL7 v2 and IHE PCD-01 rather than replacing them. It is based on FHIR 4.0.1, carries trial-use status at maturity level 2, and maps to both the IEEE 11073 domain information model and SDC.
Middleware vendors
Hospitals can connect devices one manufacturer at a time through that manufacturer’s gateway, or use vendor-neutral middleware that handles many makes. The largest independent integration business is now part of Philips. Philips announced on 19 January 2021 that it would buy Capsule Technologies for $635 million in cash (about €530 million), saying Capsule served more than 2,800 hospitals and healthcare organisations in 40 countries. Capsule had already acquired Bernoulli Health on 30 April 2019, adding the Bernoulli One clinical surveillance product; Bernoulli reported more than 450 installed systems at the time.
Device manufacturers also sell their own connectivity, such as GE HealthCare’s CARESCAPE Gateway for its monitors. EHR suppliers run their own platforms too: Oracle Health’s Device Connectivity Catalog (version 3.0, January 2026) lists more than 1,000 validated devices, from patient monitors and infusion pumps to dialysis and laboratory analysers.
Infusion pump and EHR interoperability
Pump integration is the most clinically sensitive form of MDI because data flows in both directions. With auto-programming, a nurse scans the patient, the medication and the pump, and the order details (drug, concentration, rate and volume) are sent to the pump for confirmation instead of being keyed in. With auto-documentation, the pump reports starts, stops, rate changes and volumes back to the EHR. These two directions correspond to the IHE PIV and IPEC profiles.
The evidence base is small. A systematic review by Borrelli and colleagues in Medical Devices: Evidence and Research (April 2025) found only three peer-reviewed inpatient studies. They reported a 15.4% to 54.8% reduction in the types of error interoperability can directly affect, and cumulative reductions of 21.2% to 90.5% across all medication administration errors. The authors linked the wide range to differences in baseline compliance, setting and patient population. Four of the six authors work for Becton, Dickinson and Company, which makes infusion systems, and the review calls for more research on adverse drug events, workflow and patient outcomes.
Cybersecurity rules
Connecting devices to hospital networks increases exposure, and regulators now require manufacturers to deal with this before devices reach the market.
United States: FDA section 524B
Section 3305 of the Food and Drug Omnibus Reform Act of 2022, enacted on 29 December 2022, added section 524B to the Federal Food, Drug, and Cosmetic Act. Premarket submissions for “cyber devices” (510(k), PMA, De Novo, PDP and HDE) must show that the device meets its cybersecurity requirements. The FDA’s guidance, Cybersecurity in Medical Devices: Quality System Considerations and Content of Premarket Submissions, was updated in June 2025, according to the Federal Register notice of 27 June 2025. That update replaced the September 2023 version and added a section on which devices and sponsors are covered.
As summarised by security firm Medcrypt, a cyber device is one that includes software, can connect to the internet and could be vulnerable to cybersecurity threats. Manufacturers must provide a plan to monitor and address postmarket vulnerabilities, including coordinated disclosure, and processes for routine and urgent updates and patches. They must also supply a software bill of materials covering commercial, open-source and off-the-shelf components.
England: DSPT and DTAC
NHS organisations in England assess their own cyber security through the Data Security and Protection Toolkit (DSPT), which NHS England’s board assurance guidance describes as aligned to the National Cyber Security Centre’s Cyber Assessment Framework. The guidance set a submission deadline of the end of June 2026 and says requirements will tighten each year until 2030. Suppliers of digital health technology are assessed through the Digital Technology Assessment Criteria (DTAC). NHS England published an updated DTAC form on 4 March 2026 with about 25% fewer questions, less overlap with the DSPT, and a focus on software-based technologies, with full transition by 6 April 2026.
What the evidence shows on benefits
Studies of automated vital sign capture show faster and more complete records, but smaller gains than staff often expect. In a 2018 study in BMC Emergency Medicine, Skyttberg, Chen and Koch compared manual and automatic documentation in a Stockholm emergency department across 200 vital sign measurements from 50 patients. Readings reached the record in an average of 0.6 minutes with automatic documentation against 7.7 minutes manually. Completeness was 98% against 95%, a significant difference. Correctness was also 98% against 95%, but this difference was not statistically significant. Staff reported lower time pressure, though the fall in frustration was about half what they had anticipated.
Taken together, the published research supports faster documentation and fewer transcription gaps, plus a likely reduction in some infusion errors. Most studies come from single sites, and several have manufacturer involvement. Hospitals planning MDI usually judge results locally against baseline measures such as charting delay, missing observations and pump programming overrides.
More on TechAnnouncer: What the Oura Ring can and cannot tell you about blood pressure and IoT advantages and disadvantages.
Sources
- IHE: Patient Care Device profiles
- IEEE: IEEE 11073-10700-2022
- HL7: Point-of-Care Device Implementation Guide
- GE HealthCare: CARESCAPE Gateway
- Philips: acquisition of Capsule Technologies (19 January 2021)
- Capsule Technologies: acquisition of Bernoulli Health (30 April 2019)
- Federal Register: FDA premarket cybersecurity guidance notice (27 June 2025)
- Borrelli et al., Medical Devices: Evidence and Research (2025)
- Skyttberg, Chen and Koch, BMC Emergency Medicine (2018)
- NHS Innovation Service: updated DTAC form and guidance


