Minutes - Referral WG 2023-02-24

Attendees

• Anne Nerenhausen
• Anthony Maton
• Bart Decuypere
• Bart Reekmans
• Ben Goosse
• Geert Vandenhole

• Jean-Michel Polfliet
• Julien Beard
• Katrien Dickx
• Karlien Erauw
• Laurent Lamouline
• Lionel Cremer
• Maarten Cobbaert
• Marleen Van Eygen
• Maxime Daive
• Philippe Baise
• Robin Merckx

Excused

• Benjamien Schmitt
• Christophe Behaegel
• Cyprien Janssens
• Dorsan de Fabricheckers
• Hans De Keersmaeker
• Jacques Yakoub
• Jean-Francois Coquelet
• José Costa Teixeira
• Katleen Smedts
• Pablo Christiaens
• Pieter Devolder
• Richard Francken

Agenda

• Resolution of issues

Meeting Minutes

• Valuesets: first version has been presented to eHealth platform

• available as XLS here in github
• following the business rules & logical model, a valueset is linked to a template (XLS tabs) and linked to FHIR resource
• there are only Snomed CT codes in case it is useful & relevant
• status and status reason of prescription: do not in Snomed CT, FHIR int'l is followed since they are not codeable concepts as they are administrative values

• status prescription: draft, active, on-hold, revoked, completed, entered-in-error

• there are valuesets that are a combination of Snomed CT and FHIR
• for discipline the COBHRA source is used, if preceded by pers it is the role ; still to be decided to split up in 2 valuesets (cardiology cs cardiologue
• this can have an impact on practionerRole that is part of the core: needs to be investigated
• discipline will be Snomed CT coded in the future, we don't have them yet
• changing twice the core profile is not recommended, we could enhance the CD-HCPARTY code list with the values provided in the way of an extension in a first phase (increment) and in a second phase we could add the Snomed codes to the core profile (which is already ongoing)

• Problem codes values set

• this is a large one: currently analysed by hospitals and NRC - still ongoing
• any Snomed code can be added
• the current GPrefset will be part of it, work is still ongoing and need to be validated by the NRC

• Route & device: we still need to check to put these
• Bodysite: will be a transversal valueset

• will this be aligned with the bodyparts of the woundcare ? this is important for the softs

• 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

• Issue 54: there is a document on operations

• if there are custom operations we will make them part of the IG is ok for the vendors although the FHIR patch can be used for this
• in which form do the vendors like to have the API description (in IG or in a cookbook) ? feedback no yet ready

Agenda next meeting

• issues on valuesets
• UUID issue
• continuation of resolution of issues
• input vendors on issue 54

Next meeting: next week Friday 24 Feb at 9AM - needs to be recorded for absent people due to school holiday week