Minutes - Referral WG 2023-03-31
From Health Level 7 Belgium Wiki
Attendees
- Anne Nerenhausen
- Anthony Maton
- Bart Decuypere
- Bart Reekmans
- Ben Goosse
- Dorsan de Fabricheckers
- Emily Sevrin
- Geert Vandenhole
- Hans De Keersmaecker
- Jean-Michel Polfliet
- Julien Beard
- Karlien Erauw
- Katrien Dickx
- Lionel Cremer
- Maarten Cobbaert
- Marleen Van Eygen
- Maxime Daive
- Philippe Baise
- Philippe Lejoly
Excused
- Benjamien Schmitt
- Christophe Behaegel
- Cyprien Janssens
- Jacques Yakoub
- Jean-Francois Coquelet
- José Costa Teixeira
- Katleen Smedts
- Laurent Lamouline
- Pablo Christiaens
- Pieter Devolder
- Richard Francken
- Robin Merckx
Agenda
- Resolution of issues
Meeting Minutes
- Access to Issue list
- There is a new version of the business rules 2.7, see here
- Let's have a look a the newly created issues
- Issue 215: unmapped fields
- a reason code can be added but there is no free text possibility for diagnosis, medical reason
- how to handle the identifiers provided by the clients
- still under investigation
- as a help when issues occurs for support reason
- can the contact info added in the user agent be useful ? are the requirements for the user agent available at eHealth platform ? afterwards, investigate if this would be sufficient
- can the provenance resource be used ? would make it complicated
- has to be investigated
- on top is the schema is in the business rules, below is the list of the snomed codes
- it will be looked into by RIZIV internally (Katrien + Anne)
- for wound care there are the same issues (see issue) : is being worked on by RIZIV internally
- results of the exercise can be looked into in the IG: https://build.fhir.org/ig/hl7-be/referral/ServiceRequest-ucgh211-1.html
- will not be part of Release1
- RIZIV is investigating
- RIZIV and eHealth platform need to sync
- add copy of medication in notes field
- will be part of release 1, but not yet part of the acceptation June release
- interaction with eAgreement: exchange b/w caregiver & medical advisor will take place in eAgreement,
- eReferral will have the ID number and date of reception of the eAgreement
- so these fields will have to be added to the logical model and profile
- business rules are being updated, will result in v 0.20, that will clarify the meaning of the date of reception
- are being worked on, see useful template, see in issue 211
Agenda next meeting
- feedback on use cases
- continue resolution of issues
Next meeting: next week Friday 14 April at 9AM
