Minutes - Referral WG 2020-11-09
From Health Level 7 Belgium Wiki
Contents
Attendees
- Robin Bosman
- Jamie Verelst
- Benny Verhamme
- Dieter De Gruyter
- Jos Bellen
- Kristof Jaubin
- Tom De Backer
- Filip Jacobs
- Frederik De Kegel
- Frederic Istace
- Andries Demont
- Dr Alain Derom
Excused
- Karlien Erauw
- José Costa Teixeira
Agenda
- feedback on draft implementation guide
Minutes
- Robin gives a demo of HL7 Belgium on github
- On build.fhir.org/ig/hl7-be/hl7-be-fhir-laboratory-report/ check out the Guidance and Detailed Specifications, Artifacts
- Feedback can be given through the notepad icon on the top right of each textblock which opens a feedback form
- Feedback arrives in an issue log
- clarification needed on "The laboratory report SHALL also identify itself using a business identifier in the DiagnosticReport.identifier element." : we agree that the use of this shall be in the following way: the combination of system & identifier needs to be globally unique. Typically, the laboratory assigns an identifier that will remain the same during eventual different versions.
- when to replace the lab report or when to add a new version : the extra HL7 extensions on replace, extend and addendum are removed for now. As the vital element of a laboratory report, the Observation, also carries a distinct status (www.hl7.org/fhir/valueset-observation-status.html). It is up to a receiving consumer, when he receives a new version of a report to correctly interpret any updated status on an Observation. When a diagnosticReport is solicited by a party, it should always receive the most up to date version and again, it is up to the consuming party to correctly interpret statuses.
- is the usage of UCUM codes considered as mandatory by the Belgian profile : it shall remain possible to express units using a different way. However, as UCUM provides a standardized syntax to express in theory any type of exotic unit, it is highly recommended to always use the UCUM way to express units.
- Next Meeting : Monday November 16 at 4PM