Practitioner & PractitionerRole

***Erstveröffentlichung der FHIR-Profile für die strukturierte digitale Darstellung des Entlassungsberichts aus stationärer Behandlung (DAV/VAV/SAV)*** Hierbei handelt es sich um eine Version für das "Kommentierungsverfahren DGUV-Entlassungsbericht aus stationärer Behandlung (F2102) V 0.0.2-Kommentierung". Die Profile sind noch nicht final und können im Rahmen des Kommentierungsverfahrens noch angepasst werden. --- **Allgemeine Hinweise** Eine formlose E-Mail an [ballot@hl7.de](mailto:ballot@hl7.de) als Anmeldung zum Kommentierungsverfahrens ist erforderlich. Die Kommentare bitten wir über das [Ballotierungsportal](https://hl7germany.atlassian.net/servicedesk/customer/portals) von HL7 Deutschland einzureichen. Wichtige Zeitangaben: + Eröffnung des Kommentierungsverfahrens: 1. Juli 2025 + Schließen des Kommentierungsverfahrens: 10. August 2025 + Anschließend: Besprechung und Auflösung der eingegangenen Kommentare Für Fragen steht Ihnen die Kontaktperson bei der DGUV, [Frau Sanja Berger](mailto:Sanja.Berger@dguv.de) zur Verfügung.

Die modulspezifischen Release Notes von ISiK finden Sie in den Implementierungsleitfäden. **Full Changelog**: https://github.com/gematik/spec-ISiK-Basismodul/compare/v.4.0.0...v.5.0.0

- CareConnect-GPC-Practitioner-1.name.family - cardinality is now 0..1 - CareConnect-GPC-MedicationRequest-1 - now present in package

Releasekandidat 1.3.0-RC.1 för FHIR NLL IG.

**PackageVersion 1.4.2** - GKVSV_PR_TA7_Rechnung_Bundle - identifier.value Constraint Dateiname erweitert. Die Absenderklassifikation (B|C|D) wurde um die Werte K und R erweitert => B|C|D|K|R - GKVSV_PR_TA7_Rechnung_List - entry.item.identifier.value Constraint Dateiname erweitert. Die Absenderklassifikation (B|C|D) wurde um die Werte K und R erweitert => B|C|D|K|R **PackageVersion 1.4.1** - GKVSV_PR_TA7_Rechnung_Bundle - Bundle.identifier.value: Constraint "Dateiname" verbietet jetzt den Zähler ...000 und den Zähler X00FHRNN000 - GKVSV_PR_TA7_Rechnung_List - List.entry.item.identifier.value: Constraint "Dateiname" verbietet jetzt den Zähler ...000 und den Zähler X00FHRNN000 **PackageVersion 1.4.0** - GKVSV_PR_TA7_Rechnung_Bundle - Constraint "dname-1" hinzugefügt. Dieser prüft, ob der eigene Dateiname in der TA7_Rechnung_List enthalten ist - bundle.type auf "document" gesetzt

* Dependencies * Increased de.basisprofil.r4 to 1.5.4 * CapabilityStatement * Fixed SHALL and SHOULD flags

1.20

## Release 1.5.2 (2025-06-23) - Fix discriminator for Task.extension ## Release 1.5.1 (2025-06-17) - update ePA Medication (1.0.6-2) and ePA Terminology (1.0.5-4) dependencies. This reverts the name of the "is Vaccine Extension" to `medication-id-vaccine-extension` ## Release 1.5.0 (2025-04-10) ### Breaking Changes - `breaking-change` new meta.profile Version 1.5 - `breaking-change` new dependencies: - de.basisprofil.r4 - de gematik.epa.medication - de gematik.terminology ### Profile Changes - `new profile` GEM_ERP_PR_Communication_DiGA, used by Health Care Provider to interact with Patient concerning DiGA Prescriptions - `retired profile` retired GEM_ERP_PR_Communication_InfoReq as it is not allowed - `removed` Removed $create and $activate Input Parameter Profiles and in OperationDefinitions - `removed` EPADosage for GEM_ERP_PR_Medication.dosageInstruction - `added` Add Flag for Task to identify a Task redeemable in the EU ### Terminology Changes - `removed` Removed unused GEM_ERP_VS_PerformerType - `removed` Removed unused Code in GEM_ERP_CS_DocumentType ### Changed - `changed` Remove Dependency for KBV Packages - `changed` Add Must Supports in GEM_ERP_PR_Medication

This beta release introduces the following changes: * [ZIBFHIR-318](http://bits.nictiz.nl/browse/ZIBFHIR-318): In profiles zib-LegalSituation-LegalStatus and zib-LegalSituation-Representation, an indirect mapping is added on Condition.clinicalStatus to zib concepts DateStart and DateStop, with guidance on howto map this to the proper status. * [ZIBFHIR-310](http://bits.nictiz.nl/browse/ZIBFHIR-310): In zib-AdvanceDirective,: * the mapping to the living will document has been moved from the `Consent.sourceAttachment.data` element to `Consent.sourceAttachment` itself. * the guidance on `Consent.status` that normally only _active_ resources are exchanged has been removed. * [ZIBFHIR-304](http://bits.nictiz.nl/browse/ZIBFHIR-304): The “pattern” data type profiles for references to zib HealthProfessional have been be removed. Their functionality (adding the proper comment) has been replaced by guidance in the profiling guidelines and a QA check. * [ZIBFHIR-301](http://bits.nictiz.nl/browse/ZIBFHIR-301): Pulse Rate regularity and frequency are now profiled independently within distinct Observation profiles. A new panel Observation establishes a link between these related concepts using a .hasMember relation. * [ZIBFHIR-239](http://bits.nictiz.nl/browse/ZIBFHIR-239): The profile and related resources for zib AbilityToPerformMouthcareActivities have been published. * [ZIBFHIR-235](http://bits.nictiz.nl/browse/ZIBFHIR-235): In profile zib-NutritionAdvice, a validation error is solved by a technical fix. * [ZIBFHIR-229](http://bits.nictiz.nl/browse/ZIBFHIR-229): In profile zib-SNAQScore, the definition text of {{.value[x]}} about the range has been adjusted according to the erratum of this zib. * [ZIBFHIR-227](http://bits.nictiz.nl/browse/ZIBFHIR-227): The reference to Wound on DeviceUseStatement.reasonReference is moved from the zib-MedicalDevice profile to zib-Wound.Drain. * [ZIBFHIR-220](http://bits.nictiz.nl/browse/ZIBFHIR-220): The examples of profile nl-core-Mobility have been adjusted so that the individual parts of this zib are distinct Observations instead of Observation.components. * [ZIBFHIR-212](http://bits.nictiz.nl/browse/ZIBFHIR-212): In zib-MedicalDevice, the references have been removed on `.reasonReference` to zib-BowelFunction, zib-VisualFunction, zib-HearingFunction, zib-FunctionalOrMentalStatus and zib-Mobility, because there's no causual relationship between this zibs. In all these profiles, add the extension workflow-supportingInfo to refer zib-MedicalDevice. * [ZIBFHIR-209](http://bits.nictiz.nl/browse/ZIBFHIR-209): Code NullFlavor/OTH has been added to ProductTypeCodelijst of zib MedischHulpmiddel. * [ZIBFHIR-203](http://bits.nictiz.nl/browse/ZIBFHIR-203): The profile and related resources for zib TreatmentObjective have been published. * [ZIBFHIR-200](http://bits.nictiz.nl/browse/ZIBFHIR-200): The constraints from zib MUSTScore have been added to the zib-MUSTScore profile. * [ZIBFHIR-192](http://bits.nictiz.nl/browse/ZIBFHIR-192): Where zibs (2020 and 2024) create a derived zib where a _required_ bound value set from the base is restricted but gets an _extensible_ binding, the resulting FHIR profile now interprets this as a minimum additional binding. This has been documented in the profiling guidelines and the existing zib2020 profiles have been adjusted accordingly. * [ZIBFHIR-182](http://bits.nictiz.nl/browse/ZIBFHIR-182): In profile zib-FeedingPatternInfant, data type string has been changed to CodeableConcept on the component feedingSupplement to allow for the exchange of coded feeding supplements as well. The cardinality of the component has been changed from 0..1 to 0..* and the comment refers to the relevent value set of Geboortezorg. Finally, guidance has been added regarding this deviation from the zib. * [ZIBFHIR-179](http://bits.nictiz.nl/browse/ZIBFHIR-179): The zib concept InterpretationHeartRate in zib HeartRate has been moved from a distinct Observation profile to Observation.interpretation in the zib-HeartRate profile. * [ZIBFHIR-163](http://bits.nictiz.nl/browse/ZIBFHIR-163): In profile zib-NutritionAdvice, it has been made possible to accommodate the zib string “Consistency” as structured data. Guidance has been added for receiving systems on how to reconstruct this zib string from the structured data. * [ZIBFHIR-162](http://bits.nictiz.nl/browse/ZIBFHIR-162): The profile for zib Visus (including the erratum) is published in the beta package. * [ZIBFHIR-131](http://bits.nictiz.nl/browse/ZIBFHIR-131): Mapping declarations to the zibs have been added to the nl-core profiles where they were missing. This ensures that the mappings to the zibs in the nl-core profiles will be visible on Simplifier. * [ZIBFHIR-65](http://bits.nictiz.nl/browse/ZIBFHIR-65): The profile zib-Pregnancy has been moved from the Condition to the Observation resource.

This beta release introduces the following changes: * [ZIBFHIR-318](http://bits.nictiz.nl/browse/ZIBFHIR-318): In profiles zib-LegalSituation-LegalStatus and zib-LegalSituation-Representation, an indirect mapping is added on Condition.clinicalStatus to zib concepts DateStart and DateStop, with guidance on howto map this to the proper status. * [ZIBFHIR-310](http://bits.nictiz.nl/browse/ZIBFHIR-310): In zib-AdvanceDirective,: * the mapping to the living will document has been moved from the Consent.sourceAttachment.data element to Consent.sourceAttachment itself. * the guidance on Consent.status that normally only _active_ resources are exchanged has been removed. * [ZIBFHIR-304](http://bits.nictiz.nl/browse/ZIBFHIR-304): The "pattern" data type profiles for references to zib HealthProfessional have been be removed. Their functionality (adding the proper comment) has been replaced by guidance in the profiling guidelines and a QA check. * [ZIBFHIR-301](http://bits.nictiz.nl/browse/ZIBFHIR-301): Pulse Rate regularity and frequency are now profiled independently within distinct Observation profiles. A new panel Observation establishes a link between these related concepts using a .hasMember relation. * [ZIBFHIR-239](http://bits.nictiz.nl/browse/ZIBFHIR-239): The profile and related resources for zib AbilityToPerformMouthcareActivities have been published. * [ZIBFHIR-235](http://bits.nictiz.nl/browse/ZIBFHIR-235): In profile zib-NutritionAdvice, a validation error is solved by a technical fix. * [ZIBFHIR-229](http://bits.nictiz.nl/browse/ZIBFHIR-229): In profile zib-SNAQScore, the definition text of .value[x] about the range has been adjusted according to the erratum of this zib. * [ZIBFHIR-227](http://bits.nictiz.nl/browse/ZIBFHIR-227): The reference to Wound on DeviceUseStatement.reasonReference is moved from the zib-MedicalDevice profile to zib-Wound.Drain. * [ZIBFHIR-212](http://bits.nictiz.nl/browse/ZIBFHIR-212): In zib-MedicalDevice, the references have been removed on .reasonReference to zib-BowelFunction, zib-VisualFunction, zib-HearingFunction, zib-FunctionalOrMentalStatus and zib-Mobility, because there's no causual relationship between this zibs. In all these profiles, add the extension workflow-supportingInfo to refer zib-MedicalDevice. * [ZIBFHIR-209](http://bits.nictiz.nl/browse/ZIBFHIR-209): Code NullFlavor/OTH has been added to ProductTypeCodelijst of zib MedischHulpmiddel. * [ZIBFHIR-203](http://bits.nictiz.nl/browse/ZIBFHIR-203): The profile and related resources for zib TreatmentObjective have been published. * [ZIBFHIR-200](http://bits.nictiz.nl/browse/ZIBFHIR-200): The constraints from zib MUSTScore have been added to the zib-MUSTScore profile. * [ZIBFHIR-192](http://bits.nictiz.nl/browse/ZIBFHIR-192): Where zibs (2020 and 2024) create a derived zib where a _required_ bound value set from the base is restricted but gets an _extensible_ binding, the resulting FHIR profile now interprets this as a minimum additional binding. This has been documented in the profiling guidelines and the existing zib2020 profiles have been adjusted accordingly. * [ZIBFHIR-182](http://bits.nictiz.nl/browse/ZIBFHIR-182): In profile zib-FeedingPatternInfant, data type string has been changed to CodeableConcept on the component feedingSupplement to allow for the exchange of coded feeding supplements as well. The cardinality of the component has been changed from 0..1 to 0..* and the comment refers to the relevent value set of Geboortezorg. Finally, guidance has been added regarding this deviation from the zib. * [ZIBFHIR-179](http://bits.nictiz.nl/browse/ZIBFHIR-179): The zib concept InterpretationHeartRate in zib HeartRate has been moved from a distinct Observation profile to Observation.interpretation in the zib-HeartRate profile. * [ZIBFHIR-163](http://bits.nictiz.nl/browse/ZIBFHIR-163): In profile zib-NutritionAdvice, it has been made possible to accommodate the zib string “Consistency” as structured data. Guidance has been added for receiving systems on how to reconstruct this zib string from the structured data. * [ZIBFHIR-162](http://bits.nictiz.nl/browse/ZIBFHIR-162): The profile for zib Visus (including the erratum) is published in the beta package. * [ZIBFHIR-160](http://bits.nictiz.nl/browse/ZIBFHIR-160): In the CodeSystem resources, the description of property _inactive_ has been adjusted to the description from the HL7 code system. * [ZIBFHIR-65](http://bits.nictiz.nl/browse/ZIBFHIR-65): The profile zib-Pregnancy has been moved from the Condition to the Observation resource.

# 2025-06-23 Release notes This package contains the FHIR artifacts conforming to Mitz specifications 3.8+. This package was originally published as version 0.1.1-beta, but it turned out that package was incomplete and did not reflect the version of the Mitz specification. This package should be a drop-in replacement of version 0.1.1-beta.

Updates to Patient Profile, Extensions and ValueSets