MII Implementation Guide Microbiology
2027.0.0-ballot2 -
Germany
MII Implementation Guide Microbiology
2027.0.0-ballot2 -
Germany
MII Implementation Guide Microbiology - Local Development build (v2027.0.0-ballot2) built by the FHIR (HL7® FHIR® Standard) Build Tools. See the Directory of published versions
This ImplementationGuide resource defines the technical details of this publication, including dependencies and publishing parameters.
This is an R4 IG. None of the features it uses are changed in R4B, so it can be used as is with R4B systems. Packages for both R4 (de.medizininformatikinitiative.kerndatensatz.mikrobiologie.r4) and R4B (de.medizininformatikinitiative.kerndatensatz.mikrobiologie.r4b) are available.
This IG contains the following dependencies on other IGs.
Package hl7.fhir.uv.extensions.r4#5.2.0 This IG defines the global extensions - the ones defined for everyone. These extensions are always in scope wherever FHIR is being used (built Mon, Feb 10, 2025 21:45+1100+11:00) |
Package hl7.fhir.uv.extensions.r4#5.3.0 This IG defines the global extensions - the ones defined for everyone. These extensions are always in scope wherever FHIR is being used (built Sat, May 16, 2026 18:32+1000+10:00) |
Package hl7.fhir.uv.crmi#2.0.0 This implementation guide defines profiles, operations, capability statements and guidance to facilitate the content management lifecycle for authoring, publishing, distribution, and implementation of FHIR knowledge artifacts such as value sets, profiles, libraries, rules, and measures. The guide is intended to be used by specification and content implementation guide authors as both a dependency for validation of published artifacts, and a guide for construction and publication of content. (built Thu, Jul 2, 2026 00:17+1000+10:00) |
Package de.medizininformatikinitiative.kerndatensatz.meta#2027.0.0-ballot The Meta module contains foundational artifacts used by all other MII implementation guides. (built Thu, Sep 10, 2026 12:37+0000+00:00) |
Package hl7.fhir.uv.ipa#1.1.0 This IG describes how an application acting on behalf of a patient can access information about the patient from an clinical records system using a FHIR based API. The clinical records system may be supporting a clinical care provider (e.g. a hospital, or a general practitioner), or a health data exchange, including a national health record system. (built Wed, Mar 19, 2025 14:34+0000+00:00) |
Package de.medizininformatikinitiative.kerndatensatz.laborbefund#2027.0.0-ballot Medizininformatik Initiative - Modul Labor |
Package hl7.fhir.uv.xver-r5.r4#0.1.0 Extensions for Using Data Elements from FHIR R5 in FHIR R4 (built Fri, Mar 20, 2026 15:40+1100+11:00) |
Package de.basisprofil.r4#1.6.0 Projekt Basisprofilierung R4 (HL7 Deutschland e.V.) |
Package eu.miabis.r4#1.3.0 Minimum Information About BIobank data Sharing |
Package hl7.fhir.eu.extensions.r4#1.3.0 This guide lists the extensions specified for the European REALM. (built Fri, Mar 27, 2026 19:47+0100+01:00) |
Package ihe.pharm.mpd.r4#1.0.0-comment-2 ImplementationGuide for IHE Pharmacy Medication Prescription and Dispense (MPD) profile (built Tue, May 27, 2025 16:32+0200+02:00) |
Package hl7.fhir.eu.base#2.0.0 This guide collects base and core profiles to be used in the European context. It also includes common artifacts, such as the profiles describing the European Health Insurance Card. (built Mon, Apr 27, 2026 22:40+0300+03:00) |
Package hl7.fhir.eu.laboratory#2.0.0 This guide describes how the Laboratory Report can be represented in the European REALM. (built Tue, May 5, 2026 16:28+0200+02:00) |
Package de.medizininformatikinitiative.kerndatensatz.biobank#2027.0.0-ballot FHIR profiles for representing biospecimen data in biobanks - specimens, collections, cell lines and organoids - as part of the MII core data set. (built Fri, Sep 11, 2026 09:23+0000+00:00) |
Package hl7.fhir.uv.tools.r4#1.1.2 This IG defines the extensions that the tools use internally. Some of these extensions are content that are being evaluated for elevation into the main spec, and others are tooling concerns (built Tue, Mar 24, 2026 11:13+1100+11:00) |
Where the versions come from. Every package in the table is pinned directly in
sushi-config.yaml(dependencies:) — includinghl7.terminology.r4(THO) andhl7.fhir.uv.extensions.r4, and those two deliberately so: the IG Publisher's automatic-packages rule consults only this guide's own dependency list, so without a direct pin every build would silently inject the latest THO/extensions release — a version pinned by the MII meta package alone cannot control the build (verified in the publisher source at the pinned release). A weekly check warns when these two pins drift from what the pinned meta package ships, and the exact versions a concrete build used are recorded in itsqa-versions.jsonoutput.
This IG declares the following global profiles — profiles that apply to every instance of their resource type exchanged under this guide. An empty table means this module declares none.
There are no Global profiles defined
This publication includes IP covered under the following statements.
Expansion parameters are query parameters that can be passed to a ValueSet
$expand operation to control how the ValueSet is expanded — that is, how the
full list of codes is generated from the ValueSet definition. The
IG Parameters
used for this IG are declared in
sushi-config.yaml
(parameters:). A module that pins its expansion parameters through a CRMI
manifest additionally links the generated Parameters resource from here (see
the commented manifest blocks in sushi-config.yaml and the Metadata Overview
page, if the module keeps it).
