Standards

Standards & Interoperability

HealthOS ICU is designed around published international standards for medical device interoperability. No proprietary protocols are required in the primary integration path.

Architecture

Interoperability planes

Interoperability planes Three standards groups: the control / telemetry plane (HL7 v2/MLLP, IHE DEV/PCD, ISO/IEEE 11073 SDC) feeds the HealthOS ICU platform; the platform hands off to the record plane (FHIR R4, PROV-O, SHACL) and to the auxiliary plane (DICOMweb). INTEROPERABILITY PLANES EQUIPMENT PLANE HL7 v2 / MLLP IHE DEV / PCD ISO/IEEE 11073 SDC HealthOS ICUplatform RECORD PLANE FHIR R4 PROV-O / evidence-of-fact receipt SHACL / Knowledge Graph AUXILIARY PLANE DICOMweb (WADO-RS / QIDO-RS)
Three planes: control and telemetry feed in, record flows out, auxiliary is retrospective review only.

Equipment

Equipment Plane

Standard Role Conformance
HL7 v2 / MLLP Inbound monitor stream ingestion Implemented
IHE DEV / PCD (PCD-01, DEC, ACM) Structured device data Partial
ISO/IEEE 11073-10207 SDC Bedside service-oriented control Partial

The control plane carries real-time telemetry from bedside devices. HL7 v2 over MLLP is the entry point for existing installations. An architectural slot for IHE PCD adapters enables structured device-data communication. The SDC write path (governed restricted-write control) is not part of HealthOS ICU v0 (pilot program): native bedside control remains on the roadmap, gated by phased validation and a vendor-supplied access-and-control package. Detailed status for each standard — in the conformance matrix →

Record

Record Plane

Standard Role Conformance
FHIR R4 Clinical data facade (results, audit, provenance) Implemented
PROV-O Provenance tracking in evidence-of-fact receipts Implemented
SHACL Knowledge graph constraint validation Implemented

FHIR R4 resources (Observation, Device, DeviceMetric, GuidanceResponse, Provenance, AuditEvent) are emitted by the clinical-data facade (a data projection for external systems) as a downstream projection of the canonical event log. FHIR is not the source of truth — the medical knowledge graph store (the source of truth, not FHIR) is.

PROV-O provides the provenance ontology for the evidence-of-fact receipt (proof of provenance): a cryptographic chain proving how a runtime artifact was derived from approved knowledge. SHACL validates the knowledge graph at compile time.

Auxiliary

Auxiliary Plane

Standard Role Conformance
DICOMweb (WADO-RS / QIDO-RS) Retrospective episode visualisation Partial

DICOMweb is used exclusively for retrospective episode review — loading waveform segments and correlating them with audit and result events for research and incident analysis. DICOM is not used as a command transport or stateful stream ingress.

Vendors

Vendor interoperability

The four-level adapter architecture accommodates vendors at any integration depth:

1. Read-only

HL7 v2/MLLP ingest — any vendor with HL7 output.

2. Structured

IHE PCD profile mapping — vendors with PCD support.

3. Bidirectional

ISO/IEEE 11073 SDC read path — SDC-capable devices.

4. Governed write-back

ISO/IEEE 11073 SDC write path — phase 2, per-vendor validation pack.

Next

Documents

Technical Overview

Vendor interoperability, adapter architecture details

View →

Conformance Matrix

Implemented, partial, planned — for each standard

View →

Discuss a phased rollout at your clinic or an integration with your equipment.

Contact the team