Minutes - Referral WG 2023-02-10

Attendees

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

Excused

• Bart Reekmans
• Ben Goosse
• Benjamien Schmitt
• Christophe Behaegel
• Cyprien Janssens
• Dorsan de Fabricheckers
• Geert Vandenhole
• Jacques Yakoub
• Jean-Francois Coquelet
• José Costa Teixeira
• Katleen Smedts
• Laurent Lamouline
• Lionel Cremer
• Pieter Devolder
• Richard Francken

Agenda

• Resolution of issues
• working on use cases

Meeting Minutes

• Does the group agree with the proposal presented last week

• 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

• One new issue #201

• 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 taksk: 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 194:

• all outside is out of scope of the project
• 2 main clients: GP softs & nursing softs that will have to interact
• starts with a referral prescription, ServiceRequest

• this will create a Bundle/RequestGroup which can have several prescriptions, in a specific order or having dependencies/relationships

• the nursing soft will look for a prescription to execute

• 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

• 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

• this is the Global Execution Task
• code system has to be added
• PerformerTask, see here

• there is a reference to the 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

• PLEASE review and send your feedback through creating issues in github

Agenda next meeting

• feedback on presentation of architecture phase 1
• continuation of resolution of issues

Next meeting: next week Friday 17 Feb at 9AM