This page is part of the Belgium eHealth FHIR Core specifications (v1.2.2: Trial Use) based on FHIR R4. This is the current published version. For a full list of available versions, see the Directory of published versions
Summary
Defining URL: | https://www.ehealth.fgov.be/standards/fhir/ValueSet/be-vs-problem-category |
Version: | 1.2.2 |
Name: | BeVSProblemCategory |
Title: | Problem Category |
Status: | Active as of 2021-01-10T10:59:49+00:00 |
Definition: | Problem Category |
Publisher: | eHealth |
Source Resource: | XML / JSON / Turtle |
References
https://www.ehealth.fgov.be/standards/fhir/CodeSystem/be-cs-problem-category
This value set contains 7 concepts
Expansion based on Problem Category v1.2.2 (CodeSystem)
All codes from system https://www.ehealth.fgov.be/standards/fhir/CodeSystem/be-cs-problem-category
Code | Display | Definition |
diagnosis | Diagnosis | A disease identified from a clinical reasoning, based on pathological and physiological ascertainments |
problem | Problem | Identification of problems that the healthcare provider considers harmful, potentially harmful, and which may be the subject of further investigation or treatment |
risk | Risk | Identification of a health problem or situation that may require ongoing monitoring or management |
antecedent | Antecedent | Information about a problem that has been resolved |
congenital | Congenital anomaly | Congenital anomaly |
conclusion | Conclusion | Informations about a conclusion from anamnesis performed by a professional other than a physician |
other | Other | Other |
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 |
Source | 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 |