Difference between revisions of "Minutes - Referral WG 2023-04-14"
From Health Level 7 Belgium Wiki
KarlienErauw (talk | contribs) |
KarlienErauw (talk | contribs) |
||
| Line 75: | Line 75: | ||
* Namespace for identifier, [https://github.com/hl7-be/referral/issues/214 see here] | * 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 | + | ::* INAMI security team has been consulted and is not confident on the proposed solution, ticket will be updated |
| + | * Body locations inconsistencies, [https://github.com/hl7-be/referral/issues/213 see here] | ||
| + | ::* inconsistencies will be resolved next week, they will be available in a new version of the business rules by next week | ||
| − | * | + | * CoSign, [https://github.com/hl7-be/referral/issues/211 see here] |
| − | + | ::* have the result been looked at ? industry still have to come back on this | |
| − | + | ||
| − | + | * Route and device, [https://github.com/hl7-be/referral/issues/205 see here] | |
| − | ::* | + | ::* info is in the new business rules |
| − | + | ||
| − | + | * Versioning and evolution of profiles, [https://github.com/hl7-be/referral/issues/191 see here] | |
| − | + | ::* to be discussed and decided upon in FHIR Validation & Infrastructure WG | |
| − | + | ||
| − | + | * close issue 169 | |
| − | + | * Modifications resulting from business rules will be applied in the logical model and profile | |
| − | * [https://github.com/hl7-be/referral/issues/ | ||
| − | ::* | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | ::* | ||
| − | |||
| − | |||
| − | |||
| − | * | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
=== Agenda next meeting === | === Agenda next meeting === | ||
| − | * | + | * review update of logical model following the update of the business rules |
* continue resolution of issues | * continue resolution of issues | ||
'''Next meeting: next week Friday 21 April at 9AM ''' | '''Next meeting: next week Friday 21 April at 9AM ''' | ||
Revision as of 08:00, 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, ticket will be updated
- Body locations inconsistencies, see here
- inconsistencies will be resolved next week, they will be available in a new version of the business rules by next week
- CoSign, see here
- have the result been looked at ? industry still have to come back on this
- Route and device, see here
- info is in the new business rules
- Versioning and evolution of profiles, see here
- to be discussed and decided upon in FHIR Validation & Infrastructure WG
- close issue 169
- Modifications resulting from business rules will be applied in the logical model and profile
Agenda next meeting
- review update of logical model following the update of the business rules
- continue resolution of issues
Next meeting: next week Friday 21 April at 9AM
