Difference between revisions of "Minutes - Referral WG 2023-10-06"

From Health Level 7 Belgium Wiki
(Created page with "=== Attendees === * Anne Nerenhausen * Alexis Van Zeveren * Anthony Maton * Bart Decuypere * Bart Reekmans * Benoit De Borggraef * Cyprien Janssens * Daphne Matthy * Dorsan de...")
 
Line 13: Line 13:
 
* Julien Beard
 
* Julien Beard
 
* Karlien Erauw  
 
* Karlien Erauw  
 +
* Loic Carlier
 
* Maarten Cobbaert  
 
* Maarten Cobbaert  
 
* Maxime Daive
 
* Maxime Daive
Line 47: Line 48:
 
::* while implementation the front-end/web application by RIVIV/Smals some problems came up regarding the templates
 
::* while implementation the front-end/web application by RIVIV/Smals some problems came up regarding the templates
 
::* a solution was put in place and is presented
 
::* a solution was put in place and is presented
::::* business concepts
+
::::* Phase 1 includes 7 templates only having one type of care
 +
::::* there are however templates that include different types of care, [https://drive.google.com/file/d/1hD6P38Lso5FlU3UVRfCMoAJzxBIr9vIP/view?usp=sharing see scheme here]
 +
::::* details will be stored in the orderDetail, but there specifications were not clear enough to know how to store all the info in the orderDetail
 +
::::::* a child service request has been created to store details, several groupoings are possible and a such different child service requests and there will always be a basedOn field
 +
::::::* see [https://drive.google.com/file/d/1NYTQ87WPJqtT194vNiiDXE3at6TAY2r8/view?usp=sharing technical scheme here]
 +
::::::* [https://build.fhir.org/ig/hl7-be/referral/branches/issue-265/Bundle-ucgh222p13-bundle.json branch265 has an example: see here]
  
  
* There were incoming questions from Hans
 
::* there are missing links between the business rules document, the templates and the FHIR profiling and use cases. The business rules do not reflect what to send out in the service request to create in the prescribing soft
 
::::* the project team has a mapping on confluence, which is briefly presented
 
::::* it also has the links to certain valuesets
 
::* discussing how this can be shared
 
::* it might be useful to create an additional document explaing the missing links
 
::* the project team will look into how the info on confluence can be shared
 
::* to be continues
 
  
 
* Continue resolution of issues
 
* Continue resolution of issues

Revision as of 07:49, 6 October 2023

Attendees

  • Anne Nerenhausen
  • Alexis Van Zeveren
  • Anthony Maton
  • Bart Decuypere
  • Bart Reekmans
  • Benoit De Borggraef
  • Cyprien Janssens
  • Daphne Matthy
  • Dorsan de Fabricheckers
  • Emily Sevrin
  • Hans De Keersmaecker
  • Julien Beard
  • Karlien Erauw
  • Loic Carlier
  • Maarten Cobbaert
  • Maxime Daive
  • Philippe Lejoly

Excused

  • Ben Goosse
  • Christophe Behaegel
  • Elliot Ananaba
  • Geert Vandenhole
  • Jacques Yakoub
  • Jean-Francois Coquelet
  • Jean-Michel Polfliet
  • José Costa Teixeira
  • Katleen Smedts
  • Katrien Dickx
  • Katrien Thorré
  • Lionel Cremer
  • Marleen Van Eygen
  • Nathan Peeters
  • Laurent Lamouline
  • Pablo Christiaens
  • Pieter Devolder
  • Philippe Baise
  • Richard Francken
  • Robin Merckx

Agenda

  • presentation of made changes & feedback

Meeting Minutes

  • No update from the project side
  • Update on the FHIR resources:
  • while implementation the front-end/web application by RIVIV/Smals some problems came up regarding the templates
  • a solution was put in place and is presented
  • Phase 1 includes 7 templates only having one type of care
  • there are however templates that include different types of care, see scheme here
  • details will be stored in the orderDetail, but there specifications were not clear enough to know how to store all the info in the orderDetail


  • Continue resolution of issues
  • issue 77: light adjustment to 430K message, is ongoing at NIC
  • issue 257: Cobhra FHIR facade would be good, needs to be requested from stakeholders to eHealth platform; there is a temporary solution
  • issue 255: confirmation is needed that it is possible from a technical point of view. For eAgreement you need the INAMI number. The development team is looking into it
  • issue 254: ongoing, no advice from DPO yet
  • issue 250: extension will be created, not yet done. There will not be an interference with other elements. Extension will be created by Bart.
  • issue 256: there is a solution, move towards bundles (using graph operation), still ongoing, need to present once more next meeting

Agenda next meeting

  • Continue resolution of issues and address incoming questions

Next meeting: Friday 20 Oct at 9AM