Difference between revisions of "Minutes - Referral WG 2023-04-14"
From Health Level 7 Belgium Wiki
KarlienErauw (talk | contribs) (Created page with "=== Attendees === * Anne Nerenhausen * Anthony Maton * Bart Decuypere * Bart Reekmans * Ben Goosse * Dorsan de Fabricheckers * Emily Sevrin * Geert Vandenhole * Hans De Keer...") |
KarlienErauw (talk | contribs) |
||
| Line 1: | Line 1: | ||
=== Attendees === | === Attendees === | ||
* Anne Nerenhausen | * Anne Nerenhausen | ||
| − | |||
* Bart Decuypere | * Bart Decuypere | ||
* Bart Reekmans | * Bart Reekmans | ||
| − | |||
* Dorsan de Fabricheckers | * Dorsan de Fabricheckers | ||
* Emily Sevrin | * Emily Sevrin | ||
* Geert Vandenhole | * Geert Vandenhole | ||
| − | |||
* Jean-Michel Polfliet | * Jean-Michel Polfliet | ||
* Julien Beard | * Julien Beard | ||
* Karlien Erauw | * Karlien Erauw | ||
| − | * Katrien | + | * Katrien Thorré |
* Lionel Cremer | * Lionel Cremer | ||
* Maarten Cobbaert | * Maarten Cobbaert | ||
| − | |||
* Maxime Daive | * Maxime Daive | ||
| + | * Nathan Peeters (INAMI) | ||
| + | * Pablo Christiaens | ||
* Philippe Baise | * Philippe Baise | ||
* Philippe Lejoly | * Philippe Lejoly | ||
=== Excused === | === Excused === | ||
| − | * | + | * Anthony Maton |
| + | * Ben Goosse | ||
* Christophe Behaegel | * Christophe Behaegel | ||
* Cyprien Janssens | * Cyprien Janssens | ||
| + | * Hans De Keersmaecker | ||
* Jacques Yakoub | * Jacques Yakoub | ||
* Jean-Francois Coquelet | * Jean-Francois Coquelet | ||
* José Costa Teixeira | * José Costa Teixeira | ||
* Katleen Smedts | * Katleen Smedts | ||
| + | * Katrien Dickx | ||
| + | * Marleen Van Eygen - | ||
* Laurent Lamouline | * Laurent Lamouline | ||
| − | |||
* Pieter Devolder | * Pieter Devolder | ||
* Richard Francken | * Richard Francken | ||
| Line 38: | Line 39: | ||
=== Meeting Minutes === | === Meeting Minutes === | ||
| − | * | + | * Nathan presents himself as part of the INAMI team of Anne Nerenhausen working on the caresets |
| − | * | + | * Update of business rules V0.21, [https://github.com/hl7-be/referral/issues/219 see in issue 219] |
| + | ::* change for eAgreement to include links | ||
| + | ::::* eAgreement: ReferenceID and ReceptionDate (when performer receives the response from advisory doctor) | ||
| + | ::::* in serviceRequest a link to the claimResponse can be put (an update of the business rules is needed) | ||
| + | ::* medication lines that have an impact on the nursing templates (medication, posology and dosage) | ||
| + | ::::* structured solution, not textual one, in the same way as in VIDIS - it is a temporary solution though as VIDIS has not been finalised yet | ||
| + | ::* separate new issues will be created to ensure follow up actions on each of these changes | ||
| + | |||
| + | ::* new field in logical model device on woundcare : action + type of material (attribute device) | ||
| + | ::::* there will be 3 serviceRequests having a RequestGroup that groups the 3 of them | ||
| + | ::::::* or one ServiceRequest with some orderDetails ? TBC | ||
| + | ::::* it will be clarified in the upcoming weeks as a meeting on this topic will happen next week | ||
| + | |||
| + | ::* new field in business rules Amamnesis | ||
| + | ::* prescription support information: are still present in the business rules/logical model | ||
| + | ::::* ID and reason (reason of deviation on recommendation) | ||
| + | |||
| + | |||
| + | * New issues in [https://github.com/hl7-be/referral/issues/ Issue list] | ||
| + | * Is orderDetail precise enough, [https://github.com/hl7-be/referral/issues/218 see here] | ||
| + | ::* some more meetings will happen to discuss each template | ||
| + | |||
| + | * Change on Requester field, [https://github.com/hl7-be/referral/issues/217 see here] | ||
| + | ::* modify to a BePractionerRole : agreed upon | ||
| + | |||
| + | * Add name/version of client software, [https://github.com/hl7-be/referral/issues/216 see here] | ||
| + | ::* looked at eHealth specification | ||
| + | ::* name and version will not be added in metadata as it is already present | ||
| + | ::* issue can be closed as no action is needed | ||
| + | |||
| + | * Unmapped fields, [https://github.com/hl7-be/referral/issues/215 see here] | ||
| + | ::* link to issue 218 | ||
| + | ::* this can be solved in the same way as issue 218 | ||
| + | |||
| + | * Namespace for identifier, [https://github.com/hl7-be/referral/issues/214 see here] | ||
| + | ::* INAMI security team has been consulted and is not confident on the proposed solution | ||
| + | |||
| + | |||
* Let's have a look a the newly created issues | * Let's have a look a the newly created issues | ||
* [https://github.com/hl7-be/referral/issues/215 Issue 215: unmapped fields] | * [https://github.com/hl7-be/referral/issues/215 Issue 215: unmapped fields] | ||
Revision as of 07:40, 14 April 2023
Attendees
- Anne Nerenhausen
- Bart Decuypere
- Bart Reekmans
- Dorsan de Fabricheckers
- Emily Sevrin
- Geert Vandenhole
- Jean-Michel Polfliet
- Julien Beard
- Karlien Erauw
- Katrien Thorré
- Lionel Cremer
- Maarten Cobbaert
- Maxime Daive
- Nathan Peeters (INAMI)
- Pablo Christiaens
- Philippe Baise
- Philippe Lejoly
Excused
- Anthony Maton
- Ben Goosse
- Christophe Behaegel
- Cyprien Janssens
- Hans De Keersmaecker
- Jacques Yakoub
- Jean-Francois Coquelet
- José Costa Teixeira
- Katleen Smedts
- Katrien Dickx
- Marleen Van Eygen -
- Laurent Lamouline
- Pieter Devolder
- Richard Francken
- Robin Merckx
Agenda
- Resolution of issues
Meeting Minutes
- Nathan presents himself as part of the INAMI team of Anne Nerenhausen working on the caresets
- Update of business rules V0.21, see in issue 219
- change for eAgreement to include links
- eAgreement: ReferenceID and ReceptionDate (when performer receives the response from advisory doctor)
- in serviceRequest a link to the claimResponse can be put (an update of the business rules is needed)
- medication lines that have an impact on the nursing templates (medication, posology and dosage)
- structured solution, not textual one, in the same way as in VIDIS - it is a temporary solution though as VIDIS has not been finalised yet
- separate new issues will be created to ensure follow up actions on each of these changes
- new field in logical model device on woundcare : action + type of material (attribute device)
- there will be 3 serviceRequests having a RequestGroup that groups the 3 of them
- or one ServiceRequest with some orderDetails ? TBC
- it will be clarified in the upcoming weeks as a meeting on this topic will happen next week
- new field in business rules Amamnesis
- prescription support information: are still present in the business rules/logical model
- ID and reason (reason of deviation on recommendation)
- New issues in Issue list
- Is orderDetail precise enough, see here
- some more meetings will happen to discuss each template
- Change on Requester field, see here
- modify to a BePractionerRole : agreed upon
- Add name/version of client software, see here
- looked at eHealth specification
- name and version will not be added in metadata as it is already present
- issue can be closed as no action is needed
- Unmapped fields, see here
- link to issue 218
- this can be solved in the same way as issue 218
- Namespace for identifier, see here
- INAMI security team has been consulted and is not confident on the proposed solution
- 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 21 April at 9AM
