HL7 FHIR Implementation Guide: Transversal Clinical Core
1.2.0 - STU1 Belgium flag

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

ValueSet: BeVSDiabetesObservationStatus

Official URL: https://www.ehealth.fgov.be/standards/fhir/core-clinical/ValueSet/be-vs-diabetes-observation-status Version: 1.2.0
Draft as of 2024-11-22 Computable Name: BeVSDiabetesObservationStatus

Values to be used in the status of Diabetes observations

References

Logical Definition (CLD)

Generated Narrative: ValueSet be-vs-diabetes-observation-status

  • Include these codes as defined in http://hl7.org/fhir/observation-status
    CodeDisplayDefinition
    finalFinalThe observation is complete and there are no further actions needed. Additional information such "released", "signed", etc would be represented using [Provenance](provenance.html) which provides not only the act but also the actors and dates and other related data. These act states would be associated with an observation status of `preliminary` until they are all completed and then a status of `final` would be applied.
    entered-in-errorEntered in ErrorThe observation has been withdrawn following previous final release. This electronic record should never have existed, though it is possible that real-world decisions were based on it. (If real-world activity has occurred, the status should be "cancelled" rather than "entered-in-error".).

 

Expansion

Generated Narrative: ValueSet

Expansion based on codesystem ObservationStatus v4.0.1 (CodeSystem)

This value set contains 2 concepts

CodeSystemDisplayDefinition
  finalhttp://hl7.org/fhir/observation-statusFinal

The observation is complete and there are no further actions needed. Additional information such "released", "signed", etc would be represented using Provenance which provides not only the act but also the actors and dates and other related data. These act states would be associated with an observation status of preliminary until they are all completed and then a status of final would be applied.

  entered-in-errorhttp://hl7.org/fhir/observation-statusEntered in Error

The observation has been withdrawn following previous final release. This electronic record should never have existed, though it is possible that real-world decisions were based on it. (If real-world activity has occurred, the status should be "cancelled" rather than "entered-in-error".).

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