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

From Health Level 7 Belgium Wiki
(Created page with "=== Attendees === * Anthony Maton * Bart Decuypere * Benjamien Schmitt * Cyprien Janssens * Dorsan de Fabricheckers * Geert Vandenhole * Hans De Keersmaeker * Jacques Yakoub...")
 
 
Line 3: Line 3:
 
* Bart Decuypere
 
* Bart Decuypere
 
* Benjamien Schmitt  
 
* Benjamien Schmitt  
 +
* Christophe Behaegel
 
* Cyprien Janssens
 
* Cyprien Janssens
 
* Dorsan de Fabricheckers
 
* Dorsan de Fabricheckers
Line 20: Line 21:
 
* Bart Reekmans
 
* Bart Reekmans
 
* Ben Goosse  
 
* Ben Goosse  
−
* Christophe Behaegel
 
−
 
−
 
 
* Jean-Francois Coquelet  
 
* Jean-Francois Coquelet  
 
* José Costa Teixeira
 
* José Costa Teixeira
Line 28: Line 26:
 
* Laurent Lamouline
 
* Laurent Lamouline
 
* Lionel Cremer
 
* Lionel Cremer
−
 
 
* Pieter Devolder
 
* Pieter Devolder
 
* Richard Francken  
 
* Richard Francken  
Line 36: Line 33:
  
 
=== Meeting Minutes ===
 
=== Meeting Minutes ===
−
* We have to change the meeting schedule once more, apologies, we agree to schedule the meetings on a weekly basis on Fridays at 9AM  
+
* We have to change the meeting schedule once more due to one stakeholder not able to join on Thursdays at 3PM, apologies, we agree to schedule the meetings on a weekly basis on Fridays at 9AM  
 
* The technical meeting to prepare some issues hasn't taken place yet, will happen in the upcoming days and they will provide updates in the next WG meeting
 
* The technical meeting to prepare some issues hasn't taken place yet, will happen in the upcoming days and they will provide updates in the next WG meeting
 +
 
* [https://github.com/hl7-be/referral/issues/5 Issue 5 on Request Group]: we need a link between the logical models and the profiles  
 
* [https://github.com/hl7-be/referral/issues/5 Issue 5 on Request Group]: we need a link between the logical models and the profiles  
 
::* we need a regular overview - how do we do this ? we will add a mapping table to the IG, every field from the logical model will be mapped to a FHIR resource
 
::* we need a regular overview - how do we do this ? we will add a mapping table to the IG, every field from the logical model will be mapped to a FHIR resource
Line 50: Line 48:
 
::::* it is used in eAgreement physio (snomed CT code for physiotherapy)
 
::::* it is used in eAgreement physio (snomed CT code for physiotherapy)
  
−
* [https://github.com/hl7-be/referral/issues/177 Issue 177 - Timing datatype]
+
* [https://github.com/hl7-be/referral/issues/47 Issue 47  Clarification on BasedOn]
−
::* RIZIV will check if the solution of start time + duration is sufficient to replace the start time + end time need: no update yet
+
::* when a prescription is based on another prescription
−
 
+
::* feedback from Anne necessary
−
* [https://github.com/hl7-be/referral/issues/176 Issue 176 - date format & references]
+
:* we look into the latest version of the business rules, referenced in https://github.com/hl7-be/referral/issues/167 (we are in need version of the latest version v0.19)
−
::* 2nd part on references : remains open as still not found a mature solution - FHIR WG architecture & infra needs to come up with guidelines
+
::* "replaces" will be used for prolongation, see related comment in the standard
−
 
+
::* basedOn will be used in case of a proposal , reference to a careplan or any other prior resource that causes this request
−
* [https://github.com/hl7-be/referral/issues/168 Issue 168 - add example scenarios]
+
::* we still need to discuss on how to deal with duplicates
−
::* 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]
+
* [https://github.com/hl7-be/referral/issues/47 Issue 47  Clarification on BasedOn]
−
::* part of architecture
+
::* can be closed, closed in issue 47
  
−
* [https://github.com/hl7-be/referral/issues/136 Issue 136- result receiver]
+
* [https://github.com/hl7-be/referral/issues/52 Issue 52 start operation]
−
::* there is an extension on the service request whether the prescriber of the referral has to be notified/when he wants feedback
+
::* swagger will not be used
−
::* do we want to make the result optional/mandatory, what would be default value ?
+
::* backend would prefer to have it in the form of FHIR resources
−
::* technical solution has to be as simple as possible
+
::* the use of an operation for the start is still under consideration
−
::* it will be mandatory, profiles will need to be checked
+
::* need feedback from Hans
  
−
* [https://github.com/hl7-be/referral/issues/136 Issue 130- prescription number]
+
* [https://github.com/hl7-be/referral/issues/53 Issue 53 finsih operation]
−
::* who is going to provide the UUID, client or back-end software - to be discussed next week as Anthony has left
+
::* similar to issue 52
 +
::* backedn would prefer to have it in the form of FHIR resources
 +
::* the use of an operation for the start is still under consideration
 +
::* need feedback from Hans
  
 
=== Agenda next meeting ===
 
=== Agenda next meeting ===
 +
* feedback from technical meeting
 
* continuation of resolution of issues
 
* continuation of resolution of issues
  
−
'''Next meeting: next week Thursday 26 Jan at 3PM - one hour earlier as from now on'''
+
'''Next meeting: next week Friday 27 Jan at 9AM'''

Latest revision as of 15:06, 19 January 2023

Attendees

  • Anthony Maton
  • Bart Decuypere
  • Benjamien Schmitt
  • Christophe Behaegel
  • Cyprien Janssens
  • Dorsan de Fabricheckers
  • Geert Vandenhole
  • Hans De Keersmaeker
  • Jacques Yakoub
  • Jean-Michel Polfliet
  • Julien Beard
  • Karlien Erauw
  • Maarten Cobbaert
  • Marleen Van Eygen
  • Maxime Daive
  • Philippe Baise

Excused

  • Anne Nerenhausen
  • Bart Reekmans
  • Ben Goosse
  • Jean-Francois Coquelet
  • José Costa Teixeira
  • Katleen Smedts
  • Laurent Lamouline
  • Lionel Cremer
  • Pieter Devolder
  • Richard Francken

Agenda

  • resolution of issues

Meeting Minutes

  • We have to change the meeting schedule once more due to one stakeholder not able to join on Thursdays at 3PM, apologies, we agree to schedule the meetings on a weekly basis on Fridays at 9AM
  • The technical meeting to prepare some issues hasn't taken place yet, will happen in the upcoming days and they will provide updates in the next WG meeting
  • we need a regular overview - how do we do this ? we will add a mapping table to the IG, every field from the logical model will be mapped to a FHIR resource
  • the profiles don't seem specific anymore, we decide to close the issue, we can always recreate one if it still occurs
  • we use it fo differentiate the type of referral (medical imaging, nursing, ...)
  • are we still going to use this or are we only going to rely on the value in the code (template in orderDetail) ? category is not mandatory at FHIR int'l level
  • await feedback from technical meeting
  • it is used in eAgreement physio (snomed CT code for physiotherapy)
  • when a prescription is based on another prescription
  • feedback from Anne necessary
  • "replaces" will be used for prolongation, see related comment in the standard
  • basedOn will be used in case of a proposal , reference to a careplan or any other prior resource that causes this request
  • we still need to discuss on how to deal with duplicates
  • can be closed, closed in issue 47
  • swagger will not be used
  • backend would prefer to have it in the form of FHIR resources
  • the use of an operation for the start is still under consideration
  • need feedback from Hans
  • similar to issue 52
  • backedn would prefer to have it in the form of FHIR resources
  • the use of an operation for the start is still under consideration
  • need feedback from Hans

Agenda next meeting

  • feedback from technical meeting
  • continuation of resolution of issues

Next meeting: next week Friday 27 Jan at 9AM

Retrieved from "https://wiki.hl7belgium.org/index.php?title=Minutes_-_Referral_WG_2022-01-19&oldid=2076"