Skip to content

hl7-be/lab

Repository files navigation

Laboratory IG



Publication

This ImplementationGuide is published in the following locations:

Continuous Build: http://build.fhir.org/ig/hl7-be/lab
Canonical / permanent URL:

Issues

Issues and change requests are managed here:

Issues: https://github.com/hl7-be/lab/issues
Kanban board: https://github.com/hl7-be/lab/projects/1

Implementation help

Implementation help can always be found by searching the issues. Additionally, some FAQs for implementers on the receiving side have been provided by the industry themselves: https://github.com/hl7-be/lab/blob/master/testing/Lab%20results%20in%20FHIR%20-%20Implementation%20Guide%20for%20Receivers.pdf

Successful testcases

8 labs are actively testing (A big "thank you" to all labs and software vendors providing reference files!)

NUMBER Reference file provided by
1A MACSYS/CMA BV
1B MACSYS/CMA BV
1C Labo UZ Leuven
1D Labo St Luc Bxl
1E1 CGM Lab Belgium
1E3 CGM Lab Belgium
2A1 Labo UZ Leuven
2A2 MACSYS/CMA BV
2A3 Labo St Luc Bxl
2B CGM Lab Belgium
2C MACSYS/CMA BV
2D MACSYS/CMA BV
2E CGM Lab Belgium
2F1 CGM Lab Belgium
2F2 Labo St Luc Bxl
2F3 Labo St Luc Bxl
2F4 CGM Lab Belgium
2F5 CGM Lab Belgium
2H CGM Lab Belgium
2G CGM Lab Belgium
3A CGM Lab Belgium
3B CGM Lab Belgium
3C CGM Lab Belgium
3D CGM Lab Belgium
41A CGM Lab Belgium
41B MACSYS/CMA BV
41C CGM Lab Belgium
41D MACSYS/CMA BV
42A MACSYS/CMA BV
42B CGM Lab Belgium
43A MACSYS/CMA BV
44A MACSYS/CMA BV
44B MACSYS/CMA BV
45 CGM Lab Belgium
5 MACSYS/CMA BV
5A CGM Lab Belgium
5B MACSYS/CMA BV
5C MACSYS/CMA BV
5D MACSYS/CMA BV
7A MACSYS/CMA BV
7B MACSYS/CMA BV
8A MACSYS/CMA BV
8B MACSYS/CMA BV
8C MACSYS/CMA BV
8D CGM Lab Belgium
8E CGM Lab Belgium
9A1 MACSYS/CMA BV
9A2 MACSYS/CMA BV
9A3 MACSYS/CMA BV
9A4 MACSYS/CMA BV
9A5 MACSYS/CMA BV
9A6 MACSYS/CMA BV
9A7 MACSYS/CMA BV
9A8 MACSYS/CMA BV
9A9 Labo Nuytinck
9A10 MACSYS/CMA BV
9A11 MACSYS/CMA BV
9A12 MACSYS/CMA BV
9A13 MACSYS/CMA BV
9A14 MACSYS/CMA BV
10A MACSYS/CMA BV
10B MACSYS/CMA BV

Project Digitalisation Labresults – QUESTIONS – ANSWERS

DOMAIN SUBJECT QUESTION ANSWER
LOINC codes Conversion What information do I need to provide when requesting a new ReTaM code? Every request needs to provide the following info when requesting a new ReTaM code:
  1. Label without abbreviation
  2. Used/usual abbreviation (may contain abbreviated terms)
  3. Sample/matrix
  4. Method
  5. Type and unit of result
  6. Proposed LOINC code
  7. If known, Fratem/RSW-code
  8. If known, Medidoc-code
This makes sure that the requests are sufficiently clear and precise, and prevents work for analyses that already exist in ReTaM
LOINC codes Conversion

How can you do the conversion between the codification system we use now and the LOINC codes ?

There are mapping tables at your disposal between LOINC codes and Medidoc and RSW/FRATEM codes, which your LIS provider can use.
https://www.vas.ehealth.fgov.be/webretam/retam/home.htm?eventName=MENU_SEARCH
LOINC codes Storage

Where can you find these codes ?

https://www.ehealth.fgov.be/standards/kmehr/en/page/retam-exports
See also... https://github.com/hl7-be/lab/issues?q=retam
SNOMED CT codes Conversion Where can you find these codes? Some resources (Specimen) use SNOMED CT codes. You can use values from the Belgian edition of SNOMED CT: https://browser.ihtsdotools.org/?perspective=full&conceptId1=404684003&edition=MAIN/SNOMEDCT-BE/2022-03-15&release=&languages=en,nl,fr .
If the value is not available in the Belgian edition, you can use a value from the international edition, but signal this use to terminology@health.fgov.be with subject: New LOINC code in context Lab Result
Issues eHealth To whom can you address our questions and issues ?

The created github from eHealth is the place to ask questions or to signal a problem:

https://github.com/hl7-be/lab/issues

Fhir Starting with How do we start with Fhir ?

Technical workshop about Fhir organized by eHealth

There are technical Q&A sessions organised every 6 weeks. Please send an email to support@be-ehealth-standards.atlassian.net

Visualization tool Access How can you start this tool ?

This is the link you need: https://fhir-testserver.be/index.php/visualization_webapp

Attention: this is the final link

Hub-metahub system Definition What is this system ?

The hub-metahub system is a network between hubs (Cozo, VZN KUL,RSW, Abrumet) based referential databases, which can be used by a citizen or a caregiver to retrieve all medical reports for a certain cititzen published by healthcare organizations.

GP software solution Finding results of medical examinations How can a GP know the correct reference values in case of multiple tests ?

The GP can refer to the message. He can use a LOINC code. It’s up to each software vendor to foresee a solution by using graphs, stats …

This subject will be treated by the hubs and a document will be published after analysis containing the parameters that can be used to question the hub-metahub system.

Use cases Definition What is use case ?

This term finds its origin in UML (Unified Modeling Language), the theoretical definition says: it’s a description of a behavior of a system that reacts on an input from the outside world.

On a practical level you need to test a new application and therefore you need a set of real situations in input to be able to test your system and to control the validity of the outcome. The number and the quality of the use cases will determine the risk percentage on errors of your application.

API Definition What is an API? API is short for Application Programming Interface. An API is a technical description of the system-to-system communication in terms of actions and input and output descriptions.
JSON Definition What is a JSON-file? A JSON file is a file that contains data in a syntactic format that is currently popular. Other similar, but technically different syntaxes for data are XML, HL7v2, CSV,...
Test server Access What is the RIZIV/INAMI number of the Test Server eHealthBox TestServer eHealthBox Address (Acceptance): Option 1: Recipient Address: 17166921 / Quality: DOCTOR / Identifier Type: NIHII Option 2: Recipient Address: 73100906111 / Quality: DOCTOR / Identifier Type: SSIN
Test server Access What are the SSIN numbers of the different testcases? The list of SSIN numbers for the testcases can be found here: https://docs.google.com/spreadsheets/d/1Zpkz2_rBUYXOHI0f_eQQTXIrXdaTsiUc1qyOrIk-WmY/edit#gid=0
Test server Access Where can I request a user for the testserver? Request your user here: https://fhir-testserver.be/index.php/login If you send your messages using a eHBox with a RIZIV/INAMI number, do not forget to mention it! Otherwise a CBE is enough.
Test server Documentation Where is the manual for the test server? https://docs.google.com/presentation/d/1mZEasXjsMlOKJKt5jRoWcZc2tCKtnH4T/edit?usp=sharing&ouid=101628904260211620169&rtpof=true&sd=true