CH EMS (R4)
1.9.0-cibuild - ci-build
CH EMS (R4)
1.9.0-cibuild - ci-build
CH EMS (R4), published by IVR Interverband für Rettungswesen. This guide is not an authorized publication; it is the continuous build for version 1.9.0-cibuild built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/hl7ch/ch-ems/ and changes regularly. See the Directory of published versions
| Official URL: http://fhir.ch/ig/ch-ems/ValueSet/yes-no-unknown | Version: 1.9.0-cibuild | |||
| Active as of 2020-05-25 | Computable Name: YesNoUnknown | |||
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. |
||||
The SNOMED CT codes to answer yes/no/unknown
References
Generated Narrative: ValueSet yes-no-unknown
http://snomed.info/sct| Code | Display |
| 373066001 | Yes (qualifier value) |
| 373067005 | No (qualifier value) |
| 261665006 | Unknown (qualifier value) |
Generated Narrative: ValueSet
Expansion based on SNOMED CT International edition 01-Aug 2024
This value set contains 3 concepts
| Code | System | Display |
| 373066001 | http://snomed.info/sct | Yes (qualifier value) |
| 373067005 | http://snomed.info/sct | No (qualifier value) |
| 261665006 | http://snomed.info/sct | Unknown |
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 |