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

## Artifacts Summary

This page provides a list of the FHIR artifacts defined as part of this implementation guide.

### Laboratory Report examples

Specific examples made for the Belgian laboratory report.

antibiogramAsBundleNN |
antibiogramIsNegativeAsBundleCollection |
Detailed structure of fragment of creatinine panel. | Detailed structure of fragment of creatinine panel.(Note this example only concerns the Observation structure, a laboratory report SHALL be send leveraging the diagnosticReport resource that uses this Observation to express its results.)
Detailed structure of panel that uses qualifiers. | Details how to structure a panel using qualifiers.(Note this example only concerns the Observation structure, a laboratory report SHALL be send leveraging the diagnosticReport resource that uses this Observation to express its results.)
hematologyStudiesAsFHIRDocument |

### Structures: Resource Profiles

These define constraints on FHIR resources for systems conforming to this implementation guide.

BeLaboratoryReport | Belgian profile for a laboratory report
BeLaboratoryreportComposition | Belgian profile for a composition - to use when a laboratory report is sent as FHIR Document
BeObservationLaboratory | Belgian profile for an observation in a laboratory report
BeSpecimenLaboratory | Belgian profile for a specimen in a laboratory report. In some laboratory reports, specimen information is allowed to be minimal as many informations concerning the specimen are implied by the observations done.

### Structures: Data Type Profiles

These define constraints on FHIR data types for systems conforming to this implementation guide.

Coded Annotation | Annotation DataType with added CodeableConcept extension element

### Structures: Extension Definitions

These define constraints on FHIR data types for systems conforming to this implementation guide.

Annotation Code | Codifies the content of an Annotation
BeExtNote | BeExtNote
Comment extension for ReferenceRange | Extension that adds a comment to Observation.ReferenceRange

### Terminology: Value Sets

These define sets of codes used by systems conforming to this implementation guide.

Coded Annotation Types | Value Set for specific types of coded annotations

### Terminology: Code Systems

These define new code systems used by systems conforming to this implementation guide.

CodeSystem Albert | This code system is to identify Albert code
Coded Annotation Type Codes | Code System for specific types of coded annotations

### Terminology: Naming Systems

These define identifier and/or code system identities used by systems conforming to this implementation guide.

BELAC Accreditation | BELAC Accreditation
Lab Report Bundle Id | Unique Identifier for Lab Report Bundle
Lab Report Diagnostic Report Id | Unique Identifier for Lab Report Diagnostic Reports
Retam code (Belgian subset of LOINC + Albert Code) | Retam code (Belgian subset of LOINC + Albert Code)

### Example: Example Instances

These are example instances that show what data produced and consumed by systems conforming with this implementation guide might look like.

antibiogramAsBundleCollection
bundle-2-reports-2-patients
hematologyStudiesAsBundleCollection
some-id

### Other

These are resources that are used within this implementation guide that do not fit into one of the other categories.

eHealthPlatform
obsDynamic0
obsDynamic1
obsDynamic2
obsKetonen
obsMagnesium
obsUrineIonen
obsUrineScreening
obsUrobili
organization1
practitioner10
practitionerrole1
urine1