HL7 BE Laboratory WG Implementation Guide
1.0.1 - STU
HL7 BE Laboratory WG Implementation Guide, published by eHealth Platform. This guide is not an authorized publication; it is the continuous build for version 1.0.1 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/hl7-be/lab/ and changes regularly. See the Directory of published versions
| Official URL: https://www.ehealth.fgov.be/standards/fhir/lab/ValueSet/be-vs-coded-annotation-types | Version: 1.0.1 | |||
| Active as of 2026-01-23 | Maturity Level: 1 | Computable Name: BeVSCodedAnnotationTypes | ||
Value Set for specific types of coded annotations
References
https://www.ehealth.fgov.be/standards/fhir/lab/CodeSystem/be-cs-coded-annotation-types version 📦1.0.1
Expansion performed internally based on codesystem Coded Annotation Type Codes v1.0.1 (CodeSystem)
This value set contains 3 concepts
| System | Code | Display (en) | Definition | JSON | XML |
https://www.ehealth.fgov.be/standards/fhir/lab/CodeSystem/be-cs-coded-annotation-types | lab-test-accreditation | Laboratory Test Accreditation | Test disclaimer with the report | ||
https://www.ehealth.fgov.be/standards/fhir/lab/CodeSystem/be-cs-coded-annotation-types | lab-test-subcontractor | Laboratory Test subcontractor | Laboratory Test subcontractor | ||
https://www.ehealth.fgov.be/standards/fhir/lab/CodeSystem/be-cs-coded-annotation-types | lab-referencerange-comment | Comment on laboratory reference range | Comment on reference range |
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 |