Minutes - Referral WG 2023-06-02

Attendees

• Anne Nerenhausen
• Bart Decuypere
• Bart Reekmans
• Cyprien Janssens
• Emily Sevrin
• Hans De Keersmaecker
• Jean-Michel Polfliet
• Julien Beard
• Karlien Erauw
• Lionel Cremer
• Maarten Cobbaert
• Philippe Baise
• Philippe Lejoly
• Robin Merckx

Excused

• Alexis Van Zeveren
• Anthony Maton
• Ben Goosse
• Christophe Behaegel
• Dorsan de Fabricheckers
• Geert Vandenhole
• Jacques Yakoub
• Jean-Francois Coquelet
• José Costa Teixeira
• Katleen Smedts
• Katrien Dickx
• Katrien Thorré
• Marleen Van Eygen
• Maxime Daive
• Nathan Peeters
• Laurent Lamouline
• Pablo Christiaens
• Pieter Devolder
• Richard Francken

Agenda

• continue resolution of issues (214, 250 and new issues)

Meeting Minutes

• Continue resolution of issues
• issue 214 namespace for identifier: proposal to use header

• review has been finalised and WG agrees with this solution so issue can be closed

• is performer the correct place

• practioner role is in a contained resource and cannot be searched
• several stakeholders prefer option 1 instead of an extension
• Julien thinks that performerType is the correct place but the cardinality at int'l level is 0 to 1 and we need O to * not correct so we would need an extension and this is not narrowing down
• could it work with a practioner role ? we need multiple performer types as sometimes the request can be performed by different types of performers to fulfill one service request (f.e. diabetes education by nurse & physiotherapist)
• option is to force the prescriber to choose the type of the performer

• the prescribers (HCP) need to be consulted to proceed in this way
• to check if this needs a change in the logical model

• looking into the new issues
• field based on performer task

• a performer task must be linked to a prescription via basedOn
• field basedOn is not mustSupport, needs indeed to be changed to mustSupport

• field basedOn on referral task

• needs indeed to be changed to mustSupport

• id for ressource practitionerRole and practitionner

• INAMI reasoning: there is no way/a lack in Belgium to identify a HCP so the proposed way is the only way to identify the HCP that is meaningful
• does a HCP that performs a referral not always have a INAMI number? it indeed exists that a nurse does not have an INAMI number, f.e. a nurse that works in a hospital; an example needs to be provided

• Consultation of a list of BeReferralPrescriptions - also with nihii number

• When consulting prescriptions, it is important to be able to search by nihii number and not just by niss. This is important for both the performer and the requester
• the INAMI number is not saved, you can consult it through Cobhra it it is there

• a HCP can perform care tasks using the INAMI number of a hospitaln (often foreigners)
• a visa is the right to practice
• students receive a temporary INAMI number, after their specialisation it can change

• contained ressource & search

• the "contained resource" concept will not used in the UHMEP project

• it is stated that searches in contained resources are feasible
• in a contained resource you can put your own reference

• issue 242 is still open outside of the June release but important

• as information see description of nursing use cases here

• looking into "1.9 Education and self-care for diabetes patients without a care path", see example here

Agenda next meeting

• continue resolution of issues and presentation of use cases

Next meeting: next week Friday 16 June at 9AM