Difference between revisions of "Minutes - Referral WG 2022-01-05"

From Health Level 7 Belgium Wiki
 
(One intermediate revision by the same user not shown)
Line 4: Line 4:
 
* Bart Decuypere
 
* Bart Decuypere
 
* Benjamien Schmitt  
 
* Benjamien Schmitt  
 +
* Christophe Behaegel
 
* Cyprien Janssens
 
* Cyprien Janssens
 
* Hans De Keersmaeker
 
* Hans De Keersmaeker
Line 13: Line 14:
 
* Maarten Cobbaert  
 
* Maarten Cobbaert  
 
* Maxime Daive
 
* Maxime Daive
* Philippe Baise
+
* Philippe Baise (joined partially)
  
 
=== Excused ===
 
=== Excused ===
Line 21: Line 22:
 
* Geert Vandenhole
 
* Geert Vandenhole
 
* Jean-Francois Coquelet  
 
* Jean-Francois Coquelet  
 
 
* Katleen Smedts
 
* Katleen Smedts
 
* Laurent Lamouline
 
* Laurent Lamouline
Line 40: Line 40:
 
* [https://github.com/hl7-be/referral/issues/194 Issue 194 New issue] will be looked into and presented next week
 
* [https://github.com/hl7-be/referral/issues/194 Issue 194 New issue] will be looked into and presented next week
  
* [https://github.com/hl7-be/referral/issues/193 Issue 193 - more than 1 medication ]in case of wound care:
+
* [https://github.com/hl7-be/referral/issues/193 Issue 193 - more than 1 medication] in case of wound care
::* for wound care we need to prescriptions in one (add at least 2 medications f.e. isobetadine first, flamazine afterwards) but this is not feasible in FHIR (BeMedication)
+
::* there is unclarity whether or not to use request: will be part of the technical discussion/meeting
::* a request group can be used here that refers to the 2 prescriptions
 
  
 
* [https://github.com/hl7-be/referral/issues/191 Issue 191 - Versioning]
 
* [https://github.com/hl7-be/referral/issues/191 Issue 191 - Versioning]
::* [https://drive.google.com/file/d/1z34MJz3thAz8-_X4--DmYroM0M_WNhlT/view?usp=share_link see scheme here]
+
::* still awaiting info
::* await info
 
 
::* we think that both the structure and the businessrules can change because of evolutions in the legislation
 
::* 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...
  
 
+
* [https://github.com/hl7-be/referral/issues/190 Issue 190 ]
 +
::* await architecture diagram
  
 
* [https://github.com/hl7-be/referral/issues/177 Issue 177 - Timing datatype]
 
* [https://github.com/hl7-be/referral/issues/177 Issue 177 - Timing datatype]
::* our input to HL7 Int'l has been accepted but the feature is not available in the current R4 release
+
::* RIZIV will check if the solution of start time + duration is sufficient to replace the start time + end time need: no update yet
::* RIZIV will check if the solution of start time + duration is sufficient to replace the start time + end time need
 
::* issue will remain open meanwhile
 
  
 
* [https://github.com/hl7-be/referral/issues/176 Issue 176 - date format & references]
 
* [https://github.com/hl7-be/referral/issues/176 Issue 176 - date format & references]
::* date format: solution for formatting of the dates is accepted
+
::* 2nd part on references : remains open as still not found a mature solution - FHIR WG architecture & infra needs to come up with guidelines
::* 2nd part on references : remains open as still not found a mature solution  
 
::* 3rd part on status reason: has been resolved some time ago
 
  
 
* [https://github.com/hl7-be/referral/issues/168 Issue 168 - add example scenarios]
 
* [https://github.com/hl7-be/referral/issues/168 Issue 168 - add example scenarios]
::* [https://docs.google.com/spreadsheets/d/1WJlP1WmTRc_qbGpQJsSaffWZykqchv-x/edit?usp=sharing&ouid=100968134423355597040&rtpof=true&sd=true See document]  
+
::* the info [https://docs.google.com/spreadsheets/d/1WJlP1WmTRc_qbGpQJsSaffWZykqchv-x/edit?usp=sharing&ouid=100968134423355597040&rtpof=true&sd=true here] can be the basis for a text version (in the upcoming weeks)
 +
::* info on example scenarios: https://build.fhir.org/examplescenario-example.html
 +
 
 +
* [https://github.com/hl7-be/referral/issues/149 Issue 149 - valuesets of administration routes]
 +
::* 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
 +
 
 +
* [https://github.com/hl7-be/referral/issues/147 Issue 147 - gebruik van task]
 +
::* part of architecture
 +
 
 +
* [https://github.com/hl7-be/referral/issues/136 Issue 136- result receiver]
 +
::* 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
 +
 
 +
* [https://github.com/hl7-be/referral/issues/136 Issue 130- prescription number]
 +
::* who is going to provide the UUID, client or back-end software - to be discussed next week as Anthony has left
  
 
=== Agenda next meeting ===
 
=== Agenda next meeting ===

Latest revision as of 16:05, 12 January 2023

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 12 Jan at 3PM