IKNL PZP STU3
1.0.0-rc2 - consultation
This page is part of the Advance Care Planning (PZP) (v1.0.0-rc2: Release 1) based on FHIR (HL7® FHIR® Standard) R3. No current official version has been published yet. For a full list of available versions, see the Directory of published versions
| Official URL: https://api.iknl.nl/docs/pzp/stu3/ValueSet/ACP-ContactPersonRole | Version: 1.0.0-rc2 | |||
| Draft as of 2026-03-03 | Computable Name: ContactPersonRoleVS | |||
Copyright/Legal: Copyright and related rights waived via CC0, https://creativecommons.org/publicdomain/zero/1.0/. This does not apply to information from third parties, for example a medical terminology system. The implementer alone is responsible for identifying and obtaining any necessary licenses or authorizations to utilize third party IP in connection with the specification or otherwise. |
||||
ValueSet containing additional codes to the ContactPerson's RolCodelijst. These codes are applied from the zib2024 release onwards. Currently, the ValueSet contains only SNOMED CT code 310141000146103 (Schriftelijk gemachtigde zorg en behandeling / Holder of medical power of attorney) from the zib2024 release. The ValueSet is bound to a slice in `RelatedPerson.relationship.
References
This value set includes codes based on the following rules:
http://snomed.info/sct version Not Stated (use latest from terminology server)
| Code | Display |
| 310141000146103 | Schriftelijk gemachtigde zorg en behandeling |
No Expansion for this valueset (Unknown Code System)
Explanation of the columns that may appear on this page:
| Level | A few code lists that FHIR defines are hierarchical - each code is assigned a level. In this scheme, some codes are under other codes, and imply that the code they are under also applies |
| System | The source of the definition of the code (when the value set draws in codes defined elsewhere) |
| Code | The code (used as the code in the resource instance) |
| Display | The display (used in the display element of a Coding). If there is no display, implementers should not simply display the code, but map the concept into their application |
| Definition | An explanation of the meaning of the concept |
| Comments | Additional notes about how to use the code |