This page is part of the MII Implementation Guide Symptom (v2027.0.0-ballot: 2027 Ballot 1) based on FHIR (HL7® FHIR® Standard) R4. This is the current published version. For a full list of available versions, see the Directory of published versions

MII ImplementationGuide Resource

This ImplementationGuide resource defines the technical details of this publication, including dependencies and publishing parameters.

• XML
• JSON

Cross Version Analysis

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.symptom.r4) and R4B (de.medizininformatikinitiative.kerndatensatz.symptom.r4b) are available.

IG Dependencies

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 de.basisprofil.r4#1.6.0 Projekt Basisprofilierung R4 (HL7 Deutschland e.V.)

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 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.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:) — including hl7.terminology.r4 (THO) and hl7.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 its qa-versions.json output.

Global Profiles

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

Copyrights

This publication includes IP covered under the following statements.

• ISO maintains the copyright on the country codes, and controls its use carefully. For further details see the ISO 3166 web page: https://www.iso.org/iso-3166-country-codes.html
  Show Usage
  • ISO 3166-1 Codes for the representation of names of countries and their subdivisions — Part 1: Country code: MII_CPS_Symptom_CapabilityStatement, MII_IG_Symptom, MII_LM_Symptom, MII_PR_Symptom_Condition and MII_PR_Symptom_Observation
• This material contains content from LOINC. LOINC is copyright © 1995-2020, Regenstrief Institute, Inc. and the Logical Observation Identifiers Names and Codes (LOINC) Committee and is available at no cost under the license. LOINC® is a registered United States trademark of Regenstrief Institute, Inc.
  Show Usage
  • LOINC: Observation/mii-exa-symptom-arachnodactyly and Observation/mii-exa-symptom-chestpain
• This material contains content that is copyright of SNOMED International. Implementers of these specifications must have the appropriate SNOMED CT Affiliate license - for more information contact https://www.snomed.org/get-snomed or info@snomed.org.
  Show Usage
  • SNOMED Clinical Terms® (SNOMED CT®): Condition/mii-exa-symptom-vitreoretinochoroidopathy, MII_PR_Symptom_Condition, MII_PR_Symptom_Observation and Observation/mii-exa-symptom-chestpain
• This material derives from the HL7 Terminology (THO). THO is copyright ©1989+ Health Level Seven International and is made available under the CC0 designation. For more licensing information see: https://terminology.hl7.org/license.html
  Show Usage
  • Condition Clinical Status Codes: Condition/mii-exa-symptom-vitreoretinochoroidopathy
  • ConditionVerificationStatus: Condition/mii-exa-symptom-vitreoretinochoroidopathy

IG Parameter Settings and Expansion Parameters

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).