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

From Health Level 7 Belgium Wiki
(Created page with "=== Attendees === * Anne Nerenhausen * Anthony Maton * Bart Decuypere * Hans De Keersmaeker * Jean-Michel Polfliet * Julien Beard * Katrien Dickx * Karlien Erauw * Maarten C...")
 
 
(5 intermediate revisions by the same user not shown)
Line 3: Line 3:
 
* Anthony Maton
 
* Anthony Maton
 
* Bart Decuypere
 
* Bart Decuypere
 +
* Bart Reekmans
 +
* Ben Goosse
 
* Hans De Keersmaeker
 
* Hans De Keersmaeker
 +
* Jacques Yakoub
 
* Jean-Michel Polfliet
 
* Jean-Michel Polfliet
 
* Julien Beard
 
* Julien Beard
 
* Katrien Dickx
 
* Katrien Dickx
 
* Karlien Erauw  
 
* Karlien Erauw  
−
* Maarten Cobbaert  
+
* Maarten Cobbaert
 
* Marleen Van Eygen
 
* Marleen Van Eygen
 
* Maxime Daive
 
* Maxime Daive
−
* Pablo Christiaens
 
 
* Philippe Baise
 
* Philippe Baise
 
* Robin Merckx
 
* Robin Merckx
−
* Wil Rijnen (partially)
 
  
 
=== Excused ===
 
=== Excused ===
−
* Bart Reekmans
 
−
* Ben Goosse
 
 
* Benjamien Schmitt  
 
* Benjamien Schmitt  
 
* Christophe Behaegel
 
* Christophe Behaegel
Line 24: Line 23:
 
* Dorsan de Fabricheckers
 
* Dorsan de Fabricheckers
 
* Geert Vandenhole
 
* Geert Vandenhole
−
* Jacques Yakoub
+
 
 
* Jean-Francois Coquelet  
 
* Jean-Francois Coquelet  
 
* José Costa Teixeira
 
* José Costa Teixeira
Line 30: Line 29:
 
* Laurent Lamouline
 
* Laurent Lamouline
 
* Lionel Cremer
 
* Lionel Cremer
 +
* Pablo Christiaens
 
* Pieter Devolder
 
* Pieter Devolder
 
* Richard Francken  
 
* Richard Francken  
  
 
=== Agenda ===
 
=== Agenda ===
−
* presentation of workflow & architecture
+
* Resolution of issues
−
* working on use cases
 
  
 
=== Meeting Minutes ===
 
=== Meeting Minutes ===
 
* Does the group agree with the [https://drive.google.com/file/d/156V7Pjw_ZYs4RGEit8HVFi0DhSEjduqo/view?usp=share_link proposal presented last week]
 
* Does the group agree with the [https://drive.google.com/file/d/156V7Pjw_ZYs4RGEit8HVFi0DhSEjduqo/view?usp=share_link proposal presented last week]
−
::* UHMEP system = grey rectangular
+
::* the group agrees that this proposal is moved to the master branch
−
::* all outside is out of scope of the project
+
::* so issue 91 can be closed
−
::* 2 main clients: GP softs & nursing softs that will have to interact
+
::* any comments can still be raised in the upcoming weeks
−
::* starts with a referral prescription, ServiceRequest
+
* [https://github.com/hl7-be/referral/issues/201 One new issue #201]
−
::::* this will create a Bundle/RequestGroup which can have several prescriptions, in a specific order or having dependencies/relationships
+
::*   will the controls by mutuatity or RIZIV be done directly on the UHMEP platform : this is outside the UHMEP platform
−
::* the nursing soft will look for a prescription to execute
+
::* the only thing that changes is the prescription ID
−
::::* will also look for prescriptions related to it, which will be able to retrieve
 
−
:::::* FHIR has standard capabilities to retrieve
 
−
::* nursing soft creates a task (DetailExecution) and UHMEP will create a GlobalExecution, another nurse will be able to create another DetailExecution through her/his nursing soft
 
−
::::* the business rules will indicate how many caregivers can work on a same prescription at the same time
 
−
::::* nurse will create what she is doing in her own system (Treatment: Procedure, MedicationAdministration)
 
−
::* the status of the Prescription will be added when the nurses are done
 
−
::* the nursing soft will send info related to invoicing to MyCarenet, this is out of the scope of the project but should be added to this scheme
 
−
 
 
−
::* second scenario: how will we handle the administration of medication ?
 
−
::::* the GP soft will first read the info on the medication line, available through another system (f.e. vitalink having the medication prescriptions, links also to medication dispenses), it will then use a reference/link to the medication line in its system, GP can add additional notes or prescriptions
 
−
::::* this will have to be discussed internally at INAMI
 
−
 
 
−
* [https://drive.google.com/file/d/1IFSECLKE0TMTnZkc6xxRrTrJjcoLPqPD/view?usp=share_link Use case 2A: combination of medication & compression therapies], during 1 month + afterwards another for 3 montsh
 
−
::* start with administration of medication --> ServiceRequest
 
−
::* reference to nonexisting system with medication line
 
−
::* 3 ServiceRequests are grouped in a RequestGroup
 
−
::::* status can be calculated based upon the Requests part of the group
 
−
::::* there are references to each ServiceRequest
 
−
::::* there are also related actions that refer to the other ServiceRequest
 
−
::::* other relationships can be expressed, f.e. after end if prescriptions one after the other
 
  
−
::* nursing starting a task, TaskReferral, in first ServiceRequest of Use Case 2a
+
* Work on use case :  
−
::::* this is the Global Execution Task
+
::* work on one use case (medication line) has been done and is present in the IG (implementation guide)
−
::::* code system has to be added
+
::* recently the use case on the blood case has been added, is also present in the IG
−
::::* [https://drive.google.com/file/d/1XyI0HiQwCLLVzHrRj0vzgDeYLbFBqf7D/view?usp=share_link PerformerTask, see here]
+
::* annex 81 will be the next use case that will be tackled
−
::::::* there is a reference to the [https://drive.google.com/file/d/1Oc8H1H8TsfA19ZVFMqr4aPtzJ0Tw-A94/view?usp=share_link ReferralTask] & the ServiceRequest so FHIR standard retrieving techniques it will be possible to get the associated data
 
−
::::::* a second nurse can send the info through another Task
 
  
−
::* all resources are available here
+
* referral task & performer tasks: standard FHIR quering sytem will be used
−
::::* PLEASE review and send your feedback through creating issues in github
+
::* this closes [https://github.com/hl7-be/referral/issues/201 issue #199]
 +
::* [https://github.com/hl7-be/referral/issues/197 Issue 197]: there will be additional Snomed CT codes so therefore this issue can not yet be closed
 +
::* [https://github.com/hl7-be/referral/issues/194 Issue 194]: work is ongoing on use cases
 +
::* [https://github.com/hl7-be/referral/issues/193 Issue 193]: there will be an additional serviceRequest that will refer to another medication line, so issue can be closed
 +
::* [https://github.com/hl7-be/referral/issues/191 Issue 191]: awaiting extra input, remains open, no input ready yet
 +
::* [https://github.com/hl7-be/referral/issues/190 Issue 190]: is resolved through the proposed architecture
 +
::* [https://github.com/hl7-be/referral/issues/177 Issue 177]: timing datatype, is still being looked into
 +
::::* is start time & duration sufficient : RIZIV confirms that this is fine, there is often only a start date without time, so start time is optional
 +
::* [https://github.com/hl7-be/referral/issues/187 Issue 187]: legislation requests that the medication is mentioned again on the prescription (for patient security reasons), therefore the issue remains open. There are 3 possible options that need to be presented to the business first
 +
::* [https://github.com/hl7-be/referral/issues/176 Issue 176]: if there is no litoral reference, there is a strong recommendation to have a logical reference (advice from HL7 BE FHIR WG infrastructure & architecture)
 +
::::* UHMEP will only use logical references (for Patient, Practioner)
 +
::* [https://github.com/hl7-be/referral/issues/186 Issue 186]: UCUM units for medication administration
 +
::::* nu update yet
 +
::::* this has to be taken up by the WG FHIR Medication
 +
::* [https://github.com/hl7-be/referral/issues/169 Issue 169]: a document has been provided
 +
::::* a follow-up meeting will happen as from next week
 +
::* [https://github.com/hl7-be/referral/issues/168 Issue 168]: input from José needed
 +
::* [https://github.com/hl7-be/referral/issues/167 Issue 167]: remains open
 +
::* [https://github.com/hl7-be/referral/issues/149 Issue 149]: route value set, a subset valueset will be sent by RIZIV
 +
::* [https://github.com/hl7-be/referral/issues/147 Issue 147]: use of Task is resolved by the architecture proposal
 +
::* [https://github.com/hl7-be/referral/issues/130 Issue 130]: mandatory UUID ?
 +
::::* UHMEP will provide the UUID and the client will receive the UUID when looking up the prescription (through location header)
 +
::::* it is up to the client whether they have accidentally created a double prescription (if the call is made twice)
 +
::* [https://github.com/hl7-be/referral/issues/126 Issue 126]: a use case will be created
 +
::* [https://github.com/hl7-be/referral/issues/77 Issue 77]: this is part of the valueset
 +
::* [https://github.com/hl7-be/referral/issues/73 Issue 73]: this is part of the document that will be released later on today (COBHRA sources - if incomplete RIZIV will check and o the necessary)
 +
::* [https://github.com/hl7-be/referral/issues/70 Issue 70]: input will be received later on today
 +
::* [https://github.com/hl7-be/referral/issues/54 Issue 54]: there is a document on operations
 +
::::* the information will have to be added to the IG, including an API description (using the FHIR standard operations + some specific operations)
 +
::::* in which form do the vendors like to have the API description (in IG or in a cookbook) ? feedback by next week
 +
::::* see: https://build.fhir.org/ig/hl7-be/referral/branches/issue-91/OperationDefinition-be-op-cancel
  
 
=== Agenda next meeting ===
 
=== Agenda next meeting ===
−
* feedback on presentation of architecture phase 1
+
* presentation of valuesets by RIZIV (Anne)
 
* continuation of resolution of issues
 
* continuation of resolution of issues
 +
* input vendors on issue 54
  
 
'''Next meeting: next week Friday 17 Feb at 9AM'''
 
'''Next meeting: next week Friday 17 Feb at 9AM'''

Latest revision as of 08:38, 17 February 2023

Attendees

  • Anne Nerenhausen
  • Anthony Maton
  • Bart Decuypere
  • Bart Reekmans
  • Ben Goosse
  • Hans De Keersmaeker
  • Jacques Yakoub
  • Jean-Michel Polfliet
  • Julien Beard
  • Katrien Dickx
  • Karlien Erauw
  • Maarten Cobbaert
  • Marleen Van Eygen
  • Maxime Daive
  • Philippe Baise
  • Robin Merckx

Excused

  • Benjamien Schmitt
  • Christophe Behaegel
  • Cyprien Janssens
  • Dorsan de Fabricheckers
  • Geert Vandenhole
  • Jean-Francois Coquelet
  • José Costa Teixeira
  • Katleen Smedts
  • Laurent Lamouline
  • Lionel Cremer
  • Pablo Christiaens
  • Pieter Devolder
  • Richard Francken

Agenda

  • Resolution of issues

Meeting Minutes

  • the group agrees that this proposal is moved to the master branch
  • so issue 91 can be closed
  • any comments can still be raised in the upcoming weeks
  • will the controls by mutuatity or RIZIV be done directly on the UHMEP platform : this is outside the UHMEP platform
  • the only thing that changes is the prescription ID
  • 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
  • referral task & performer tasks: standard FHIR quering sytem will be used
  • this closes issue #199
  • Issue 197: there will be additional Snomed CT codes so therefore this issue can not yet be closed
  • Issue 194: work is ongoing on use cases
  • Issue 193: there will be an additional serviceRequest that will refer to another medication line, so issue can be closed
  • Issue 191: awaiting extra input, remains open, no input ready yet
  • Issue 190: is resolved through the proposed architecture
  • Issue 177: timing datatype, is still being looked into
  • is start time & duration sufficient : RIZIV confirms that this is fine, there is often only a start date without time, so start time is optional
  • Issue 187: legislation requests that the medication is mentioned again on the prescription (for patient security reasons), therefore the issue remains open. There are 3 possible options that need to be presented to the business first
  • Issue 176: if there is no litoral reference, there is a strong recommendation to have a logical reference (advice from HL7 BE FHIR WG infrastructure & architecture)
  • UHMEP will only use logical references (for Patient, Practioner)
  • Issue 186: UCUM units for medication administration
  • nu update yet
  • this has to be taken up by the WG FHIR Medication
  • a follow-up meeting will happen as from next week
  • UHMEP will provide the UUID and the client will receive the UUID when looking up the prescription (through location header)
  • it is up to the client whether they have accidentally created a double prescription (if the call is made twice)
  • Issue 126: a use case will be created
  • Issue 77: this is part of the valueset
  • Issue 73: this is part of the document that will be released later on today (COBHRA sources - if incomplete RIZIV will check and o the necessary)
  • Issue 70: input will be received later on today
  • Issue 54: there is a document on operations

Agenda next meeting

  • presentation of valuesets by RIZIV (Anne)
  • continuation of resolution of issues
  • input vendors on issue 54

Next meeting: next week Friday 17 Feb at 9AM

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