Advance Care Planning (PZP)
1.0.0-rc1 - trial-use

Advance Care Planning (PZP) - Downloaded Version 1.0.0-rc1 See the Directory of published versions

## ValueSet: Preferred Place Of Death

Official URL: https://api.iknl.nl/docs/pzp/r4/ValueSet/ACP-PreferredPlaceOfDeath | Version: 1.0.0-rc1
Draft as of 2025-10-30 | Computable Name: ACPPreferredPlaceOfDeathVS
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 for Preferred Place of Death, representing the place where the patient prefers to die, if possible.

References

- Preferred Place Of Death

### Logical Definition (CLD)

This value set includes codes based on the following rules:

- Include these codes as defined in `http://terminology.hl7.org/CodeSystem/v3-NullFlavor`

  Code | Display | Definition | Synonym | English (United States) (English (United States), en) | Nederlands (Nederland) (Dutch (Netherlands), nl)
  OTH | Anders | **Description:**The actual value is not a member of the set of permitted data values in the constrained value domain of a variable. (e.g., concept not provided by required code system). **Usage Notes**: This flavor and its specializations are most commonly used with the CD datatype and its flavors. However, it may apply to \*any\* datatype where the constraints of the type are tighter than can be conveyed. For example, a PQ that is for a true measured amount whose units are not supported in UCUM, a need to convey a REAL when the type has been constrained to INT, etc. With coded datatypes, this null flavor may only be used if the vocabulary binding has a coding strength of CNE. By definition, all local codes and original text are part of the value set if the coding strength is CWE. |  |  |
  UNK | Nog onbekend | **Description:**A proper value is applicable, but not known. **Usage Notes**: This means the actual value is not known. If the only thing that is unknown is how to properly express the value in the necessary constraints (value set, datatype, etc.), then the OTH or UNC flavor should be used. No properties should be included for a datatype with this property unless: 1. Those properties themselves directly translate to a semantic of "unknown". (E.g. a local code sent as a translation that conveys 'unknown') 2. Those properties further qualify the nature of what is unknown. (E.g. specifying a use code of "H" and a URL prefix of "tel:" to convey that it is the home phone number that is unknown.) |  |  |

- Include these codes as defined in `http://snomed.info/sct`

  Code | Display | Synonym | English (United States) (English (United States), en) | Nederlands (Nederland) (Dutch (Netherlands), nl)
  264362003 | thuis | thuis | Private dwelling | thuis
  22232009 | ziekenhuis | ziekenhuis | Hospital | ziekenhuis
  108344006 | verpleeghuis en/of locatie voor ambulante zorg | verpleeghuis en/of locatie voor ambulante zorg | Nursing home AND/OR ambulatory care site | verpleeghuis en/of locatie voor ambulante zorg
  284546000 | hospice | hospice | Hospice | hospice

### Expansion

No Expansion for this valueset (not supported by Publication Tooling)

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