This page is part of the MII Implementation Guide Consent (v2027.0.0-ballot: Release) 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

Code Systems

CodeSystems

This page describes the CodeSystems of the Consent module. The ValueSets built on top of them are described on the ValueSets page.

Important: CodeSystem resources of external terminologies (e.g. ICD-10-GM, OPS, SNOMED CT) are not published in this module; they are obtained from the central KDS terminology server (SU-TermServ): https://mii-termserv.de/.

MII CS Consent Version and Modules

Codes for the Broad Consent versions and additional modules (urn:oid:2.16.840.1.113883.3.1937.777.24.5.27): see the artifact page mii-cs-consent-version-modules.

MII_CS_Consent_Answer

Answer codes (urn:oid:2.16.840.1.113883.3.1937.777.24.5.2): see the artifact page MII_CS_Consent_Answer.

MII CS Consent Policy

Consent resource and provision levels

The Consent resource allows a refinement of consent.provision, in that consent.provision can itself again contain a provision. In this IG, this refinement in Consent resources is restricted to 2 levels. Level 1 (consent.provision) is set to DENY in accordance with the opt-out model (consent.provision.type=DENY). This specifies that initially EVERYTHING is prohibited (per the opt-in approach). Level 2 of the Consent resource, consent.provision.provision, is the refinement of the level 1 provisions and can now add permissions in a targeted way. For level 2 provisions within the Consent resource, the policies from the following CodeSystem MII CS Consent Policy are used.

Example:

<provision> <!-- Level 1 Provision steht auf 'deny' -->
  <type value="deny" />
  <period>
    <start value="2020-09-01" />
    <end value="2050-08-31" />
  </period>
  <provision> <!-- Level 2 Provision steht auf 'permit' -->
    <type value="permit" />
    <period>
      <start value="2020-09-01" />
      <end value="2025-08-31" />
    </period>
    <code>
      <coding>
        <system value="urn:oid:2.16.840.1.113883.3.1937.777.24.5.3" />
        <code value="2.16.840.1.113883.3.1937.777.24.5.3.6" />
        <display value="MDAT_erheben" />
      </coding>
    </code>
  </provision>
</provision>

Policy CodeSystem and its level entries ("Lvl") for modules and policies

As can be seen in the following table, the CodeSystem MII CS Consent Policy is likewise structured in 2 levels: CodeSystem level 1 (Lvl=1) represents the modules and thus the questions in the Broad Consent.

Example:

CodeSystem level 2 (Lvl=2) represents the semantic policies of the MII Broad Consent. Policies allow a fine-grained differentiation of permissions within a module.

Example:

In the Consent resource, only the policy entries (Lvl=2) may be used in consent.provision.provision (level 2 provisions)!

Notes on use in withdrawals and partial withdrawals

To implement withdrawals or partial withdrawals, the corresponding policies must be set to DENY by means of the level 2 provisions (consent.provision.provision). For example, collection (.6) can be prohibited while storage and use (.8) remain unaffected ("MDAT erheben"="DENY", but "MDAT wissenschaftlich nutzen"="PERMIT").

Notes on policies with _status "deprecated/inactive"

Policies that have the status "deprecated/inactive" in the following table shall no longer be added to newly created Consent resources in the future. These policies should also no longer be evaluated in the future (enforcement).

This code system urn:oid:2.16.840.1.113883.3.1937.777.24.5.3 contains the following codes: