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

This page is part of the Advance Care Planning (PZP) (v1.0.0-rc3: Release 1) based on FHIR (HL7® FHIR® Standard) R4. No current official version has been published yet. For a full list of available versions, see the Directory of published versions

ValueSet: ACP Yes, No, Unknown Codes

Official URL: https://api.iknl.nl/docs/pzp/r4/ValueSet/ACP-YesNoUnknownVS Version: 1.0.0-rc3
Draft as of 2026-06-03 Computable Name: ACPYesNoUnknownVS

Copyright/Legal: This artefact includes content from SNOMED Clinical Terms® (SNOMED CT®) which is copyright of the International Health Terminology Standards Development Organisation (IHTSDO). Implementers of these artefacts must have the appropriate SNOMED CT Affiliate license - for more information contact http://www.snomed.org/snomed-ct/getsnomed-ct or info@snomed.org.

ValueSet representing 'Yes, No, Unknown' answers.

References

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 version 📍2018-08-12
    CodeDisplaySynonymNederlands (Nederland) (Dutch (Netherlands), nl)English (English, en)English (United States) (English (United States), en)
    UNKnog onbekendonbekendonbekend
  • Include these codes as defined in http://snomed.info/sct version Not Stated (use latest from terminology server)
    CodeDisplaySynonymNederlands (Nederland) (Dutch (Netherlands), nl)English (English, en)English (United States) (English (United States), en)
    373066001 ja bevestiging bevestiging Yes Yes
    373067005 nee neen neen No No

 

Expansion

Expansion from tx.fhir.org based on:

  • SNOMED CT Dutch edition 30-Sep 2024
  • codesystem v3 Code System NullFlavor version 2018-08-12

This value set contains 3 concepts

SystemCodeDisplay (en)DefinitionJSONXML
http://terminology.hl7.org/CodeSystem/v3-NullFlavor  UNKunknown

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:

                    
                       Those properties themselves directly translate to a semantic of "unknown".  (E.g. a local code sent as a translation that conveys 'unknown')
                       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.)
http://snomed.info/sct  373066001Yes
http://snomed.info/sct  373067005No

Description of the above table(s).