Architecture
Hospital as an API
monaOS turns a tangle of systems into one clean interface. All clinical data arrives once, is unified and is available through the hospital API: for our applications, for your own software, for third-party developers and for AI with read access. New applications plug in without needing an interface of their own.
Hospital API
one route for every application
FHIR API
Patient, stay, results, medication, every change
Observation?patient=…&_sort=-date
Time-series API
High-frequency device data
monaOS unifies, once
Hospital
Built on
The foundation of the API
Standards

An API is only as good as the data behind it. monaOS prepares every value before an application sees it: translated, bound to its patient and stay, coded and versioned.
FHIR® is the registered trademark of HL7 and is used with the permission of HL7.
One data model for everything
HL7 FHIR is the common language, whatever system delivers the data. The same resources for patient, stay, observation and medication in every hospital, never a proprietary schema.
Context included
Every value carries its patient, stay, time and source. An application or an AI reads it exactly as it was meant, without reassembling the context.
Shared codes
Local codes are mapped to international code systems at entry, so values stay comparable across units, hospitals and applications.
Traceable
Each change creates a new version with its author, so a correction never erases what was there before.
Permissions per application
What an application may read and write is set when it is connected, and every access is recorded in the audit.
Clinical data
PostgreSQL
Relational database
QuestDB
Time-series database
RabbitMQ
Message broker
Valkey
Key-value store
Services and workspaces
Node.js
Service runtime
NestJS
Service framework
Angular
Clinical workspaces
Keycloak
Identity and sign-in
Permify
Authorisation
Platform and operations
Kubernetes
Orchestration
Argo CD
Deployment
Vault
Secrets
Prometheus
Metrics
Grafana
Monitoring
The path of one value
From the device into the API, in four steps
01 · Hospital site · In
Arrives
A laboratory result as an HL7v2 message, a heart rate from the monitor, both through the Clinomic Cloud Connector.
02 · HL7 Transformation Engine · In
Unified
Translated into FHIR, bound to the patient and the stay, and its local codes mapped to international code systems, with the hospital's mapping applied at entry.
03 · Clinical record · The record
Stored with its history
Kept as a resource with its source and version history, and the write is audited.
04 · Hospital API · Out through the API
Available to every application
Workspaces, terminals, the hospital's own software and third-party applications read it through the hospital API. AI tools read it through the monaOS AI server, read only.
The services
The services behind the API
In
Clinomic Cloud Connector
The secure connection between the hospital and the platform. HL7v2 messages and device data from the hospital site travel through it.
In
HL7 Transformation Engine
Takes every HL7v2 message a hospital information system sends, device data included, and creates the FHIR resources in the clinical record. The mapping is configured per hospital, message type and event, so the engine fits whichever HL7v2 systems a hospital runs.
Across
Identity, permissions, audit
Personal sign-in, roles and permissions per application apply in every service. Every change creates a new version with its author and time.
Core
Clinical record
The single source of truth, held on a FHIR server: everything about the patient and the stay, every value with its source and version history. Every other store is filled from it, and no data path goes around it.
Out
Hospital API
The one route to all clinical data, for our applications and for yours: a FHIR API for the clinical record and a time-series API for high-frequency device data. What each application may read and write is granted per application.
Out
Time-series store
Serves high-frequency device data for charts and trends, fast and at any resolution, from one minute to one day, and to other applications through the time-series API. It is filled from the clinical record.
Out
Scores and algorithms
Prefills scores from what is already in the record, following internationally standardised scoring systems, and calculates fluid balances by the unit's own rules. Clinicians confirm the result instead of collecting the values by hand.
Out
monaOS AI server
AI tools such as Claude or ChatGPT reach the data through a guarded gateway, read only.
FAQ
Questions evaluators ask first
Does monaOS replace our hospital information system?
No. The hospital information system, the laboratory system and the devices stay where they are. monaOS connects to them, builds one clinical record from what they send, and makes that record available to the workspaces and applications above it.
Is monaOS one product or several?
One platform. The intensive care and anaesthesia workspaces and the AI tools all run on the same clinical data repository, so an anaesthesia case continues on the unit without a transfer step.
Where does the data live?
In the clinical data repository of your installation: on the Clinomic Cloud in European data centres, or on-premise. High-frequency device data is additionally held in the time-series store beside it.
Can we connect our own software?
Yes, through the unified hospital API, with read access and any write capability scoped per application and per connection.
Can third-party developers build on monaOS?
Yes, through the same hospital API, with permissions per application and per connection. Our own applications use the same interface.
Which parts are certified?
monaOS is certified as a medical device under MDR, Class IIa. Clinomic's quality and information security management are certified to ISO 13485 and ISO/IEC 27001, and the Clinomic Cloud Services hold a BSI C5 Type 2 attestation for June 2025 to May 2026 (basic criteria).
Talk to one of our engineers
Bring your estate: the systems that admit and report, the devices on the wards, the software you want to connect. We map it onto the services behind the API with you.