eHDSI Terminologies
0.1.0 - ci-build
eHDSI Terminologies, published by HL7 Europe. This guide is not an authorized publication; it is the continuous build for version 0.1.0 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/hl7-eu/EHDSI-Terminology-package/ and changes regularly. See the Directory of published versions
Official URL: http://terminology.ehdsi.eu/ValueSet/eHDSICodeProb | Version: 0.1.0 | |||
Draft as of 2024-11-29 | Computable Name: EHDSICodeProb | |||
Other Identifiers: OID:1.3.6.1.4.1.12559.11.10.1.3.1.42.23 |
The Value Set is used as an optional description of a problem in the patient Summary. It gives an information on the circumstances under which the problem was defined/discovered.
References
This value set is not used here; it may be used elsewhere (e.g. specifications and/or implementations that use this content)
Generated Narrative: ValueSet
Expansion based on SNOMED CT International edition 01-Aug 2024
This value set contains 7 concepts
Code | System | Display | Inactive |
55607006 | http://snomed.info/sct | Problem | |
282291009 | http://snomed.info/sct | Diagnosis interpretation | |
409586006 | http://snomed.info/sct | Complaint (finding) | inactive |
64572001 | http://snomed.info/sct | Disease | |
248536006 | http://snomed.info/sct | Skill and ability | inactive |
418799008 | http://snomed.info/sct | Finding reported by subject or history provider (finding) | |
404684003 | http://snomed.info/sct | Clinical finding (finding) |
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 |