Connectivity
Whatever runs in your hospital ends up in the API
Every HL7v2 message and 200+ medical device types arrive once, are mapped to international code systems and bound to the right patient. From then on, it is data anyone can build on, through one hospital API.
- medical device types connected
- 200+
- manufacturers and system vendors shown in the catalogue below
- 46
- every message a hospital information system sends, configured per hospital and mapped into FHIR
- HL7v2
- of connections built device by device, hospital by hospital
- 8 years
Every system speaks its own dialect.
Every hospital information system sends the same event in its own dialect of HL7, many with proprietary extensions the standard never foresaw. Every monitor model labels the same vital sign differently, and every device speaks its own protocol. Without translation, values from two sites cannot be compared, and data stays locked in the system that recorded it. monaOS resolves this once, at the point of entry, with a catalogue of device drivers and an engine that is configured rather than programmed, so no application built on top has to.
In, unified, out
From every source into one API
Three things turn hospital data into an API: getting every message in, giving every value a shared meaning and binding it to the right patient. Then it leaves through one route.
- 01HL7 Transformation Engine
Any HL7v2 system
Every HL7v2 message gets in, even from systems that bend the standard.
Every HL7v2 message a hospital sends, from admissions, transfers and discharges to orders and results, enters through the HL7 Transformation Engine, and device data takes the same path. The engine is configured per hospital, message type and event, so proprietary extensions and systems that do not follow the standard to the letter work through configuration, not new code.
- 02International code systems
Comparability
Every value is translated into international code systems on the way in.
A heart rate arrives as HR from one monitor, HF from another and PULSE from a third. At the point of entry, local labels, codes and units are mapped to international code systems, so a heart rate means the same thing on every unit and at every site. That makes values from different hospitals comparable, for a group's own reporting as much as for research. No application built on the API has to know which monitors a hospital runs.
- 03Patient and encounter
Binding
Every reading lands on the right patient, even when the device moves.
A monitor at a bed belongs to whoever is admitted to that bed, and admission, transfer and discharge messages keep that binding current. A device that travels with the patient, such as a transport monitor on the way to CT, is assigned to the patient by hand, so its readings join the same stay.
- 04Hospital API
Out
Out through one API, or as a message where a system needs one.
Applications read the unified data through the hospital API: the FHIR API for the clinical record and the time-series API for high-frequency device data, with permissions per application. Where an existing system expects data pushed to it, monaOS sends it in the format that system needs, as HL7v2 or FHIR. Either way, the data does not stay locked inside monaOS.
Hospital as an API
Connectivity
200+ medical device types, already connected
The manufacturers below are connected through drivers that already exist, grouped by device class. A new unit starts from this list.
How connectivity worksPatient monitors
Haemodynamics and neuromonitoring
Ventilators and anaesthesia
Infusion and nutrition
Dialysis and renal replacement
Diagnostics and point of care
Hospital information systems
Integration checklist
What to settle with your team
The questions that decide the timeline of an integration, ready for the first planning meeting.
- Source inventory
- Which systems and device types are in scope, and which interfaces each of them exposes.
- Network
- How the sources reach the platform: inside the hospital for on-premise, over the controlled connection for the Clinomic Cloud.
- Identifiers
- Which patient and encounter identifier systems each source uses, and how conflicts are resolved.
- Message scope
- Which message types and fields each source sends, so the mapping covers everything in use.
- Mapping
- Which local codes and units are translated into which international code systems, and who validates the mapping clinically.
- Device assignment
- How devices are assigned to patients, and what happens on transfer or device exchange.
- Outbound
- Which systems receive data from monaOS, and in which format.
- Access and audit
- Who may see and contribute what, and how activity is audited.
- Validation
- Test cases, parallel operation and acceptance criteria before go-live.
FAQ
Questions integration teams ask first
Is our device supported?
monaOS connects 200+ medical device types from the manufacturers in the catalogue above and more. Every project starts with an inventory of your unit's devices, which confirms each model and software version.
Does monaOS control our devices?
No. It receives data from medical devices without controlling or adjusting them. It has no alarm functions; the devices remain the reference for real-time surveillance.
What happens when a patient moves to another bed?
The transfer message from the hospital information system moves the patient's binding to the new bed, so device data from there lands on the same stay. Devices that travel with the patient are assigned by hand.
Our system does not follow the HL7 standard to the letter. Will it work?
Yes. The HL7 Transformation Engine is configured per hospital, message type and event, so dialects and proprietary extensions are handled by configuration.
Can we get our data out of monaOS?
Yes. Applications read it through the hospital API, as FHIR for the clinical record and as time series for device data. Systems that expect data pushed to them receive it as HL7v2 or FHIR.
Which HL7 messages are processed?
All of them. monaOS takes every HL7v2 message a hospital sends (admissions, transfers and discharges, orders, results and the rest) and maps it into FHIR, including terminology mapping.
Bring us your device list
The monitors, ventilators, pumps and analysers on your wards, and the systems that admit and report. We tell you what is configuration and what is work.