HL7 Europe Base and Core FHIR IG
2.0.1 - trial-use
150
HL7 Europe Base and Core FHIR IG
2.0.1 - trial-use
150
HL7 Europe Base and Core FHIR IG - Downloaded Version 2.0.1 See the Directory of published versions
This page summarizes the main changes applied to this version of the guide.
Version 2.0.1 is a technical correction of the 2.0.0 release. It carries the resolutions of tickets recorded as technical corrections, corrections and clarifications, with one exception named below.
Substance and BiologicallyDerivedProduct to the reference targets of MedicalTestResultEuCore.focus. This is the one substantive addition in this release. It is included because the HL7 Europe Laboratory Report IG cannot apply its own resolution of FHIR-57055 without it: ObservationResultsLaboratoryEu derives from MedicalTestResultEuCore, and a derived profile cannot add reference targets its parent does not allow. The two tickets were resolved as a pair, the laboratory resolution stating that the targets are to be added "after being added to the EU base/core profiles".BodyStructure.extension:includedStructure in the R4 profile from 0..* to 1..*. The cross-version extension defines its own root as 1..*, derived from BodyStructure.includedStructure 1..* in R5, so the profile contradicted the extension it uses and the element was never optional. No tooling reported the mismatch: the cardinality of a contains rule is checked against the base element BodyStructure.extension, and an extension definition is evaluated only where an instance of it is present. Instances that omitted the included structure therefore passed validation against 2.0.0 without having been conformant to the extension.DiagnosticReportEuCore.performer. It used a profile discriminator on the path $this; on a Reference element that expression yields the reference itself and not the referenced resource, so the slices could not be discriminated and strict validators rejected the profile and everything derived from it. The discriminator path is now resolve(), as it already was on the resultsInterpreter slicing in the same profile. The defect was introduced with the profile (FHIR-53481) and is present in 2.0.0.component.extension:value-r5 slice in MedicalTestResultEuCore. It used the cross-version extension Observation.value, whose context is limited to Observation and therefore does not allow Observation.component. It now uses Observation.component.value, which has the matching context. Added the constraint obs-value-2 on Observation.component, mirroring obs-value-1, so that component.value[x] and component.extension:value-r5 cannot be used simultaneously.Observation.performer.extension:performerFunction to 0..1 in MedicalTestResultEuCore. The slice allowed 0..* although the event-performerFunction extension is itself defined as 0..1, so a second occurrence was never valid. Added a comment that a Practitioner(Role) acting in multiple roles has to be listed as performer multiple times.EhdsCategoriesEuVs. Nothing bound it: its only reference sat in the commented out category slice of CompositionEuCore, which went out of use with FHIR-55424, and no other HL7 Europe guide refers to it. Its presence suggested a settled position on document categories that the discussion has not reached. The commented out slice went with it, since holding the binding to this value set was all it did.LaboratoryResultStandardEuVs and SpeciesTypesEuVs, both left over from laboratory content that has since moved to the HL7 Europe Laboratory Report IG. Nothing in this guide bound either of them, and no other HL7 Europe guide refers to them. lab-obsCode-eu-lab shared its id and its title with a value set the Laboratory Report IG publishes under its own canonical with different content, which is a trap for anyone resolving it by id; speciesType-eu belonged to the animal patient, which this guide no longer carries.Left and Right to SiteQualifierEuVs, as they can be used both as a laterality and as a site qualifier. This reverses the removal made for FHIR-51391, following the discussion with the Orders & Observations WG. Added Apical, Central and Peripheral as well, completing pairs the value set already builds on: Basal was present without its counterpart, and Central / Peripheral follows the same pattern as Superficial / Deep.1.0.0 of the Xt-EHR EHDS logical models. Updated the model links from 0.3.0 to 1.0.0, renamed the mapping page of the medication summary model to EHDSMedicationUse to FHIR MedicationStatement Mapping, and reviewed the model map pages against the new model version: corrected relationship labels, added the missing EHDSPatient.deceased[x] and changeType rows, renamed EHDSObservation.component.code to component.type and mapped EHDSAddress.country to the country code.http://hl7.eu/fhir/base/StructureDefinition/periods-of-life to http://hl7.eu/fhir/extensions/StructureDefinition/periods-of-life. The canonical shown did not exist: the extension is published by the HL7 Europe Extensions IG, and this guide has never defined one under that id, while the sentence above the fragment already linked to the extensions guide. The core profiles slice the periodOfLife extension on the extensions canonical, so an instance built from the fragment did not match the slice and carried an unresolvable extension instead of the intended life stage.BodyStructure example covering more than one included structure, multiple site qualifiers and a business identifier.DiagnosticReportComposition extension from the R5 profile.DiagnosticReportEuCore to align with IPS.DiagnosticReportEuCore.performer and resultInterpreter in DiagnosticReportEuCore.procedure-targetBodyStructure extension.subject.reference.patient.reference.FlagEuCore to FlagPatientEuCore.Immunization profile to align with model maps.resultValidator.Composition.attester.party cardinality to 1.. for validator and legalAuthenticator.value[x] extension to fix extension errors.MedicalTestResultEuCore.0.3.0)
0.3.0.0.3.0 model and refactored EHDS-to-FHIR mappings based on the updated model.basedOn in Medication diff).2.0.0) (FHIR-53618)2.0.0 (FHIR-51370).iso21090-SC-coding extension with iso21090-codedString (FHIR-51664, R4).1.. (FHIR-51374).lowerCamelCase convention (FHIR-51663).Patient.name.extension[name-absent-reason] to 0..1 (FHIR-51261).Location.managingOrganization reference to OrganizationEU (FHIR-51268).Patient.communication to 0..0 for animals (FHIR-51362).name-or-identifier (FHIR-51392).
IG © 2024+ HL7 Europe. Package hl7.fhir.eu.base#2.0.1 based on FHIR 4.0.1. Generated 2026-09-13
