bgz:Vissue-MSZ-392 Technical IG BgZ MSZ - Bewerkingsoverzicht

Daniel Püttmann: /* Boundaries and relationships */

2026-07-06T14:28:42Z

‎Boundaries and relationships

Daniel Püttmann: /* Mapping between profiles and dataset */ MSZ-392 Textual changes

2026-07-06T14:28:18Z

‎Mapping between profiles and dataset: MSZ-392 Textual changes

Daniel Püttmann: Clone of V2.0 production page for issue MSZ-392

2026-07-06T14:25:54Z

Clone of V2.0 production page for issue MSZ-392

Wijzigingen bekijken

← Oudere versie		Versie van 6 jul 2026 om 14:28
Regel 42:		Regel 42:

	* The Metadata building block is made independent of the zibs. Metadata contains data that relates to the registration process rather than the medical content. Exchange of metadata for the BgZ-MSZ is designed via a query add-on: BgZ-MSZ sections can be queried with or without metadata. When data with a specific section are exchanged, there may be metadata about the registration process that refer to instances within such a section. In the future, when more information standards use the Provenance resource to exchange registration data, it is planned to create an nl-core-MetaData profile that will replace the current bgz-MetaData profile.		* The Metadata building block is made independent of the zibs. Metadata contains data that relates to the registration process rather than the medical content. Exchange of metadata for the BgZ-MSZ is designed via a query add-on: BgZ-MSZ sections can be queried with or without metadata. When data with a specific section are exchanged, there may be metadata about the registration process that refer to instances within such a section. In the future, when more information standards use the Provenance resource to exchange registration data, it is planned to create an nl-core-MetaData profile that will replace the current bgz-MetaData profile.
−
−	~~== Relations between building blocks ==~~
−
−	~~<div class="center" style="width:auto; margin-left:auto; margin-right:auto;">~~
−	~~[[Bestand: ChaptersAndRelationsBgZ2 v1.png\|800px]]~~
−	~~</div>~~
−	~~<small><b>Figure 1.</b> Relations between building blocks.</small>~~

	== Mapping between profiles and dataset ==		== Mapping between profiles and dataset ==

@@ Regel 54: / Regel 54: @@
 Each FHIR profile maps to the functional definition in ART-DECOR. FHIR profiles contain mappings to all data elements that are present in the functional data set. Either zib mappings are used (e.g., NL-CM:17.2.1) or BgZ-MSZ-specific mappings are used with the prefix "bgz2017-dataelement-".
-Each transaction must contain a Patient building block. Therefore, a reference to a Patient resource conforming to the nl-core-Patient profile is expected in .subject or .patient of each FHIR instance of each main building block except for MetaData, Patient, HealthProvider.
+Each transaction must contain a Patient building block. Therefore, a reference to a Patient resource conforming to the nl-core-Patient profile is expected in .subject or .patient of each FHIR instance of each main building block except for MetaData, Patient, HealthCareProvider, and HealthProfessional.
 FHIR instances, exchanged as part of a transaction, will contain references to other instances. For example, a procedure may reference a problem list item. Implementers SHOULD use literal references (using .reference) instead of logical references (using .identifier) where possible; see the general FHIR IG on the Reference data type.