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 source 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.
npx --yes @records-fhir/cli@0.1.1 \ profile install hl7.fhir.eu.base \ --version 2.0.0 --activatenpx --yes @records-fhir/cli@0.1.1 validate-file \ ./ehds-lab-clean-lab-result-bundle.json \ --engine --format jsonprofile install requires a configured Records connection and permission to install packages. It changes the workspace catalog. The separate local validate-file --engine check uses packages available on your machine; it does not inherit the workspace installation, and a passing Bundle check does not establish that its entries were checked. Download the teaching input from the EHDS lab. To reproduce the profile exercise in Records, check the Patient and Observation against the installed profiles and inspect the recorded package and terminology basis.
| 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.
A Patient Summary is a document, not a flat Bundle
The European Patient Summary carries its own ballot version and a clinical-document readiness preflight before any profile validation is read.
Records recognises IPS and European Patient Summary Bundles as clinical documents. Before the profile result is meaningful, the document itself has to hold together: a Composition, a subject, resolvable section references, and the declared document standard and version.
That preflight is shown as its own state. A blocked readiness result is not the same finding as a failed profile constraint, and the two are never merged into a single pass/fail badge.
Inspect a Patient Summary in its document context.
Explore document structure, embedded resources and a correction in the workflow library.
Records
Correct and recheck an IPS document
Follow a missing Composition title through source correction to the new document result.
Records
Repair a Bundle reference
Find an unresolved subject reference, correct the test copy and validate the Bundle again.
Records
Read a Bundle timeline
Follow a dated entry to its underlying resource and field.
The run records its reproducibility basis
The relevant evidence is not only pass/fail; it also states whether the measurement context was fully locked or remained provisional.
Records preserves validator identity and configuration, enabled aspects, terminology basis, package context, source, scope, thresholds, timestamp, and environment evidence. A comparison is clean only when the outcome-affecting inputs are compatible and the lock limitations are explicit.
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 an approved FHIR scope against pinned national and HL7 Europe package contexts, with explicit evidence and lock status.