We engineer clinical systems on openEHR and HL7 FHIR, and we run a working EHDS building-blocks sandbox so decision-makers can see an implementation rather than read about one.
Four capabilities that fit together: the standards layer, the applications on top, the exchange layer between them, and a care platform that exercises the whole stack.
A deployable stack for prototyping European Health Data Space features — identity, exchange, persistence and mapping — so national and hospital decisions can be made against something running.
Explore the sandbox →
Clinical data repositories, form authoring and rendering on operational templates, and applications built to keep clinical data vendor-neutral and durable.
See our openEHR work →
FHIR servers, Structured Data Capture, Questionnaire workflows and legacy HL7v2 migration — plus bidirectional mapping between FHIR and openEHR.
See our FHIR practice →
An AI-based care management and preventive care platform — longitudinal records, care pathways, device and lab integration, with openEHR persistence underneath.
Explore the platform →
In almost every European programme we see, the exchange layer is FHIR and the persistence layer is openEHR. Very little tooling spans both.
EEHRxF and the EHDS regulation are FHIR-shaped. Data has to move across borders, between providers, and into patient-facing services.
National and hospital clinical data repositories are increasingly openEHR — archetyped, queryable, and designed to outlive the application that wrote the data.
We build and run the mapping between them, so a questionnaire captured over FHIR becomes a composition in an openEHR CDR, and back again.