Difference between revisions of "Minutes - Referral WG 2020-01-25"

From Health Level 7 Belgium Wiki
 
(4 intermediate revisions by the same user not shown)
Line 25: Line 25:
  
 
===== Agenda =====
 
===== Agenda =====
* updated items
+
* updated items since last meeting
* labo codes
 
  
 
===== Minutes =====
 
===== Minutes =====
'''Intro'''
+
''Intro:''
 
* Discussion on the deadlines and questions on the way the FHIR messages will be exchanges b/w labo's and GPsofts and hospitals
 
* Discussion on the deadlines and questions on the way the FHIR messages will be exchanges b/w labo's and GPsofts and hospitals
 
* Question on status of referral platform (at RIZIV end)
 
* Question on status of referral platform (at RIZIV end)
Line 36: Line 35:
 
* The architecture has not been decided yet
 
* The architecture has not been decided yet
  
'''Review of updated items of Labo ordering after last meeting's discussions/open items'''
+
''Review of updated items of Labo ordering after last meeting's discussions/open items:''
 
* Labo ordering: Priority codes as part of the laboratory service request (routine, urgent, asap, stat= emergency)
 
* Labo ordering: Priority codes as part of the laboratory service request (routine, urgent, asap, stat= emergency)
 
::* 4 FHIR basic codes will be used: routine, urgent, asap, stat (= emergency)
 
::* 4 FHIR basic codes will be used: routine, urgent, asap, stat (= emergency)
Line 46: Line 45:
 
::* 3 elements :  
 
::* 3 elements :  
 
::::* channel: by phone, by mail, will be codeable concept
 
::::* channel: by phone, by mail, will be codeable concept
::::* party: having the reference to the patient or practione who needs to be notified
+
::::* party: having the reference to the patient or practioner who needs to be notified
 
::::* instructions: text/string having additional info
 
::::* instructions: text/string having additional info
 
::* see [http://build.fhir.org/ig/hl7-be/hl7-be-fhir-referral-prescription/ServiceRequest-laboratory-order-example1.xml.html example]  
 
::* see [http://build.fhir.org/ig/hl7-be/hl7-be-fhir-referral-prescription/ServiceRequest-laboratory-order-example1.xml.html example]  
 +
::::* looks like we need an additional optional value : phone nbr, email address
 +
::* is there a need to be able to have multiple be-ext-urgent-communication ?  sometimes you need to notify the requester and the patient - extension will be made repeatable and channel as well (if party wants to be notified by phone before 10PM, otherwise by text)
  
 +
::* Results: copy to - HL7 V2 element: be-ext-inform-party can be used
  
 +
* Action points:
 +
::* Robin asks for examples to be converted in FHIR f.e. creatinine clearance with 2 specimens (blood + urine)
 +
::* Labo results: is there any additional feedback on the profiling ?
  
 
'''Next Meeting:''' Monday February 8 at 4PM
 
'''Next Meeting:''' Monday February 8 at 4PM

Latest revision as of 16:07, 25 January 2021

Attendees
  • Robin Bosman
  • Dr Alain Derom
  • Benny Verhamme
  • Frederik Lenaerts
  • Hans De Keersmaecker
  • Joost Van Averbeke
  • Jos Bellen
  • José Costa Teixeira
  • Kristof Jaubin
  • Paul Neyens
  • Peter Laridon
  • Karlien Erauw
  • Theo Schumacher

Not present

  • Andries Demont
  • Frank Vandewiele
  • Mieke Buckinx
  • Thibault Mahieu
  • Tom Fiers
Excused
  • Hendrik Plaetinck
Agenda
  • updated items since last meeting
Minutes

Intro:

  • Discussion on the deadlines and questions on the way the FHIR messages will be exchanges b/w labo's and GPsofts and hospitals
  • Question on status of referral platform (at RIZIV end)
  • Abrumet and RSW have the links to lab results, Coozo not - results are available in the LIS ; at Coozo you need to request a patient's transactions list and then you can request the details
  • it has been decided that there will be an asynchroon communication through the eHealthBox
  • The architecture has not been decided yet

Review of updated items of Labo ordering after last meeting's discussions/open items:

  • Labo ordering: Priority codes as part of the laboratory service request (routine, urgent, asap, stat= emergency)
  • 4 FHIR basic codes will be used: routine, urgent, asap, stat (= emergency)
  • the definition of each of these codes have to be respected, see here
  • Labo ordering: Testing codes - see 2.6.2 here
  • Labo ordering: clarification has been added, see 2.6.3 here
  • callback result/requested result notification : FHIR extension seems necessary: be-ext-urgent-communication, see here
  • when needed to communicate urgently any results
  • 3 elements :
  • channel: by phone, by mail, will be codeable concept
  • party: having the reference to the patient or practioner who needs to be notified
  • instructions: text/string having additional info
  • looks like we need an additional optional value : phone nbr, email address
  • is there a need to be able to have multiple be-ext-urgent-communication ? sometimes you need to notify the requester and the patient - extension will be made repeatable and channel as well (if party wants to be notified by phone before 10PM, otherwise by text)
  • Results: copy to - HL7 V2 element: be-ext-inform-party can be used
  • Action points:
  • Robin asks for examples to be converted in FHIR f.e. creatinine clearance with 2 specimens (blood + urine)
  • Labo results: is there any additional feedback on the profiling ?

Next Meeting: Monday February 8 at 4PM