Quick reference of openEHR conformance for Atomik. For full detail see openEHR conformance docs.
CaboLabs spent 4 years on openEHR Conformance Verification. That work was taken as the foundation for the official openEHR Conformance specification (currently in DRAFT).
We also designed the openEHR Conformance Framework — broader in scope than the official spec, and the foundation for a formal openEHR Software Certification Program. When we say Atomik is conformant, we're the ones who defined what conformant means.
Atomik implements both openEHR Reference Models: EHR and Demographic (RM 1.0.2). Upgrading to a newer version is straightforward.
What this means for you: patient records and demographic data are semantically interoperable with any other conformant system worldwide — no proprietary data translation required, now or in the future.
EHR Extract is not yet supported but is on the roadmap.
Spec: openEHR RM Release-1.0.2
Atomik complies with the openEHR REST API release 1.0.2, covering: EHR, EHR_STATUS, CONTRIBUTION, COMPOSITION, and DIRECTORY.
What this means for you: your integration team uses standard tooling and documentation — no proprietary SDKs, no undocumented endpoints. Any developer familiar with the openEHR REST spec can integrate on day one.
Most AQL implementations are technically spec-compliant but not truly portable — the spec defines syntax, not execution semantics, so the same query can return different results on different CDRs.
Atomik implements SAQM (Simple Archetype Query Model), a vendor-neutral query formalism designed specifically for portability across CDR implementations. No syntax lock-in. No silent result differences between vendors. The openEHR service layer formally supports alternative query formalisms alongside AQL. The SAQM spec will be publicly available.
Spec: openEHR ITS-REST Release-1.0.2
Atomik uses Operational Templates (OPTs) — sets of openEHR Archetypes composed for a specific clinical context. Supports OPTs based on AOM 1.4.
What this means for you: existing clinical templates deploy as-is — no conversion step, no proprietary template format to learn. Templates created with standard openEHR tooling work out of the box.
Spec: openEHR AM Release-2.2.0
We love to hear from you, let us know how we can be of help.
