Difference between revisions of "Minutes - Referral WG 2023-02-24"

From Health Level 7 Belgium Wiki
(Created page with "=== Attendees === * Anne Nerenhausen * Anthony Maton * Bart Decuypere * Bart Reekmans * Ben Goosse * Geert Vandenhole * Jean-Michel Polfliet * Julien Beard * Katrien Dickx...")
 
Line 3: Line 3:
 
* Anthony Maton
 
* Anthony Maton
 
* Bart Decuypere
 
* Bart Decuypere
−
* Bart Reekmans
 
−
* Ben Goosse
 
 
* Geert Vandenhole
 
* Geert Vandenhole
−
 
 
* Jean-Michel Polfliet
 
* Jean-Michel Polfliet
 
* Julien Beard
 
* Julien Beard
Line 17: Line 14:
 
* Maxime Daive
 
* Maxime Daive
 
* Philippe Baise
 
* Philippe Baise
−
* Robin Merckx
 
  
 
=== Excused ===
 
=== Excused ===
 +
* Ben Goosse
 
* Benjamien Schmitt  
 
* Benjamien Schmitt  
 +
* Bart Reekmans
 
* Christophe Behaegel
 
* Christophe Behaegel
 
* Cyprien Janssens
 
* Cyprien Janssens
Line 32: Line 30:
 
* Pieter Devolder
 
* Pieter Devolder
 
* Richard Francken  
 
* Richard Francken  
 +
* Robin Merckx
  
 
=== Agenda ===
 
=== Agenda ===
Line 37: Line 36:
  
 
=== Meeting Minutes ===
 
=== Meeting Minutes ===
−
* Valuesets: first version has been presented to eHealth platform
+
* Valuesets: first version was presented last week
 +
::* all the valuesets have been [https://build.fhir.org/ig/hl7-be/referral added to the IG]
 +
::* Geert provided the already used bodyparts for woundcare - thanks
 
::* available as [https://github.com/hl7-be/referral/issues/205 XLS here in github]
 
::* available as [https://github.com/hl7-be/referral/issues/205 XLS here in github]
−
::* following the business rules & logical model, a valueset is linked to a template (XLS tabs) and linked to FHIR resource
 
−
::* there are only Snomed CT codes in case it is useful & relevant
 
−
::* status and status reason of prescription: do not in Snomed CT, FHIR int'l is followed since they are not codeable concepts as they are administrative values
 
−
::::* status prescription: draft, active, on-hold, revoked, completed, entered-in-error
 
−
::* there are valuesets that are a combination of Snomed CT and FHIR
 
−
::* for discipline the COBHRA source is used, if preceded by pers it is the role ; still to be decided to split up in 2 valuesets (cardiology cs cardiologue
 
−
::* this can have an impact on practionerRole that is part of the core: needs to be investigated
 
−
::* discipline will be Snomed CT coded in the future, we don't have them yet
 
−
::* changing twice the core profile is not recommended, we could enhance the CD-HCPARTY code list with the values provided in the way of an extension in a first phase (increment) and in a second phase we could add the Snomed codes to the core profile (which is already ongoing)
 
  
−
* Problem codes values set
+
* As we slowly move to Snomed, there will be continuous changes and needs for discussion as linked to different projects. The first version will be used for the upcoming weeks/months
−
::* this is a large one: currently analysed by hospitals and NRC - still ongoing
+
 
−
::* any Snomed code can be added
+
* [https://github.com/hl7-be/referral/issues/ Issue list]
−
::* the current GPrefset will be part of it, work is still ongoing and need to be validated by the NRC
+
::* Annex 81 use case : work awaits steerco decision
 +
::* [https://github.com/hl7-be/referral/issues/5 Issue 5]: will remain open, awaiting info
 +
::* [https://github.com/hl7-be/referral/issues/10 Issue 10]: remains open, awaiting info
 +
::* [https://github.com/hl7-be/referral/issues/47 Issue 47]: how to handle duplicates of a service request ?
 +
::::* we don't need a link with the original service request for a duplicate so we can drop the third option and close the issue
 +
::* [https://github.com/hl7-be/referral/issues/54 Issue 54]: description of custom operations, these will be part of the IG
 +
::* [https://github.com/hl7-be/referral/issues/77 Issue 77]: needs to be decided
 +
::* [https://github.com/hl7-be/referral/issues/126 Issue 126]: needs to be checked by RIZIV
  
−
* Route & device: we still need to check to put these
 
−
* Bodysite: will be a transversal valueset
 
−
::* will this be aligned with the bodyparts of the woundcare ? this is important for the softs
 
  
 
* Work on use case :  
 
* Work on use case :  

Revision as of 08:32, 24 February 2023

Attendees

  • Anne Nerenhausen
  • Anthony Maton
  • Bart Decuypere
  • Geert Vandenhole
  • Jean-Michel Polfliet
  • Julien Beard
  • Katrien Dickx
  • Karlien Erauw
  • Laurent Lamouline
  • Lionel Cremer
  • Maarten Cobbaert
  • Marleen Van Eygen
  • Maxime Daive
  • Philippe Baise

Excused

  • Ben Goosse
  • Benjamien Schmitt
  • Bart Reekmans
  • Christophe Behaegel
  • Cyprien Janssens
  • Dorsan de Fabricheckers
  • Hans De Keersmaeker
  • Jacques Yakoub
  • Jean-Francois Coquelet
  • José Costa Teixeira
  • Katleen Smedts
  • Pablo Christiaens
  • Pieter Devolder
  • Richard Francken
  • Robin Merckx

Agenda

  • Resolution of issues

Meeting Minutes

  • Valuesets: first version was presented last week
  • As we slowly move to Snomed, there will be continuous changes and needs for discussion as linked to different projects. The first version will be used for the upcoming weeks/months
  • Annex 81 use case : work awaits steerco decision
  • Issue 5: will remain open, awaiting info
  • Issue 10: remains open, awaiting info
  • Issue 47: how to handle duplicates of a service request ?
  • we don't need a link with the original service request for a duplicate so we can drop the third option and close the issue
  • Issue 54: description of custom operations, these will be part of the IG
  • Issue 77: needs to be decided
  • Issue 126: needs to be checked by RIZIV


  • Work on use case :
  • work on one use case (medication line) has been done and is present in the IG (implementation guide)
  • recently the use case on the blood case has been added, is also present in the IG
  • annex 81 will be the next use case that will be tackled
  • Issue 54: there is a document on operations
  • if there are custom operations we will make them part of the IG is ok for the vendors although the FHIR patch can be used for this
  • in which form do the vendors like to have the API description (in IG or in a cookbook) ? feedback no yet ready

Agenda next meeting

  • issues on valuesets
  • UUID issue
  • continuation of resolution of issues
  • input vendors on issue 54

Next meeting: next week Friday 24 Feb at 9AM - needs to be recorded for absent people due to school holiday week

Retrieved from "https://wiki.hl7belgium.org/index.php?title=Minutes_-_Referral_WG_2023-02-24&oldid=2181"