Minutes - Referral WG 2023-02-03

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
• Wil Rijnen (partially)

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

• presentation of workflow & architecture
• working on use cases

Meeting Minutes

• There has been progress on the workflow and architecture which will be presented partially,i.e. architecture for the first phase - see scheme here

• UHMEP system = grey rectangular
• 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

-- draft , previous meeting:

• The latest business rules, version 0.19, are referenced here-issue 195

• Issue 47 Clarification on BasedOn

• when a prescription is based on another prescription (different from RequestGroup!)
• feedback from Anne : the orderDetail valueset is still being reviewed

• this is also linked to Issue 10 Category field
• this is also linked to the New Issue 197 List of codes for orderDetail

• New Issue 199 List of codes for orderDetail

• this is a placeholder as being identified as a workitem once the workflow is clarified, not possible to tackle right now

• Issue 52 start operation & Issue 53 finish operation

• this is linked to the workflow & architecture, the UHMEP platform will calculate the status
• Hans will have another check with his technical team

• The meeting is adjourned at 9.20AM due to no updates on meetings, awaiting the input on workflow & architecture

Agenda next meeting

• feedback from technical meeting
• continuation of resolution of issues

Next meeting: next week Friday 10 Feb at 9AM