Difference between revisions of "Minutes - Referral WG 2023-04-28"

From Health Level 7 Belgium Wiki
 
Line 75: Line 75:
 
::* [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 has to handle this manually (when receiving an error, the prescriber has to check if the prescription already exists, if no, he has to create a new one) - the WG members do not agree with this proposal  
 
::* [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 has to handle this manually (when receiving an error, the prescriber has to check if the prescription already exists, if no, he has to create a new one) - the WG members do not agree with this proposal  
 
::::* for security reasons the ID cannot be stored, scty team gave a negative advice
 
::::* for security reasons the ID cannot be stored, scty team gave a negative advice
::::* the prescriber software should handle this, they proposed before to create a UUID but this proposal was not taken into account
+
::::* the prescriber software should handle this (checking if the ID has been created or not and showing the right messages to the prescriber...), they proposed before to create a UUID but this proposal was not taken into account
  
 
=== Agenda next meeting ===
 
=== Agenda next meeting ===

Latest revision as of 07:59, 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
  • 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 has to handle this manually (when receiving an error, the prescriber has to check if the prescription already exists, if no, he has to create a new one) - the WG members do not agree with this proposal
  • for security reasons the ID cannot be stored, scty team gave a negative advice
  • the prescriber software should handle this (checking if the ID has been created or not and showing the right messages to the prescriber...), they proposed before to create a UUID but this proposal was not taken into account

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