Difference between revisions of "Minutes - Referral WG 2022-10-25"

From Health Level 7 Belgium Wiki
 
(5 intermediate revisions by the same user not shown)
Line 56: Line 56:
 
* Issue 165: https://github.com/hl7-be/lab/issues/165
 
* Issue 165: https://github.com/hl7-be/lab/issues/165
 
::* quick win for the visualizer: when opening the Service request when showing the file  
 
::* quick win for the visualizer: when opening the Service request when showing the file  
::* please note that the visualiser is not part of the HL7 FHIR standard and as such, not eligible for this kind of meeting
+
::* please note that the visualiser is not part of the HL7 FHIR standard and its rework as such is not eligible for this kind of meeting
  
 
* Issue 164: https://github.com/hl7-be/lab/issues/164
 
* Issue 164: https://github.com/hl7-be/lab/issues/164
 
::* add postal codes to visualiser  
 
::* add postal codes to visualiser  
::* please note that the visualiser is not part of the HL7 FHIR standard and as such, not eligible for this kind of meeting
+
::* please note that the visualiser is not part of the HL7 FHIR standard and its rework as such is not eligible for this kind of meeting
  
 
* Issue 163: https://github.com/hl7-be/lab/issues/163
 
* Issue 163: https://github.com/hl7-be/lab/issues/163
Line 73: Line 73:
 
* Issue 160: https://github.com/hl7-be/lab/issues/160 - is more a question
 
* Issue 160: https://github.com/hl7-be/lab/issues/160 - is more a question
 
::* our profile is for a diagnostic report - do we need to mention this in the guidance
 
::* our profile is for a diagnostic report - do we need to mention this in the guidance
 +
 +
* Issue 157: https://github.com/hl7-be/lab/issues/157 - have logical model
 +
::* eHealth platform will reverse engineer technical model to have a logical model and have it reviewed by the clinical biologists - any volunteers are welcomed
 +
::* NL has already a logical model
 +
 +
* Issue 144: https://github.com/hl7-be/lab/issues/144, raised by Philippe Cauchie on dynamic testing: more info (fro mMIPS) is needed
 +
* Issue 141: https://github.com/hl7-be/lab/issues/141, clarification from MIPS is needed
 +
* Issue 139: https://github.com/hl7-be/lab/issues/139, label from LOINC codes differ from those in RETAM
 +
::* loinc numbers will be there, often being RETAM ; a description of the test will be a label that will depend on the lab performing the test, that description will not be the label
 +
::* if the LOINC code is a RETAM code then the RETAM description will have to be used
 +
::* results will be displayed next to one another, showing the RETAM label - which can be confusing
 +
::* RETAM descriptions can be long though although there are short labels
 +
::* --> the labs have to ensure to use the same label on the paper record and digital report
 +
::* --> it is up to the GP softs to decide what they show when results come form different labs
 +
::* this info will have to be included in the guidance
  
 
* Open issues
 
* Open issues
::* does logical model need to be updated ?
+
::* work on logical model  
 
::* is the visualizer part of the standard ? if so, documentation will be necessary  
 
::* is the visualizer part of the standard ? if so, documentation will be necessary  
  
Line 81: Line 96:
 
* wrap-up and resolution of any open issues if they arise
 
* wrap-up and resolution of any open issues if they arise
  
'''Next Meeting : TBC ?'''
+
'''Next Meeting : TBC - in the upcoming weeks '''

Latest revision as of 17:42, 25 October 2022

Attendees

  • Dr Alain Derom
  • Ardon Toonstra
  • Bart Decuypere
  • Benny Verhamme
  • Christoff Nicque
  • Frédéric Istace
  • Hans De Keersmaecker
  • Ilse
  • Jean-Michel Polfiet
  • Jonathan Capitano
  • Jos Bellen
  • José Costa Teixeira
  • Karlien Erauw
  • Kristof Jaubin
  • Peter Laridon
  • Robert Nicolas
  • Theo Schumacher
  • Thibault Mahieu
  • Thomas Mellen
  • Tom Fiers
  • Tom Tollenaere

Excused/Not present

  • Alexis Van Zeveren
  • Bart Havermans
  • Filip Migom
  • Frederik De Kegel
  • Frederik Lenaerts -
  • Hendrik De Moor
  • Joost Van Averbeke
  • Lotte Adriaensen
  • Mieke Buckinx
  • Nick Hermans
  • Nico Vannieuwenhuyze
  • Pablo Christiaens
  • Philippe Cauchie
  • Olivier Lothaire
  • Paul Neyens
  • Richard Francken
  • Roland Vueghs
  • Stefan Waegemans
  • Toon Schiemsky
  • Veerle Claessens
  • Werner De Mulder

Agenda

  • Issue resolutions
  • New issues/questions from an open Q&A organised by the eHealth platform earlier this afternoon
  • other project request: analyse m.b.t. de ontiwkkeling van een nieuwe nationale database en applicatie m.b.t. antistoffen tegen rode bloedcellen en bloedplaatjes

Minutes

Context: since the publication of the profile mid September by eHealth platform, some new issues have been raised

Resolution of open issues: https://github.com/hl7-be/lab/issues

  • quick win for the visualizer: when opening the Service request when showing the file
  • please note that the visualiser is not part of the HL7 FHIR standard and its rework as such is not eligible for this kind of meeting
  • add postal codes to visualiser
  • please note that the visualiser is not part of the HL7 FHIR standard and its rework as such is not eligible for this kind of meeting
  • a lab can have different activity centers but only 1 RIZIV number
  • has to be dealt with as part of BeOrganisation as part of the core profile
  • lab results related to blood transfusion
  • having a centralized database would be risky
  • tests regarding blood transfusions can be dealt with in this profile
  • our profile is for a diagnostic report - do we need to mention this in the guidance
  • eHealth platform will reverse engineer technical model to have a logical model and have it reviewed by the clinical biologists - any volunteers are welcomed
  • NL has already a logical model
  • loinc numbers will be there, often being RETAM ; a description of the test will be a label that will depend on the lab performing the test, that description will not be the label
  • if the LOINC code is a RETAM code then the RETAM description will have to be used
  • results will be displayed next to one another, showing the RETAM label - which can be confusing
  • RETAM descriptions can be long though although there are short labels
  • --> the labs have to ensure to use the same label on the paper record and digital report
  • --> it is up to the GP softs to decide what they show when results come form different labs
  • this info will have to be included in the guidance
  • Open issues
  • work on logical model
  • is the visualizer part of the standard ? if so, documentation will be necessary

Agenda for next meeting:

  • wrap-up and resolution of any open issues if they arise

Next Meeting : TBC - in the upcoming weeks