Vendor directory
Device Integration & Interoperability
Connected device data is worthless until it lands in the EHR clean, mapped, and patient-associated. Vendor-neutral integration middleware is the layer that gets it there, normalizing output from hundreds of device models and routing it to the EHR, alarm management, and clinical surveillance. We evaluate these platforms on driver coverage, standards support (HL7, FHIR, IHE PCD), and how they handle alarms, the connectivity layer HTM and clinical informatics own together.
Ascom
Vendor-independent medical device integration software that collects device data for alarm management, clinical surveillance, and nurse call — integrating RTLS and wearables.
Better Care
Sabadell, SpainBetter Care makes BC Link, a vendor-agnostic medical device interoperability platform that connects bedside devices such as multiparameter monitors, ventilators, anaesthesia workstations, and pulse oximeters, then harmonizes their data, including high-resolution waveforms, into a unified clinical database. BC Link integrates bidirectionally with hospital systems (EHR, HIS, PACS, LIS) and is certified as a Class IIb medical device in Europe. It can be deployed on-premise, cloud, or hybrid.
Connexall
Toronto, ON, CanadaConnexall is a vendor-neutral clinical alarm management and event-notification middleware platform that ingests alarms and events from patient monitors, nurse call, smart beds, IV pumps, and IT systems, then applies routing and escalation rules to deliver alerts to caregiver endpoints such as smartphones, voice badges, and workstations. It is positioned as enterprise middleware sitting between source systems and care teams. Connexall is a product of GlobeStar Systems, founded in 1992.
Emorphis Health
Indore, IndiaHealthcare software engineering firm that builds custom medical device integration software, capturing real-time data from bedside devices and routing it into the EHR to automate manual clinical data entry. Also offers EHR/FHIR/HL7 integration, care management, and SaMD development services.
Medical Informatics Corp (Sickbay)
Houston, TX, USAMedical Informatics Corp makes Sickbay, an FDA-cleared, vendor-neutral platform that collects and aggregates high-resolution physiologic waveforms and numeric data from bedside monitors, ventilators, pumps, and other ICU devices across manufacturers. It time-synchronizes and stores this data for real-time remote monitoring, virtual ICU, and downstream analytics and machine-learning applications. The platform is used as clinical data infrastructure for predictive monitoring research.
MediCollector
Boston, MA, USAMediCollector provides software for real-time acquisition, recording, and streaming of medical device data, captured directly from bedside devices such as Philips, GE, and Dräger monitors. It captures both waveform and numeric vital-signs data and translates vendor-specific protocols into standardized HL7 messages for HIS, EMR, and integration engines. Classified as a Medical Device Data System (MDDS), it acquires and transports data without altering it. MediCollector was founded in 2017 in Boston out of the Wyss Institute at Harvard.
Philips Capsule
Vendor-neutral Medical Device Information Platform (MDIP) that connects 1,200+ device types via 250+ drivers and streams harmonized data to EHRs, alarm management, and clinical surveillance systems.
Frequently Asked Questions
What does vendor-neutral device integration middleware actually do, and how is it different from the EHR?
Middleware sits between bedside devices and the EHR, handling data acquisition, normalization, protocol conversion, and routing. The EHR stores and displays the patient record; it does not speak the dozens of proprietary device protocols a hospital runs. Vendor-neutral middleware connects devices from any manufacturer to any EHR (Epic, Oracle Health, MEDITECH) plus alarm and surveillance systems, so you are not locked into one device vendor's gateway.
Which interoperability standards should we require in an integration platform?
Expect HL7 v2.x messaging (ADT, ORM, ORU) for the core observation flow into the EHR and FHIR R4 (Device, Observation, DeviceMetric resources) for modern app and analytics layers. On the device side, look for IEEE 11073 / SDC and the IHE Patient Care Device profile, specifically PCD-01 (Device Enterprise Communication), which standardizes how device observations reach enterprise systems. A platform supporting all four covers both legacy and forward-looking deployments.
What does alarm management middleware add beyond device connectivity?
Alarm middleware filters, prioritizes, and forwards device alarms to secondary notification channels (mobile devices, pagers, central stations) so the right alert reaches the right clinician. This directly supports Joint Commission NPSG.06.01.01 on clinical alarm safety and aligns with IEC 60601-1-8 alarm-priority principles. The design goal is reducing alarm fatigue without downgrading urgent conditions, so validate latency, packet loss handling, and acknowledgment behavior before you buy.
What are our obligations under IEC 80001 when devices connect to the hospital network?
IEC 80001-1 places risk management for any IT network carrying medical devices on the "responsible organization," meaning the hospital, across the full network lifecycle. You must manage safety, effectiveness, and security before, during, and after connecting devices. IEC 81001-5-1 extends this to security activities across the health-software lifecycle. Practically, HTM, IT, and clinical engineering share a documented risk-management process rather than treating connectivity as a one-time install.
How do device integration platforms address IoMT cybersecurity?
Connected device counts multiply the attack surface, so integration platforms should support network segmentation, encrypted transport, and device authentication, not just data movement. Request each device's MDS2 (Manufacturer Disclosure Statement for Medical Device Security) to assess its security posture, and confirm the middleware vendor follows FDA premarket cybersecurity expectations. Treat the integration layer as a security boundary, not a neutral pipe.