Difference between revisions of "Minutes - Referral WG 2023-03-31"
From Health Level 7 Belgium Wiki
KarlienErauw (talk | contribs) |
KarlienErauw (talk | contribs) |
||
| (4 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
=== Attendees === | === Attendees === | ||
* Anne Nerenhausen | * Anne Nerenhausen | ||
| + | * Anthony Maton | ||
* Bart Decuypere | * Bart Decuypere | ||
* Bart Reekmans | * Bart Reekmans | ||
* Ben Goosse | * Ben Goosse | ||
| + | * Dorsan de Fabricheckers | ||
* Emily Sevrin | * Emily Sevrin | ||
* Geert Vandenhole | * Geert Vandenhole | ||
| Line 10: | Line 12: | ||
* Julien Beard | * Julien Beard | ||
* Karlien Erauw | * Karlien Erauw | ||
| + | * Katrien Dickx | ||
* Lionel Cremer | * Lionel Cremer | ||
* Maarten Cobbaert | * Maarten Cobbaert | ||
| Line 15: | Line 18: | ||
* Maxime Daive | * Maxime Daive | ||
* Philippe Baise | * Philippe Baise | ||
| − | * | + | * Philippe Lejoly |
=== Excused === | === Excused === | ||
| − | |||
* Benjamien Schmitt | * Benjamien Schmitt | ||
* Christophe Behaegel | * Christophe Behaegel | ||
* Cyprien Janssens | * Cyprien Janssens | ||
| − | |||
* Jacques Yakoub | * Jacques Yakoub | ||
* Jean-Francois Coquelet | * Jean-Francois Coquelet | ||
* José Costa Teixeira | * José Costa Teixeira | ||
* Katleen Smedts | * Katleen Smedts | ||
| − | |||
* Laurent Lamouline | * Laurent Lamouline | ||
| − | |||
* Pablo Christiaens | * Pablo Christiaens | ||
* Pieter Devolder | * Pieter Devolder | ||
* Richard Francken | * Richard Francken | ||
| + | * Robin Merckx | ||
=== Agenda === | === Agenda === | ||
| Line 38: | Line 38: | ||
=== Meeting Minutes === | === Meeting Minutes === | ||
| − | * [https://github.com/hl7-be/referral/issues/ Issue list] | + | * Access to [https://github.com/hl7-be/referral/issues/ Issue list] |
* There is a new version of the business rules 2.7, [https://github.com/hl7-be/referral/issues/215 see here] | * There is a new version of the business rules 2.7, [https://github.com/hl7-be/referral/issues/215 see here] | ||
* Let's have a look a the newly created issues | * Let's have a look a the newly created issues | ||
| Line 62: | Line 62: | ||
* [https://github.com/hl7-be/referral/issues/191 Issue 191: versioning] | * [https://github.com/hl7-be/referral/issues/191 Issue 191: versioning] | ||
::* RIZIV and eHealth platform need to sync | ::* RIZIV and eHealth platform need to sync | ||
| − | + | * [https://github.com/hl7-be/referral/issues/187 Issue 187: administration of medication] | |
| − | + | ::* add copy of medication in notes field | |
| − | + | ::* will be part of release 1, but not yet part of the acceptation June release | |
| − | ::* [https://github.com/hl7-be/referral/issues/ | + | * [https://github.com/hl7-be/referral/issues/169 Issue 169: interaction with eAgreement] |
| − | ::::* | + | ::* 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 |
| − | ::* | + | * [https://github.com/hl7-be/referral/issues/168 Issue 168: example scenarios ] |
| + | ::* are being worked on, see useful template, see [https://github.com/hl7-be/referral/issues/211 in issue 211] | ||
=== Agenda next meeting === | === Agenda next meeting === | ||
* feedback on use cases | * feedback on use cases | ||
| − | * | + | * continue resolution of issues |
'''Next meeting: next week Friday 14 April at 9AM ''' | '''Next meeting: next week Friday 14 April at 9AM ''' | ||
Latest revision as of 07:46, 31 March 2023
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
