Minutes - Referral WG 2022-01-19

Attendees

• Anthony Maton
• Bart Decuypere
• Benjamien Schmitt
• Cyprien Janssens
• Dorsan de Fabricheckers
• Geert Vandenhole
• Hans De Keersmaeker
• Jacques Yakoub
• Jean-Michel Polfliet
• Julien Beard
• Karlien Erauw
• Maarten Cobbaert
• Marleen Van Eygen
• Maxime Daive
• Philippe Baise

Excused

• Anne Nerenhausen
• Bart Reekmans
• Ben Goosse
• Christophe Behaegel

• Jean-Francois Coquelet
• José Costa Teixeira
• Katleen Smedts
• Laurent Lamouline
• Lionel Cremer

• Pieter Devolder
• Richard Francken

Agenda

• resolution of issues

Meeting Minutes

• We have to change the meeting schedule once more, apologies, we agree to schedule the meetings on a weekly basis on Fridays at 9AM
• The technical meeting to prepare some issues hasn't taken place yet, will happen in the upcoming days and they will provide updates in the next WG meeting
• Issue 5 on Request Group: we need a link between the logical models and the profiles

• we need a regular overview - how do we do this ? we will add a mapping table to the IG, every field from the logical model will be mapped to a FHIR resource

• Issue 6 The names and specificity of the profiles : we need more general profiles

• the profiles don't seem specific anymore, we decide to close the issue, we can always recreate one if it still occurs

• Issue 10 Category field

• we use it fo differentiate the type of referral (medical imaging, nursing, ...)

• are we still going to use this or are we only going to rely on the value in the code (template in orderDetail) ? category is not mandatory at FHIR int'l level
• await feedback from technical meeting
• it is used in eAgreement physio (snomed CT code for physiotherapy)

• Issue 177 - Timing datatype

• RIZIV will check if the solution of start time + duration is sufficient to replace the start time + end time need: no update yet

• Issue 176 - date format & references

• 2nd part on references : remains open as still not found a mature solution - FHIR WG architecture & infra needs to come up with guidelines

• Issue 168 - add example scenarios

• the info here can be the basis for a text version (in the upcoming weeks)
• info on example scenarios: https://build.fhir.org/examplescenario-example.html

• Issue 149 - valuesets of administration routes

• Dr Lambot is working on this, still ongoing ; transversal valueset is being created to be shared with medication projects
• route in logical model is broader than the one applicable for medication: how to deal with this ? will some additional ones be created ?

• objective is to have a large set, for projects/other contexts there will be subsets

• Issue 147 - gebruik van task

• part of architecture

• Issue 136- result receiver

• there is an extension on the service request whether the prescriber of the referral has to be notified/when he wants feedback
• do we want to make the result optional/mandatory, what would be default value ?
• technical solution has to be as simple as possible
• it will be mandatory, profiles will need to be checked

• Issue 130- prescription number

• who is going to provide the UUID, client or back-end software - to be discussed next week as Anthony has left

Agenda next meeting

• continuation of resolution of issues

Next meeting: next week Thursday 26 Jan at 3PM - one hour earlier as from now on