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 waiting on a licence from the publisher, not on engineering. The adapter, the plumbing and the country settings are built. What is missing is the 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 isn’t 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’s licensed nationally, and free to use in member and low-income countries. That’s why commvita ties the edition to each country instead of shipping one and hoping 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 Commvita Flow Edition instance is one deployment for your organisation, with every environment included — production, test, training and disaster recovery. Not per seat, not per environment, not per site. With optional paid support. It isn’t free, and describing it as free would be the first inaccurate thing on this page.
Ours, yours or sovereign
Run it as a service, host it yourself, or run it as a national system. Same software, same standards.
Open export, on demand
Bulk FHIR export and an OMOP extract with a data-quality report. What leaves can be checked, not trusted.
What “openEHR” means here, precisely
commvita is built to openEHR’s record shapes. When a consultation is finished it writes the record to an EHRbase repository, and an EHRbase container ships with the platform for each country. That’s a real integration, working against a real clinical data repository.
It’s not a native openEHR implementation, and we don’t 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 instead of during procurement.
We say so here for a simple reason. Anyone technical can find the gap in about ten minutes, and a claim that fails that test poisons every other claim next to it.