Unattributed Code Systems

Copyright Fragment

This fragment is not visible to the reader

This publication includes IP covered under the following statements.

Copyright and Registered Trademark Uses

External References

Type Reference Content
web github.com IG © 2024+ koppelmij . Package fhir.gidsopenstandaarden.koppelmij#0.1.0 based on FHIR 4.0.1 . Generated 2026-05-08
Links: Table of Contents | QA Report
web nictiz.nl Each occurrence of the zib HealthProfessional is normally represented by two FHIR resources: a PractitionerRole resource (instance of nl-core-HealthProfessional-PractitionerRole ) and a Practitioner resource (instance of nl-core-HealthProfessional-Practitioner ). The Practitioner resource is referenced from the PractitionerRole instance. For this reason, sending systems should fill the reference to the PractitionerRole instance here, and not the Practitioner resource. Receiving systems can then retrieve the reference to the Practitioner resource from that PractitionerRole instance.
web nictiz.nl Each occurrence of the zib HealthProfessional is normally represented by two FHIR resources: a PractitionerRole resource (instance of nl-core-HealthProfessional-PractitionerRole ) and a Practitioner resource (instance of nl-core-HealthProfessional-Practitioner ). The Practitioner resource is referenced from the PractitionerRole instance. For this reason, sending systems should fill the reference to the PractitionerRole instance here, and not the Practitioner resource. Receiving systems can then retrieve the reference to the Practitioner resource from that PractitionerRole instance.
web decor.nictiz.nl The codes SHALL be taken from GeslachtCodelijst
( required to http://decor.nictiz.nl/fhir/ValueSet/2.16.840.1.113883.2.4.3.11.60.40.2.0.1.1--20200901000000 )
web decor.nictiz.nl Patient's administrative gender.
Binding: GeslachtCodelijst ( required )
web decor.nictiz.nl GeslachtCodelijst
http://decor.nictiz.nl/fhir/ValueSet/2.16.840.1.113883.2.4.3.11.60.40.2.0.1.1--20200901000000
web vzvz.nl In Koppeltaal wordt op de Task een custom extensie instantiates gebruikt om te verwijzen naar de ActivityDefinition. Het voorstel is om dezelfde extensie symmetrisch op de ServiceRequest toe te passen:
web vzvznl.github.io Zie de Memo: ServiceRequest als orkestratiemiddel voor de volledige analyse en de SMART Task-based Launch overwegingen voor vergelijking met het experimentele SMART Task-based Launch mechanisme.
web vzvznl.github.io Memo: ServiceRequest als orkestratiemiddel in KoppelMij

Internal Images

koppeltaal/optie0.png
koppeltaal/optie0.png
koppeltaal/optie1a.png
koppeltaal/optie1a.png
koppeltaal/optie1b.png
koppeltaal/optie1b.png
koppeltaal/optie2a.png
koppeltaal/optie2a.png
koppeltaal/optie2b.png
koppeltaal/optie2b.png
koppeltaal/optie3.png
koppeltaal/optie3.png
overview_koppelmij.svg
overview_koppelmij.svg
overview_optie_3a.png
overview_optie_3a.png
tree-filter.png
tree-filter.png