HL7 FHIR R4
The exchange standard the platform is built on, and the reason a record written today remains readable by a system built later.
Three properties that matter in the field
Resource-shaped
A patient, an observation, a condition, a medication statement — the units of exchange match the units of clinical thought.
Web-native
Ordinary HTTP and JSON. It can be implemented by a small team without a specialist integration platform.
Widely adopted
Including by the national ecosystem, which means our records are exchangeable by default rather than by special arrangement.
Experience
The team has seven years of working experience on FHIR R4, out of twelve years on the platform overall.
The whole stack
What we claim and what we do not
We build to R4
Resources, profiles and ValueSets are defined against FHIR R4.
Conformance is tested, not asserted
Claims of conformance mean nothing without a test suite behind them, and we treat independent testing as a gate before live data.
Review the architecture.
For technical evaluators.