HL7 Europe Base/Core IG 2.0.0 evidence
What the new HL7 Europe Base and Core FHIR Implementation Guides look like when they become executable validation evidence.
For: EHDS program teams, FHIR implementers, national infrastructure teams
Why this matters
Published IGs are not the same thing as measurable conformance.
HL7 Europe published Base and Core FHIR Implementation Guides 2.0.0 for both FHIR R4 and R5 on 28 April 2026. The guides define European base and core profiles, extensions, constraints, terminology, and mapping material intended to support EHDS-aligned implementations.
The operational question for implementation teams is narrower: can a system validate actual resources against a pinned version of those profiles, preserve the run configuration, and show the resource, profile, and validation messages together?
That is the evidence surface Records is built to produce. No clinical payloads are stored; the evidence consists of resource IDs, profile references, issue counts, run metadata, package pins, and reproducibility fingerprints.
The validation lane
A small synthetic EHDS smoke run pinned to the published HL7 Europe packages.
Install the published R4 package
records profile install \ hl7.fhir.eu.base#2.0.0Run a pinned validation
records validate-file \ ./ehds-2026-base-laboratory-bundle.json \ --ig=hl7.fhir.eu.base#2.0.0 \ --fhir=R4| FHIR package | hl7.fhir.eu.base#2.0.0 |
| FHIR release | R4 / 4.0.1 |
| Companion lane | hl7.fhir.eu.base-r5#2.0.0 |
| Fixture source | Synthetic EHDS smoke bundle |
| Profiles | EU Core Patient, Medical Test Result Observation |
| Output | Run metadata, issue list, profile-aware resource view |
Profiles become visible
The first screen should answer which profile package and profile set were used.
Resources and messages stay together
A useful EHDS evidence screen does not hide validation issues away from the resource that produced them.
The run is reproducible
The relevant evidence is not only pass/fail; it is the locked measurement context.
Every Records run keeps the validator configuration, enabled aspects, terminology source, package pins, thresholds, timestamp, and environment label together. That is what lets a team compare a future HL7 Europe IG update against this exact baseline.
For EHDS work, this is the useful stance today: validate against the published profiles now, keep the evidence, and re-run the same resource scope when HL7 Europe or the implementing acts move the target.
Source references
The evidence lane is anchored to the official HL7 Europe publication and IG pages.
Validate your EHDS baseline.
Use Records to run your current FHIR resources against national and HL7 Europe profiles with reproducible evidence.