Difference between revisions of "Minutes - Referral WG 2023-04-14"

From Health Level 7 Belgium Wiki
(Created page with "=== Attendees === * Anne Nerenhausen * Anthony Maton * Bart Decuypere * Bart Reekmans * Ben Goosse * Dorsan de Fabricheckers * Emily Sevrin * Geert Vandenhole * Hans De Keer...")
 
 
(2 intermediate revisions by the same user not shown)
Line 1: Line 1:
 
=== Attendees ===
 
=== Attendees ===
 
* Anne Nerenhausen  
 
* Anne Nerenhausen  
−
* Anthony Maton
 
 
* Bart Decuypere
 
* Bart Decuypere
 
* Bart Reekmans
 
* Bart Reekmans
−
* Ben Goosse
 
 
* Dorsan de Fabricheckers
 
* Dorsan de Fabricheckers
 
* Emily Sevrin
 
* Emily Sevrin
 
* Geert Vandenhole
 
* Geert Vandenhole
−
* Hans De Keersmaecker
 
 
* Jean-Michel Polfliet
 
* Jean-Michel Polfliet
 
* Julien Beard
 
* Julien Beard
 
* Karlien Erauw  
 
* Karlien Erauw  
−
* Katrien Dickx
+
* Katrien Thorré
 
* Lionel Cremer
 
* Lionel Cremer
 
* Maarten Cobbaert  
 
* Maarten Cobbaert  
−
* Marleen Van Eygen
 
 
* Maxime Daive
 
* Maxime Daive
 +
* Nathan Peeters (INAMI)
 +
* Pablo Christiaens
 
* Philippe Baise
 
* Philippe Baise
 
* Philippe Lejoly
 
* Philippe Lejoly
  
 
=== Excused ===
 
=== Excused ===
−
* Benjamien Schmitt
+
* Anthony Maton
 +
* Ben Goosse
 
* Christophe Behaegel
 
* Christophe Behaegel
 
* Cyprien Janssens
 
* Cyprien Janssens
 +
* Hans De Keersmaecker
 
* Jacques Yakoub
 
* Jacques Yakoub
 
* Jean-Francois Coquelet  
 
* Jean-Francois Coquelet  
 
* José Costa Teixeira
 
* José Costa Teixeira
 
* Katleen Smedts
 
* Katleen Smedts
 +
* Katrien Dickx
 +
* Marleen Van Eygen -
 
* Laurent Lamouline
 
* Laurent Lamouline
−
* Pablo Christiaens
 
 
* Pieter Devolder
 
* Pieter Devolder
 
* Richard Francken  
 
* Richard Francken  
Line 38: Line 39:
  
 
=== Meeting Minutes ===
 
=== Meeting Minutes ===
−
* Access to [https://github.com/hl7-be/referral/issues/ Issue list]
+
* Nathan presents himself as part of the INAMI team of Anne Nerenhausen working on the caresets
−
* There is a new version of the business rules 2.7, [https://github.com/hl7-be/referral/issues/215 see here]
+
* Update of business rules V0.21, [https://github.com/hl7-be/referral/issues/219 see in issue 219]
−
* Let's have a look a the newly created issues
+
::* change for eAgreement to include links
−
* [https://github.com/hl7-be/referral/issues/215 Issue 215: unmapped fields]
+
::::* eAgreement: ReferenceID and ReceptionDate (when performer receives the response from advisory doctor)
−
::* a reason code can be added but there is no free text possibility for diagnosis, medical reason
+
::::* in serviceRequest a link to the claimResponse can be put (an update of the business rules is needed)
−
* [https://github.com/hl7-be/referral/issues/214 Issue 214: namespace for identifier]
+
::* medication lines that have an impact on the nursing templates (medication, posology and dosage)
−
::* how to handle the identifiers provided by the clients
+
::::* structured solution, not textual one, in the same way as in VIDIS - it is a temporary solution though as VIDIS has not been finalised yet
−
::* still under investigation
+
::* separate new issues will be created to ensure follow up actions on each of these changes
−
* [https://github.com/hl7-be/referral/issues/216 Issue 216: can we add the name/version of the client software in the metadata of the resource]
+
 
−
::* as a help when issues occurs for support reason
+
::* new field in logical model device on woundcare : action + type of material (attribute device)
−
::* can the contact info added in the user agent be useful ? are the requirements for the user agent available at eHealth platform ? afterwards, investigate if this would be sufficient
+
::::* there will be 3 serviceRequests having a RequestGroup that groups the 3 of them
−
::* can the provenance resource be used ? would make it complicated
+
::::::* or one ServiceRequest with some orderDetails ? TBC
−
::* has to be investigated
+
::::* it will be clarified in the upcoming weeks as a meeting on this topic will happen next week
−
* [https://github.com/hl7-be/referral/issues/213 Issue 213: inconsistencies body location]
+
 
−
::* on top is the schema is in the business rules, below is the list of the snomed codes
+
::* new field in business rules Amamnesis
−
::* it will be looked into by RIZIV internally (Katrien + Anne)
+
::* prescription support information: are still present in the business rules/logical model
−
::* for wound care there are the same issues (see issue) : is being worked on by RIZIV internally
+
::::* ID and reason (reason of deviation on recommendation)
−
* [https://github.com/hl7-be/referral/issues/211 Issue 211: useCase CoSign]
+
 
−
::* results of the exercise can be looked into in the IG: https://build.fhir.org/ig/hl7-be/referral/ServiceRequest-ucgh211-1.html
+
* New issues in [https://github.com/hl7-be/referral/issues/ Issue list]
−
::* will not be part of Release1
+
* Is orderDetail precise enough, [https://github.com/hl7-be/referral/issues/218 see here]
−
* [https://github.com/hl7-be/referral/issues/210 Issue 210: compression therapy]
+
::* some more meetings will happen to discuss each template
−
::* RIZIV is investigating
+
 
−
* [https://github.com/hl7-be/referral/issues/191 Issue 191: versioning]
+
* Change on Requester field, [https://github.com/hl7-be/referral/issues/217 see here]
−
::* RIZIV and eHealth platform need to sync
+
::* modify to a BePractionerRole : agreed upon
−
* [https://github.com/hl7-be/referral/issues/187 Issue 187: administration of medication]
+
 
−
::* add copy of medication in notes field
+
* Add name/version of client software, [https://github.com/hl7-be/referral/issues/216 see here]
−
::* will be part of release 1, but not yet part of the acceptation June release
+
::* looked at eHealth specification
−
* [https://github.com/hl7-be/referral/issues/169 Issue 169: interaction with eAgreement]
+
::* name and version will not be added in metadata as it is already present
−
::* interaction with eAgreement: exchange b/w caregiver & medical advisor will take place in eAgreement,
+
::* issue can be closed as no action is needed
−
::* eReferral will have the ID number and date of reception of the eAgreement
+
 
−
::::* so these fields will have to be added to the logical model and profile  
+
* Unmapped fields, [https://github.com/hl7-be/referral/issues/215 see here]
−
::::* business rules are being updated, will result in v 0.20, that will clarify the meaning of the date of reception
+
::* link to issue 218
−
* [https://github.com/hl7-be/referral/issues/168 Issue 168: example scenarios ]
+
::* this can be solved in the same way as issue 218
−
::* are being worked on, see useful template, see [https://github.com/hl7-be/referral/issues/211 in issue 211]
+
 
 +
* Namespace for identifier, [https://github.com/hl7-be/referral/issues/214 see here]
 +
::* INAMI security team has been consulted and is not confident on the proposed solution, ticket will be updated
 +
 
 +
* Body locations inconsistencies, [https://github.com/hl7-be/referral/issues/213 see here]
 +
::* inconsistencies will be resolved next week, they will be available in a new version of the business rules by next week
 +
 
 +
* CoSign, [https://github.com/hl7-be/referral/issues/211 see here]
 +
::* have the result been looked at ? industry still have to come back on this
 +
 
 +
* Route and device, [https://github.com/hl7-be/referral/issues/205 see here]
 +
::* info is in the new business rules
 +
 
 +
* Versioning and evolution of profiles, [https://github.com/hl7-be/referral/issues/191 see here]
 +
::* to be discussed and decided upon in FHIR Validation & Infrastructure WG
 +
 
 +
* close issue 169
 +
* Modifications resulting from business rules will be applied in the logical model and profile  
  
 
=== Agenda next meeting ===
 
=== Agenda next meeting ===
−
* feedback on use cases
+
* review update of logical model following the update of the business rules
 
* continue resolution of issues  
 
* continue resolution of issues  
  
 
'''Next meeting: next week Friday 21 April at 9AM '''
 
'''Next meeting: next week Friday 21 April at 9AM '''

Latest revision as of 09:03, 14 April 2023

Attendees

  • Anne Nerenhausen
  • Bart Decuypere
  • Bart Reekmans
  • Dorsan de Fabricheckers
  • Emily Sevrin
  • Geert Vandenhole
  • Jean-Michel Polfliet
  • Julien Beard
  • Karlien Erauw
  • Katrien Thorré
  • Lionel Cremer
  • Maarten Cobbaert
  • Maxime Daive
  • Nathan Peeters (INAMI)
  • Pablo Christiaens
  • Philippe Baise
  • Philippe Lejoly

Excused

  • Anthony Maton
  • Ben Goosse
  • Christophe Behaegel
  • Cyprien Janssens
  • Hans De Keersmaecker
  • Jacques Yakoub
  • Jean-Francois Coquelet
  • José Costa Teixeira
  • Katleen Smedts
  • Katrien Dickx
  • Marleen Van Eygen -
  • Laurent Lamouline
  • Pieter Devolder
  • Richard Francken
  • Robin Merckx

Agenda

  • Resolution of issues

Meeting Minutes

  • Nathan presents himself as part of the INAMI team of Anne Nerenhausen working on the caresets
  • Update of business rules V0.21, see in issue 219
  • change for eAgreement to include links
  • eAgreement: ReferenceID and ReceptionDate (when performer receives the response from advisory doctor)
  • in serviceRequest a link to the claimResponse can be put (an update of the business rules is needed)
  • medication lines that have an impact on the nursing templates (medication, posology and dosage)
  • structured solution, not textual one, in the same way as in VIDIS - it is a temporary solution though as VIDIS has not been finalised yet
  • separate new issues will be created to ensure follow up actions on each of these changes
  • new field in logical model device on woundcare : action + type of material (attribute device)
  • there will be 3 serviceRequests having a RequestGroup that groups the 3 of them
  • or one ServiceRequest with some orderDetails ? TBC
  • it will be clarified in the upcoming weeks as a meeting on this topic will happen next week
  • new field in business rules Amamnesis
  • prescription support information: are still present in the business rules/logical model
  • ID and reason (reason of deviation on recommendation)
  • some more meetings will happen to discuss each template
  • modify to a BePractionerRole : agreed upon
  • Add name/version of client software, see here
  • looked at eHealth specification
  • name and version will not be added in metadata as it is already present
  • issue can be closed as no action is needed
  • link to issue 218
  • this can be solved in the same way as issue 218
  • INAMI security team has been consulted and is not confident on the proposed solution, ticket will be updated
  • Body locations inconsistencies, see here
  • inconsistencies will be resolved next week, they will be available in a new version of the business rules by next week
  • have the result been looked at ? industry still have to come back on this
  • info is in the new business rules
  • Versioning and evolution of profiles, see here
  • to be discussed and decided upon in FHIR Validation & Infrastructure WG
  • close issue 169
  • Modifications resulting from business rules will be applied in the logical model and profile

Agenda next meeting

  • review update of logical model following the update of the business rules
  • continue resolution of issues

Next meeting: next week Friday 21 April at 9AM

Retrieved from "https://wiki.hl7belgium.org/index.php?title=Minutes_-_Referral_WG_2023-04-14&oldid=2295"