HL7 FHIR Implementation Guide: Transversal Clinical Core
1.2.0 - STU1
HL7 FHIR Implementation Guide: Transversal Clinical Core, published by eHealth Platform. This guide is not an authorized publication; it is the continuous build for version 1.2.0 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/hl7-be/core-clinical/ and changes regularly. See the Directory of published versions
Official URL: https://www.ehealth.fgov.be/standards/fhir/core-clinical/ValueSet/be-vs-diabetes-report-category | Version: 1.2.0 | |||
Draft as of 2024-11-22 | Computable Name: BeVSDiabetesReportCategory |
Values to be used in the categorisation of Diabetes reports
References
Generated Narrative: ValueSet be-vs-diabetes-report-category
http://snomed.info/sct
version http://snomed.info/sct/11000172109
Code | Display |
4311000179106 | Chemical pathology report (record artifact) |
408475000 | Diabetic medicine (qualifier value) |
394583002 | Endocrinology (qualifier value) |
Generated Narrative: ValueSet
Expansion based on SNOMED CT 11000172109 edition 15-Nov 2023
This value set contains 3 concepts
Code | System | Display | http://terminology.hl7.org/CodeSystem/designation-usage#display |
4311000179106 | http://snomed.info/sct | Chemical pathology report (record artifact) | Chemical pathology report |
408475000 | http://snomed.info/sct | Diabetic medicine (qualifier value) | Diabetic medicine |
394583002 | http://snomed.info/sct | Endocrinology (qualifier value) | endocrinologie |
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 |