MII IG Laborbefund
2027.0.0-ballot -
Germany
MII IG Laborbefund - Local Development build (v2027.0.0-ballot) built by the FHIR (HL7® FHIR® Standard) Build Tools. See the Directory of published versions
Ballot version for 2027.0.0. It contains the following changes compared to the previous version 2026.0.3.
de.medizininformatikinitiative.kerndatensatz.laborbefund, which is the id the module is distributed under. The repository previously declared …kerndatensatz.labor, so a consumer following the packageId stated in the guide could not resolve the package. The canonical is unaffected.system URL would not match in a pattern. The ValueSet compositions remain version-bound.type.profile carry no version either. An extension slice matches on Extension.url, a uri without a version in the instance, so a version there fixes something that plays no part in matching. Which package version applies is stated in the dependencies; pin-canonicals fixes versions in the published output.Coding.version is flagged Must Support on Observation.code, Observation.valueCodeableConcept and ServiceRequest.code.2027.0.0-ballot, the version this module is balloted alongside. The CapabilityStatement references that module's Observation interpretation search parameter.category is sliced, open, with one mandatory slice carrying the mandatory HL7 coding — $v2-0074#LAB on the laboratory report, $observation-category#laboratory on the laboratory test. LOINC 26436-6 stays permitted as a further coding but is no longer required. The slicing deliberately sits on category, not on category.coding: category is 1..*, and constraints below a repeating element apply to every repetition, so on category.coding every further category would have to repeat the mandatory codes. A laboratory area belongs beside the mandatory slice as its own category entry. The slice names changed — v2-lab and observation-category; in 2026.0.3 they were lab-category. Names appear in validator messages and in profile diffs. Measured against the category shapes of every release since 2025.0.2, including the microbiology module's: all validate.0..*, constrained to Reference(ServiceRequest) and flagged Must Support (issue #82). The cardinality stays that of the base profile; basedOn is mandatory only on the laboratory report, and has been so unchanged since 2025.0.2.code onto the new open slice code.coding[loinc], is tightened from preferred to extensible, and points at a different IPS ValueSet — results-laboratory-pathology-observations-uv-ips instead of results-laboratory-observations-uv-ips. Observation.code itself no longer carries a binding.qualitativ and semiquantitativ originally foreseen have been dropped, because the two ValueSets overlap and can therefore not be discriminated.L, LU, N, H, HU). Locally common scales such as --, -, N, +, ++ or L N H map onto these; beyond the "alarm" limits the abnormal codes A, HH, LL and AA may additionally be used.fix: Invariant mii-lab-2: the expression hasMember.exists() xor value.exists().not() implies dataAbsentReason.exists() did not evaluate as described and now reads hasMember.exists() or value.exists() or dataAbsentReason.exists() — at least one of the three elements has to be present.based-on is now mandatory (SHALL); it had been commented out.interpretation NEW and mandatory (SHALL). R4 defines no such search parameter; the definition in the Meta module is referenced instead, with identical code and type.requester removed (issue #82).mii-exa-labor-laborwert-ratio states its result as valueQuantity with the composed UCUM unit mg/(24.h) instead of as a valueRatio. A ratio cannot be reached through value-quantity — the R4 expression is (Observation.value as Quantity) | (Observation.value as SampledData) — while the CapabilityStatement requires that parameter as SHALL. The instance id keeps its -ratio suffix, because the URL has been published before.experimental set to false. status was already active.Observation.note, and the interpretation-affecting properties. It sets out how the narrow FHIR sense of "interpretation" relates to its wider use in the Rili-BÄK and ISO 15189 (both linked), what a coded interpretation is worth for secondary use and where its data quality is limited.Version 2026.0.3 contains the following changes compared to the previous version 2026.0.2 (for a complete overview of the changes, the differential view on GitHub can be used).
Note: Version 2026.0.3 is a package release carrying out technical corrections. The Implementation Guide was not changed in substance.
fix: Unification of the version designation of the 2026 artifacts on 2026.0.3; several profiles, extensions, ValueSets and the CapabilityStatement still referenced 2026.0.0.fix: Update of the meta.profile and supportedProfile references from 2026.0.0 to 2026.0.3.fix: Update of the example instances to profile version 2026.0.3; some profile references still pointed at 2026.0.0.2026.0.0 to 2026.0.3 in package.json, sushi-config.yaml, qc/custom.rules.yaml and the FSH rule sets.README.md from 2026.0.0 to 2026.0.3.Version 2026.0.2 contains the following changes compared to the previous version 2026.0.1 (for a complete overview of the changes, the differential view on GitHub can be used).
Note: Version 2026.0.2 is a package release carrying out technical corrections. The Implementation Guide was not changed in substance.
fix: Correction of the dependency from hl7.fhir.uv.extensions to hl7.fhir.uv.extensions.r4, so that the R4 extensions in use resolve correctly.fix: Version specification of the referenced FHIR ValueSet identifier-type on 4.0.1.fix: Correction of the LOINC display text in the example mii-exa-labor-laborwert ("hohe Vergrößerung").Version 2026.0.1 contains the following changes compared to the previous version 2026.0.0 (for a complete overview of the changes, the differential view on GitHub can be used).
Note: Version 2026.0.1 is a package release carrying out technical corrections. The Implementation Guide was not changed in substance.
fix: hl7.fhir.uv.extensions was added as a dependency in order to support snapshot generation by Simplifier. MII_PR_Labor_Laboruntersuchung had no snapshot until then.Version 2026.0.0 contains the following changes compared to the previous version 2025.0.2 (for a complete overview of the changes, the differential view on GitHub can be used).