Standards-based, and specific about which standards.
A table of ticks is easy to write and useless to buy from. This one carries the partial rows and the missing ones.
Shipped, and in use
These are built, persisted and reachable today.
| Standard | What we do with it | Status |
|---|---|---|
| FHIR R4 | Exchange — records, documents, bulk export | Live |
| HL7 v2 | Messaging — ADT, ORU, order comms | Live |
| SNOMED CT | Clinical terminology; edition is a per-jurisdiction binding | Live |
| OMOP CDM v5.4 | Research extracts with a data-quality report | Live |
| ICD-10 | Morbidity and activity coding | Live |
| CVX | Vaccine coding, bound per jurisdiction | Live |
| DICOM | Imaging — a real viewer over Part 10 studies | Live |
| OpenID Connect / OAuth 2 | Federated sign-in and API authorisation | Live |
Everything with a caveat on it
Two of these are pending a publisher licence rather than any engineering: the adapter, the plumbing and the per-jurisdiction binding are built, and what is outstanding is a licence and its credentials.
| Standard | What we do with it | Status |
|---|---|---|
| openEHR | Record shape and a real EHRbase write path — see the ceiling below | Partial |
| IHE profiles | XCPD, XCA and ATNA built; conformance not certified | Partial |
| ATC | Anatomical main groups only — a subset, and it says so | Partial |
| DHIS2 2.40 | Aggregate national return; no payload sent to a live server yet | Partial |
| ICD-11 | Adapter and per-jurisdiction binding built; awaiting WHO licence | Pending licence |
| LOINC | Adapter built; awaiting Regenstrief licence and source access | Pending licence |
| OpenHIE 2.0 | Not built | Not built |
Terminology licensing is not uniform across the world
Terms differ by publisher, by country and by organisation type, and in several schemes a country’s membership status or income classification changes what it pays. SNOMED CT is the example we can evidence: it is licensed through a national affiliate arrangement and is free at the point of use in member and low-income countries — which is exactly why commvita treats the edition as a per-jurisdiction binding rather than shipping one and assuming it fits.
The specific current terms for ICD-11 and LOINC were not retrieved for this page. Confirm them with the publisher before they reach a business case.
The commercial model, stated as plainly as the technical one
£1 per instance
One pound per instance, with optional paid support. It is not free, and describing it as free would be the first inaccurate thing on this page.
Ours, yours or sovereign
Software as a service, self-hosted on your infrastructure, or a sovereign national deployment. Same images, same standards.
Open export, on demand
Bulk FHIR export and an OMOP extract with a data-quality report. What leaves can be checked rather than trusted.
What “openEHR” means here, precisely
commvita is designed to openEHR’s record shapes and writes a composition to an EHRbase repository on consultation completion, and per-jurisdiction EHRbase containers ship with the platform. That is a real integration and it works against a real clinical data repository.
It is not a native openEHR implementation, and we do not describe it as one. commvita ships 0 archetype definitions, has no AQL query support, and the default repository target in a stock configuration is a mock. A platform that claimed “openEHR-native” on this basis would be overstating it, and a buyer would find out during implementation rather than during procurement.
The reason to say so on a marketing page is simple: the gap is discoverable in about ten minutes by anyone technical, and a claim that fails that test damages every other claim beside it.