Difference between revisions of "Minutes - Referral WG 2023-01-27"

From Health Level 7 Belgium Wiki
(Created page with "=== Attendees === * Anne Nerenhausen * Anthony Maton * Benjamien Schmitt * Dorsan de Fabricheckers * Geert Vandenhole * Hans De Keersmaeker * Jacques Yakoub * Jean-Michel Po...")
 
 
(3 intermediate revisions by the same user not shown)
Line 35: Line 35:
  
 
=== Meeting Minutes ===
 
=== Meeting Minutes ===
* The workflow and architecture cannot be presented just yet as it is still under investigation, it will happen in next week's meeting
+
* The workflow and architecture cannot be presented just yet as it is still being worked on, it will happen in next week's meeting
  
* The latest business rules, version 0.19, are referenced in [https://github.com/hl7-be/referral/issues/195 here-issue 195]
+
* The latest business rules, version 0.19, are referenced [https://github.com/hl7-be/referral/issues/195 here-issue 195]
  
 
* [https://github.com/hl7-be/referral/issues/47 Issue 47  Clarification on BasedOn]
 
* [https://github.com/hl7-be/referral/issues/47 Issue 47  Clarification on BasedOn]
::* when a prescription is based on another prescription
+
::* when a prescription is based on another prescription (different from RequestGroup!)
 
::* feedback from Anne : the orderDetail valueset is still being reviewed
 
::* feedback from Anne : the orderDetail valueset is still being reviewed
:* we look into the latest version of (we are in need version of the latest version v0.19)
+
::::* this is also linked to [https://github.com/hl7-be/referral/issues/10 Issue 10 Category field ]
::* "replaces" will be used for prolongation, see related comment in the standard
+
::::* this is also linked to the [https://github.com/hl7-be/referral/issues/179 New Issue 197 List of codes for orderDetail]
::* 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
 
* 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
 
  
* [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/199 New Issue 199 List of codes for orderDetail]
::* 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
+
::* this is a placeholder as being identified as a workitem once the workflow is clarified, not possible to tackle right now
 
 
* [https://github.com/hl7-be/referral/issues/6 Issue 6 The names and specificity of the profiles] : we need more general profiles
 
::* the profiles don't seem specific anymore, we decide to close the issue, we can always recreate one if it still occurs
 
 
 
* [https://github.com/hl7-be/referral/issues/10 Issue 10 Category field ]
 
::* we use it to 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)
 
 
 
 
 
* [https://github.com/hl7-be/referral/issues/48 Issue 48 new extends extension]
 
::* can be closed, linked to issue 47
 
  
 
* [https://github.com/hl7-be/referral/issues/52 Issue 52 start operation] & [https://github.com/hl7-be/referral/issues/53 Issue 53 finish operation]
 
* [https://github.com/hl7-be/referral/issues/52 Issue 52 start operation] & [https://github.com/hl7-be/referral/issues/53 Issue 53 finish operation]
::* this is linked to the workflow & architecture
+
::* this is linked to the workflow & architecture, the UHMEP platform will calculate the status
 
::* Hans will have another check with his technical team
 
::* Hans will have another check with his technical team
  

Latest revision as of 08:59, 27 January 2023

Attendees

  • Anne Nerenhausen
  • Anthony Maton
  • Benjamien Schmitt
  • Dorsan de Fabricheckers
  • Geert Vandenhole
  • Hans De Keersmaeker
  • Jacques Yakoub
  • Jean-Michel Polfliet
  • Julien Beard
  • Katrien Dickx
  • Karlien Erauw
  • Maarten Cobbaert
  • Marleen Van Eygen
  • Philippe Baise

Excused

  • Bart Decuypere - due to technical issue/lack of network
  • Bart Reekmans
  • Ben Goosse
  • Christophe Behaegel
  • Cyprien Janssens
  • Jean-Francois Coquelet
  • José Costa Teixeira
  • Katleen Smedts
  • Laurent Lamouline
  • Lionel Cremer
  • Maxime Daive
  • Pieter Devolder
  • Richard Francken

Agenda

  • presentation of workflow & architecture
  • continuation of resolution of issues

Meeting Minutes

  • The workflow and architecture cannot be presented just yet as it is still being worked on, it will happen in next week's meeting
  • The latest business rules, version 0.19, are referenced here-issue 195
  • when a prescription is based on another prescription (different from RequestGroup!)
  • feedback from Anne : the orderDetail valueset is still being reviewed
  • this is a placeholder as being identified as a workitem once the workflow is clarified, not possible to tackle right now
  • this is linked to the workflow & architecture, the UHMEP platform will calculate the status
  • Hans will have another check with his technical team
  • The meeting is adjourned at 9.20AM due to no updates on meetings, awaiting the input on workflow & architecture

Agenda next meeting

  • feedback from technical meeting
  • continuation of resolution of issues

Next meeting: next week Friday 3 Feb at 9AM