MII IG Dokument
2027.0.0-ballot.2 -
This page is part of the MII IG Dokument (v2027.0.0-ballot.2: 2027 Ballot 3) based on FHIR (HL7® FHIR® Standard) R4. This is the current published version in its permanent home (it will always be available at this URL). For a full list of available versions, see the Directory of published versions
This page contains a changelog describing the changes between versions.
It records the changes between the released versions of the Dokument module, newest version first, and follows Keep a Changelog and the KDS calendar versioning scheme described on the Versioning page.
Each version gets its own section with the release date and the changes grouped by category:
Leave out the categories with nothing to report. Where a change is driven by an issue or a pull request, link it.
Breaking changes MUST be reported and explained
A version section that contains a breaking change is not complete until it answers, explicitly and in this changelog:
What counts as breaking — treat a change as breaking if it does any
of the following, even when it looks small: tightens a cardinality
(0..* → 1..1), raises a binding strength (example →
required), removes codes from a required value set, removes or renames an
element or a slice, narrows a type, adds an invariant or a must-support
obligation, or changes a canonical URL. When in doubt, report it as
breaking.
Breaking for whom: state both perspectives — stored data (instances valid against the old version) and implementations (clients and servers built against it; a removed search parameter breaks implementations while every stored instance stays valid).
The version number will not warn anyone. The KDS calendar versioning
scheme (YYYY.n.n) carries no major-version signal the way SemVer
does — this changelog section is the only warning a reader gets.
Link the technical delta. From the second formal publication on,
enable the IG Publisher's version comparison (version-comparison,
to be added to sushi-config.yaml — see the
Versioning page for the setup and its
prerequisites); it publishes a
machine-generated comparison at
comparison-v<previous>/index.html. Link it from the version
section, so the prose explanation and the technical diff sit side by side.
Mark such entries clearly (for example, prefix them with BREAKING:) so a reader scanning the section cannot miss them.
Date 2026-09-14 · Status ballot release (2027 cycle)
Rebuilds 2027.0.0-ballot against the released Meta and Base ballot
packages. The previous release pinned their release candidates, which were the
newest versions at the time it was prepared; both modules published their final
ballot on 2026-09-10.
kerndatensatz.meta and kerndatensatz.base both move
from their release candidates (2027.0.0-ballot.rc3 and
2027.0.0-ballot.rc1) to 2027.0.0-ballot.SearchParameter definitions the CapabilityStatement
points at, and the Patient, PatientPseudonymisiert and
KontaktGesundheitseinrichtung profiles the examples use. Nothing was
removed from either dependency.2027.0.0-ballot, which remains resolvable. Ballot against
this version.Known Issue: 2 validation errors on examples with
context.event(eventCodeList expansion, upstream defect inde.ihe-d.terminology 3.0.1) — see Issue #33
Date 2026-09-13 · Status ballot release (2027 cycle)
The ballot release of the 2027 cycle. Content is that of release candidate 2, which was published to the package registry and reviewed without change requests; this version supersedes both candidates and is the one to ballot against.
2027.0.0-ballot.rc2 — the
profile, the extension, the terminologies, the logical model, the
CapabilityStatement and the examples are identical. Only the version
identifiers, the publication descriptor and this changelog differ.2027.0.0-ballot.rc1 and 2027.0.0-ballot.rc2. Both remain
resolvable in the package registry; neither should be used for the ballot.Known Issue: 2 validation errors on examples with
context.event(eventCodeList expansion, upstream defect inde.ihe-d.terminology 3.0.1) — see Issue #33
Date 2026-09-08 · Status ballot release candidate 2 (2027 cycle)
Second candidate of the 2027 ballot version — the rc1 content after the guide's
migration from Simplifier to the HL7 IG Publisher (MII KDS module template
v0.13.1, English as the default language, German translation). No changes to
the profile, the extension, the terminologies or the logical model; the package
content changes through translation extensions (.po), the SNOMED CT licence
notice on the four SNOMED value sets, the corrected supportedProfile and the
CapabilityStatement's search-parameter references to the Meta module.
kerndatensatz.base 2027.0.0-ballot.rc1,
kerndatensatz.meta 2027.0.0-ballot.rc3.supportedProfile points at the Dokument profile
(rc1: at its own metadata URL); the three module-specific search parameters
reference the Meta module's SearchParameter definitions.http://fhir.de/CodeSystem/Kontaktebene; titles and descriptions for all
example instances; ExampleScenario of the NLP pipeline.input/ignoreWarnings.txt); known externally caused
errors: see the known issue below.Date 2026-09-01 (publication date of the guide; the RC package was released in the package registry on 2026-08-28)
de.gematik.isik 6.0.0); updated
dependencies de.basisprofil.r4 1.6.0, hl7.terminology.r4 7.1.0;
hl7.fhir.uv.extensions.r4 5.2.0 now declared explicitlyadvisor.json added for the validator pipeline,
quality-control rules updatedMII_EX_Dokument_NLP_Processing_Status itself has already been included,
unchanged in content, since 2026.0.1): new example
AmandaAlzheimerKlartextDokument as a plain-text extraction step; the
original document now provided as DOCX
(application/vnd.…wordprocessingml.document) instead of text/plain;
processing-status codes along the pipeline corrected
(annotated/preprocessed/surrogated per the illustration, instead of
uniformly deid); the transforms chaining of the pipeline steps updatedhttp://snomed.info/sct/900000000000207008/version/20260701surrogated concept
clarified; the CodeSystem's title corrected ("MII CS Dokument …" instead of
the erroneous "MII VS Dokument …")MII_LM_Dokument is now shipped with the package (status
draft → active; it had previously been excluded by the package build
filter)The MII_PR_Dokument_Dokument profile, the extension and the
CapabilityStatement are unchanged in content compared to 2026.0.1.
Known Issue: 2 validation errors on examples with
context.event(eventCodeList expansion, an upstream bug inde.ihe-d.terminology 3.0.1) — see Issue #33
Date 2026-03-11
Date 2025-12-10