Transaction: Laboratory result 2.0
General information
STATUS:
Published
OWNER:
eHealth Platform
STANDARD:
KMEHR with encapsulated FHIR
VERSION:
2.0
DATE:
2023-12-08
DEFINITION:
The Laboratory result transaction aims to transfer the results of examinations performed by the following medical specialties: laboratory, anatomopathology, genetics, bacteriology, molecular biology and toxicology.
This is the description of a minimal KMEHR transaction that can be processed by the current HUB/METAHUB system, and that contains a Lab Report FHIR resource and, at the same time, that provides the means for clients that are not yet FHIR aware to show a simple PDF to the user.
It is the explicit wish of the HUBs to provide a solution that enables a gradual transition from a landscape that only contains clients that are not FHIR capable to a landscape that only contains clients that are FHIR capable.
STATUS:
Published
OWNER:
eHealth Platform
STANDARD:
KMEHR with encapsulated FHIR
VERSION:
2.0
DATE:
2023-12-08
DEFINITION:
The Laboratory result transaction aims to transfer the results of examinations performed by the following medical specialties: laboratory, anatomopathology, genetics, bacteriology, molecular biology and toxicology.
This is the description of a minimal KMEHR transaction that can be processed by the current HUB/METAHUB system, and that contains a Lab Report FHIR resource and, at the same time, that provides the means for clients that are not yet FHIR aware to show a simple PDF to the user.
It is the explicit wish of the HUBs to provide a solution that enables a gradual transition from a landscape that only contains clients that are not FHIR capable to a landscape that only contains clients that are FHIR capable.
Guidelines
Generalities
This transaction only requires a level 1 of kmehr normalization. However, further levels may be applied (see structure overview).
Transaction elements
|
id |
id of the transaction according to the ID-KMEHR convention. |
|
cd |
You must use the value 'labresult' from CD-TRANSACTION. You can always add your own local codes. |
|
date |
This is the date of the reporting of the examination(s). By default, this is also the performing date of the examination. If these two dates differ, the performing date should be defined at the item level. |
|
time |
This is the time of the reporting of the examination(s). |
|
author |
This is the person assuming the responsibility of medical content of the result. |
|
iscomplete |
If this is false, this means that you transfer only part of the information and that the recipient should expect a more complete version later. It is not allowed to use a 'true' value if at least one underlying item has the value 'false' for that element. |
|
isvalidated |
If this is false, this means that the information has not been validated medically. It is not allowed to use a 'true' value if at least one underlying item has the value 'false' for that element. |
Structure overview
The transaction consists of two elements:
- lnk: a link element with contentType application/pdf. This will be the pdf that can be used by clients that are not able to process FHIR messages. The pdf will be provided in BASE64 encoding
- lnk: a link element with contentType application/fhir+json, for FHIR documents in json representation, or a link element with contentType application/fhir+xml, for FHIR documents in XML representation. The documents will be provided in BASE64 encoding. The FHIR document SHALL follow the rules as described in the FHIR implementation guide on https://www.ehealth.fgov.be/standards/fhir/lab/index.htm
Generalities
This transaction only requires a level 1 of kmehr normalization. However, further levels may be applied (see structure overview).
Transaction elements
|
id |
id of the transaction according to the ID-KMEHR convention. |
|
cd |
You must use the value 'labresult' from CD-TRANSACTION. You can always add your own local codes. |
|
date |
This is the date of the reporting of the examination(s). By default, this is also the performing date of the examination. If these two dates differ, the performing date should be defined at the item level. |
|
time |
This is the time of the reporting of the examination(s). |
|
author |
This is the person assuming the responsibility of medical content of the result. |
|
iscomplete |
If this is false, this means that you transfer only part of the information and that the recipient should expect a more complete version later. It is not allowed to use a 'true' value if at least one underlying item has the value 'false' for that element. |
|
isvalidated |
If this is false, this means that the information has not been validated medically. It is not allowed to use a 'true' value if at least one underlying item has the value 'false' for that element. |
Structure overview
The transaction consists of two elements:
- lnk: a link element with contentType application/pdf. This will be the pdf that can be used by clients that are not able to process FHIR messages. The pdf will be provided in BASE64 encoding
- lnk: a link element with contentType application/fhir+json, for FHIR documents in json representation, or a link element with contentType application/fhir+xml, for FHIR documents in XML representation. The documents will be provided in BASE64 encoding. The FHIR document SHALL follow the rules as described in the FHIR implementation guide on https://www.ehealth.fgov.be/standards/fhir/lab/index.htm