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

From Health Level 7 Belgium Wiki
 
(9 intermediate revisions by the same user not shown)
Line 1: Line 1:
 
===== Attendees =====  
 
===== Attendees =====  
* Robin Bosman -
+
* Robin Bosman  
* Dr Alain Derom -
+
* 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
 
* Andries Demont
* Benny Verhamme -
 
 
* Frank Vandewiele
 
* Frank Vandewiele
* Frederik Lenaerts -
 
* Hans De Keersmaecker -
 
* Joost Van Averbeke -
 
* Jos Bellen -
 
* José Costa Teixeira -
 
* Kristof Jaubin -
 
 
* Mieke Buckinx  
 
* Mieke Buckinx  
* Paul Neyens -
 
* Peter Laridon
 
* Karlien Erauw -
 
* Theo Schumacher -
 
 
* Thibault Mahieu  
 
* Thibault Mahieu  
 
* Tom Fiers
 
* Tom Fiers
  
 
===== Excused =====  
 
===== Excused =====  
* Hendrik
+
* Hendrik Plaetinck
  
 
===== Agenda =====
 
===== Agenda =====
* updated items
+
* updated items since last meeting
* labo codes
 
  
 
===== Minutes =====
 
===== Minutes =====
* Set priorities of work items
+
''Intro:''
* Lab prescription: transfer of codes in the labo ordering
+
* Discussion on the deadlines and questions on the way the FHIR messages will be exchanges b/w labo's and GPsofts and hospitals
::* 2 fields are foreseen in the FHIR profile: code and detail code (multiple ones are possible)
+
* Question on status of referral platform (at RIZIV end)
::* detail code : similar to result
+
* 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
* What about the specimen ?
+
* it has been decided that there will be an asynchroon communication through the eHealthBox
::* you cannot link code to specimen
+
* The architecture has not been decided yet
::* there is a workaround: requisition code (which is an identifier)
+
 
::* if you have several specimens, you need several labo orders (one order per specimen)
+
''Review of updated items of Labo ordering after last meeting's discussions/open items:''
::* for micro biology, you give the specimen (aeroob & anaeroob)
+
* Labo ordering: Priority codes as part of the laboratory service request (routine, urgent, asap, stat= emergency)
::* with requisition id you can link several labo orders
+
::* 4 FHIR basic codes will be used: routine, urgent, asap, stat (= emergency)
* a RETAM code can only appear once in an order, otherwise labo cannot deal with
+
::::* the definition of each of these codes have to be respected, see [http://hl7.org/fhir/valueset-request-priority.html here]
::* if this RETAM code is not sufficient, the specimen info has to added
+
* Labo ordering: Testing codes - see 2.6.2 [http://build.fhir.org/ig/hl7-be/hl7-be-fhir-referral-prescription/guidance.html here]
::* if 2 RETAM codes are needed, 2 labo orders will be needed
+
* Labo ordering: clarification has been added, see 2.6.3 [http://build.fhir.org/ig/hl7-be/hl7-be-fhir-referral-prescription/guidance.html here]
::* sending system has to determine this
+
* callback result/requested result notification : FHIR extension seems necessary: be-ext-urgent-communication, see [http://build.fhir.org/ig/hl7-be/hl7-be-fhir-referral-prescription/StructureDefinition-be-lab-prescription.html here]
* there is a link with the invoicing
+
::* 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
 +
::* 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
  
* Priority codes as part of the service request (routine, urgent, asap, stat= emergency)
+
* Action points:
::* 4 codes are available in FHIR: routine, urgent, asap, stat (= emergency)
+
::* Robin asks for examples to be converted in FHIR f.e. creatinine clearance with 2 specimens (blood + urine)
::* are these codes sufficient when mentioning the definitions or are more , see [http://hl7.org/fhir/valueset-request-priority.html here]
+
::* Labo results: is there any additional feedback on the profiling ?
::* we can define our own list or an existing other [https://www.hl7.org/fhir/v3/ActPriority/cs.html HL7 list]
 
::* preference goes to list with 4 options
 
* callback result/requested result notification: is useful
 
::* could a boolean be sufficient ? yes/no ?
 
::* options for callback: phone call, text message, notification by eHealthbox
 
::* how do other countries handle this?
 
::* check with other county and setup Q&A session
 
  
 
'''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