Skip to content
Get in touch

Why one platform

Every clinical system needs the same patient data. monaOS connects it once.

Intensive care documentation, the anaesthesia record, telemedicine, research and now AI all draw on the same monitors, ventilators, laboratory results and admission data. Bought as separate products, each one needs its own interfaces, keeps its own copy of the patient and brings its own logins, audit and contract. monaOS is one certified platform for all of them: your hospital connects its systems and devices once, and every workspace and application works from the same record, in the international HL7 FHIR standard.

Connected once

Four connections instead of twenty: every source connected once, for every application

A system bought on its own is connected to every source on its own. Each of those interfaces has to be specified, tested and kept running through every update on both sides. On one platform each source is connected once, and every further workspace reads what is already there.

Bought one by one

IntensiveCareAnaesthesiaTelemedicineResearchAIFurtherapplicationsMonitorsVentilatorsLaboratoryHospitalinformation system
20+ interfacesEach system connected to each source on its own, and a copy of every patient in each. Every further application adds four more interfaces.

On monaOS

monaOS · one FHIR record, one set of rulesIntensiveCareAnaesthesiaTelemedicineResearchAIFurtherapplicationsMonitorsVentilatorsLaboratoryHospitalinformation system
4 connectionsEach source connected once, and every system works from the same record. A further application reads that record too: still four connections.

Built on HL7 FHIR

One record, in the international HL7 FHIR standard

monaOS is FHIR-native. The clinical record is stored as standard HL7 FHIR resources, bound to the patient and the stay. Messages from hospital information systems in HL7v2 are translated into FHIR the moment they arrive, so the record is never held in a proprietary schema.

HL7 FHIR, an HL7 International Standard
  • Stored in FHIR

    The record itself consists of standard FHIR resources with explicit references to the patient and the stay, not of a schema only Clinomic can read.

  • Read through FHIR

    Workspaces, applications and AI read the record through the same FHIR interface, so any FHIR-capable software can work with it.

  • Ready to exchange

    The same representation carries research, federated data sharing and the European Health Data Space.

FHIR® is the registered trademark of HL7 and is used with the permission of HL7.

What it costs

What separate systems cost your hospital every day

  • Staff enter the same values twice

    More detail

    Separate systems: Values are typed from one system into the next

    One platform: Every workspace shows the same values, nothing is typed in twice

  • The patient's story breaks at every handover

    More detail

    Separate systems: The handover at the door is verbal

    One platform: The next team opens what the last one documented

  • Every new system is a new project

    More detail

    Separate systems: New interfaces, validation and training every time

    One platform: Starts on connections that already run

  • Every system is another risk to manage

    More detail

    Separate systems: Own accounts, audit and security review per product

    One platform: One role concept, one audit, certified

One patient, one record

One stay, from theatre to discharge, in the same record

One patient record

  1. In theatre

    Anaesthesia record

  2. On the intensive care unit

    Intensive care record

  3. At tele-rounds

    The specialist's advice

  4. Before discharge

    Discharge summary

Bring the list of systems on your units

Tell us which systems and devices your units run today and what you want to add. We show you what monaOS connects and what runs on top of it.