Difference between revisions of "Minutes - Referral WG 2023-04-28"
From Health Level 7 Belgium Wiki
KarlienErauw (talk | contribs) |
KarlienErauw (talk | contribs) |
||
| Line 66: | Line 66: | ||
::::* wound care: use case has not been discussed on json level, no progress | ::::* wound care: use case has not been discussed on json level, no progress | ||
| − | ::* [https://github.com/hl7-be/referral/issues/ | + | ::* [https://github.com/hl7-be/referral/issues/16 BodyLaterality] : can be closed |
| − | + | ::* Emily is preparing all the use cases for the June release and will be ready next Thursday and afterwards json files will be created by Bart, [https://github.com/hl7-be/referral/issues/218 see issue 218] and [https://github.com/hl7-be/referral/issues/218 see issue 215] | |
| − | + | ::* [https://github.com/hl7-be/referral/issues/214 namespace on identifier, see issue 214]: no update, not yet tackled - Maarten will look into | |
| − | + | ::* [https://github.com/hl7-be/referral/issues/211, issue 211] : not part of June release | |
| − | + | ::* [https://github.com/hl7-be/referral/issues/210, issue 210] : it is part of the business rules, version from last week | |
| − | + | ::::* there were 2 different requests that can now be distinguished, as orderDetail removal and application have been added | |
| − | + | ::* [https://github.com/hl7-be/referral/issues/191 issue on versioning] : depends on the advice of HL7 Belgium FHIR WG infrastructure - Karlien to move it as agenda point for 3 May meeting | |
| − | + | ::* [https://github.com/hl7-be/referral/issues/130 prescriptionNumber] : how to identify a duplicate in case of a network failure, backend will not provide additional info, the prescriber and its software has to handle this (when receiving an error, the prescriber has to check if the prescription already exists, if no, he has to create a new one) | |
| − | : | ||
| − | : | ||
| − | ::: | ||
| − | : | ||
| − | |||
| − | : | ||
| − | |||
| − | |||
| − | |||
| − | ::* | ||
| − | : | ||
| − | |||
| − | ::::* | ||
| − | |||
| − | |||
| − | |||
| − | ::* | ||
| − | : | ||
| − | |||
| − | |||
| − | : | ||
| − | ::* | ||
=== Agenda next meeting === | === Agenda next meeting === | ||
Revision as of 07:43, 28 April 2023
Attendees
- Anthony Maton
- Bart Decuypere
- Cyprien Janssens
- Dorsan de Fabricheckers
- Emily Sevrin
- Geert Vandenhole
- Hans De Keersmaecker
- Jean-Michel Polfliet
- Karlien Erauw
- Katrien Dickx
- Lionel Cremer
- Maarten Cobbaert
- Philippe Baise
- Philippe Lejoly
- Robin Merckx
Excused
- Anne Nerenhausen
- Bart Reekmans
- Ben Goosse
- Christophe Behaegel
- Dorsan de Fabricheckers
- Jacques Yakoub
- Jean-Francois Coquelet
- José Costa Teixeira
- Julien Beard
- Katleen Smedts
- Katrien Thorré
- Marleen Van Eygen
- Maxime Daive
- Nathan Peeters
- Laurent Lamouline
- Pablo Christiaens
- Pieter Devolder
- Richard Francken
Agenda
- review update of logical model following the update of the business rules
- continue resolution of issues
Meeting Minutes
- Project update: focus on acceptation release
- Updates on logical model
- the recorder and the requester: wording is being changed
- validationPeriod has been changed into validityPeriod
- Continue resolution of issues
- issue on body location : work is ongoing, one valueset has more values than the other one. List has already been reduced. List differ depending the context, one list on the caretaking process has 48 elements, the list for the prescription has more elements and on top there can be other element in the patient information model. RIZIV will continue investigating towards what might be a temporary mapping table.
- an addition to the profile has been made following the request, see issue Add BeCodedAnnotation
- different types of notes are needed
- instead of a simple annotation we change it into multiple notes and will add a type to the note, snomed CT codes: "Contraindication to" and "Reason for", these
- the prescriber fills it in
- WG agrees with this change
-
- use case for annex 81 has been prepared
- is this included in the June release ? no Annex 81 is not part of the June release
-
-
- still open items
- in package core clinical some values has been added to laterality
-
-
- catheter care is not part of the June release
- wound care: use case has not been discussed on json level, no progress
-
- BodyLaterality : can be closed
- Emily is preparing all the use cases for the June release and will be ready next Thursday and afterwards json files will be created by Bart, see issue 218 and see issue 215
- namespace on identifier, see issue 214: no update, not yet tackled - Maarten will look into
- issue 211 : not part of June release
- issue 210 : it is part of the business rules, version from last week
- there were 2 different requests that can now be distinguished, as orderDetail removal and application have been added
- issue on versioning : depends on the advice of HL7 Belgium FHIR WG infrastructure - Karlien to move it as agenda point for 3 May meeting
- prescriptionNumber : how to identify a duplicate in case of a network failure, backend will not provide additional info, the prescriber and its software has to handle this (when receiving an error, the prescriber has to check if the prescription already exists, if no, he has to create a new one)
Agenda next meeting
- review update of logical model following the update of the business rules
- continue resolution of issues
Next meeting: next week Friday 5 May at 9AM
