Minutes - Referral WG 2022-01-12

From Health Level 7 Belgium Wiki
Revision as of 16:41, 12 January 2023 by KarlienErauw (talk | contribs)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Attendees

  • Anne Nerenhausen
  • Anthony Maton
  • Bart Decuypere
  • Benjamien Schmitt
  • Christophe Behaegel
  • Cyprien Janssens
  • Hans De Keersmaeker
  • Jacques Yakoub
  • Jean-Michel Polfliet
  • José Costa Teixeira
  • Julien Beard
  • Karlien Erauw
  • Maarten Cobbaert
  • Maxime Daive
  • Philippe Baise (joined partially)

Excused

  • Bart Reekmans
  • Ben Goosse
  • Dorsan De Fabribeckers
  • Geert Vandenhole
  • Jean-Francois Coquelet
  • Katleen Smedts
  • Laurent Lamouline
  • Lionel Cremer
  • Marleen Van Eygen
  • Pieter Devolder
  • Richard Francken

Agenda

  • resolution of issues

Meeting Minutes

  • still open: how will we retrieve the request group from the service request- use extension or API feature as reverseInclude - this will be part of the architecture overview presentation by Anthony, foreseen for the meeting in 2/3 weeks ; still under investigation
  • some preparatory work will be done between the technical people (Athony, José, Bart, ...) to prepare the work/proposals that will afterwards presented in this WG
  • there is unclarity whether or not to use request: will be part of the technical discussion/meeting
  • still awaiting info
  • we think that both the structure and the businessrules can change because of evolutions in the legislation
  • there will be different versions of templates that could result in different versions of profiles, several publications...
  • await architecture diagram
  • RIZIV will check if the solution of start time + duration is sufficient to replace the start time + end time need: no update yet
  • 2nd part on references : remains open as still not found a mature solution - FHIR WG architecture & infra needs to come up with guidelines
  • Dr Lambot is working on this, still ongoing ; transversal valueset is being created to be shared with medication projects
  • route in logical model is broader than the one applicable for medication: how to deal with this ? will some additional ones be created ?
  • objective is to have a large set, for projects/other contexts there will be subsets
  • part of architecture
  • there is an extension on the service request whether the prescriber of the referral has to be notified/when he wants feedback
  • do we want to make the result optional/mandatory, what would be default value ?
  • technical solution has to be as simple as possible
  • it will be mandatory, profiles will need to be checked
  • who is going to provide the UUID, client or back-end software - to be discussed next week as Anthony has left

Agenda next meeting

  • continuation of resolution of issues

Next meeting: next week Thursday 19 Jan at 3PM - one hour earlier as from now on