Difference between revisions of "Minutes - Referral WG 2023-02-17"

From Health Level 7 Belgium Wiki
(Created page with "=== Attendees === * Anne Nerenhausen * Anthony Maton * Bart Decuypere * Bart Reekmans * Geert Vandenhole * Hans De Keersmaeker * Jean-Michel Polfliet * Julien Beard * Katrie...")
 
 
Line 4: Line 4:
 
* Bart Decuypere
 
* Bart Decuypere
 
* Bart Reekmans
 
* Bart Reekmans
−
 
+
* Ben Goosse
 
* Geert Vandenhole
 
* Geert Vandenhole
 
* Hans De Keersmaeker
 
* Hans De Keersmaeker
Line 20: Line 20:
  
 
=== Excused ===
 
=== Excused ===
−
* Ben Goosse
 
 
* Benjamien Schmitt  
 
* Benjamien Schmitt  
 
* Christophe Behaegel
 
* Christophe Behaegel
Line 38: Line 37:
 
=== Meeting Minutes ===
 
=== Meeting Minutes ===
 
* Valuesets: first version has been presented to eHealth platform
 
* Valuesets: first version has been presented to eHealth platform
 +
::* available as [https://github.com/hl7-be/referral/issues/205 XLS here in github]
 
::* following the business rules & logical model, a valueset is linked to a template (XLS tabs) and linked to FHIR resource
 
::* following the business rules & logical model, a valueset is linked to a template (XLS tabs) and linked to FHIR resource
 
::* there are only Snomed CT codes in case it is useful & relevant
 
::* there are only Snomed CT codes in case it is useful & relevant
Line 44: Line 44:
 
::* there are valuesets that are a combination of Snomed CT and FHIR  
 
::* there are valuesets that are a combination of Snomed CT and FHIR  
 
::* for discipline the COBHRA source is used, if preceded by pers it is the role ; still to be decided to split up in 2 valuesets (cardiology cs cardiologue
 
::* for discipline the COBHRA source is used, if preceded by pers it is the role ; still to be decided to split up in 2 valuesets (cardiology cs cardiologue
−
::::
+
::* this can have an impact on practionerRole that is part of the core: needs to be investigated
 +
::* discipline will be Snomed CT coded in the future, we don't have them yet
 +
::* changing twice the core profile is not recommended, we could enhance the CD-HCPARTY code list with the values provided in the way of an extension in a first phase (increment) and in a second phase we could add the Snomed codes to the core profile (which is already ongoing)
 +
 
 +
* Problem codes values set
 +
::* this is a large one: currently analysed by hospitals and NRC - still ongoing
 +
::* any Snomed code can be added
 +
::* the current GPrefset will be part of it, work is still ongoing and need to be validated by the NRC
  
−
* Does the group agree with the [https://drive.google.com/file/d/156V7Pjw_ZYs4RGEit8HVFi0DhSEjduqo/view?usp=share_link proposal presented last week]
+
* Route & device: we still need to check to put these
−
::* the group agrees that this proposal is moved to the master branch
+
* Bodysite: will be a transversal valueset
−
::* so issue 91 can be closed
+
::* will this be aligned with the bodyparts of the woundcare ? this is important for the softs
−
::* any comments can still be raised in the upcoming weeks
 
−
* [https://github.com/hl7-be/referral/issues/201 One new issue #201]
 
−
::*   will the controls by mutuatity or RIZIV be done directly on the UHMEP platform : this is outside the UHMEP platform
 
−
::* the only thing that changes is the prescription ID
 
  
 
* Work on use case :  
 
* Work on use case :  
Line 59: Line 62:
 
::* annex 81 will be the next use case that will be tackled  
 
::* annex 81 will be the next use case that will be tackled  
  
−
* referral task & performer taksk: standard FHIR quering sytem will be used
 
−
::* this closes [https://github.com/hl7-be/referral/issues/201 issue #199]
 
−
::* [https://github.com/hl7-be/referral/issues/197 Issue 197]: there will be additional Snomed CT codes so therefore this issue can not yet be closed
 
−
::* [https://github.com/hl7-be/referral/issues/194 Issue 194]: work is ongoing on use cases
 
−
::* [https://github.com/hl7-be/referral/issues/193 Issue 193]: there will be an additional serviceRequest that will refer to another medication line, so issue can be closed
 
−
::* [https://github.com/hl7-be/referral/issues/191 Issue 191]: awaiting extra input, remains open, no input ready yet
 
−
::* [https://github.com/hl7-be/referral/issues/190 Issue 190]: is resolved through the proposed architecture
 
−
::* [https://github.com/hl7-be/referral/issues/177 Issue 177]: timing datatype, is still being looked into
 
−
::::* is start time & duration sufficient : RIZIV confirms that this is fine, there is often only a start date without time, so start time is optional
 
−
::* [https://github.com/hl7-be/referral/issues/187 Issue 187]: legislation requests that the medication is mentioned again on the prescription (for patient security reasons), therefore the issue remains open. There are 3 possible options that need to be presented to the business first
 
−
::* [https://github.com/hl7-be/referral/issues/176 Issue 176]: if there is no litoral reference, there is a strong recommendation to have a logical reference (advice from HL7 BE FHIR WG infrastructure & architecture)
 
−
::::* UHMEP will only use logical references (for Patient, Practioner)
 
−
::* [https://github.com/hl7-be/referral/issues/186 Issue 186]: UCUM units for medication administration
 
−
::::* nu update yet
 
−
::::* this has to be taken up by the WG FHIR Medication
 
−
::* [https://github.com/hl7-be/referral/issues/169 Issue 169]: a document has been provided
 
−
::::* a follow-up meeting will happen as from next week
 
−
::* [https://github.com/hl7-be/referral/issues/168 Issue 168]: input from José needed
 
−
::* [https://github.com/hl7-be/referral/issues/167 Issue 167]: remains open
 
−
::* [https://github.com/hl7-be/referral/issues/149 Issue 149]: route value set, a subset valueset will be sent by RIZIV
 
−
::* [https://github.com/hl7-be/referral/issues/147 Issue 147]: use of Task is resolved by the architecture proposal
 
−
::* [https://github.com/hl7-be/referral/issues/130 Issue 130]: mandatory UUID ?
 
−
::::* UHMEP will provide the UUID and the client will receive the UUID when looking up the prescription (through location header)
 
−
::::* it is up to the client whether they have accidentally created a double prescription (if the call is made twice)
 
−
::* [https://github.com/hl7-be/referral/issues/126 Issue 126]: a use case will be created
 
−
::* [https://github.com/hl7-be/referral/issues/77 Issue 77]: this is part of the valueset
 
−
::* [https://github.com/hl7-be/referral/issues/73 Issue 73]: this is part of the document that will be released later on today (COBHRA sources - if incomplete RIZIV will check and o the necessary)
 
−
::* [https://github.com/hl7-be/referral/issues/70 Issue 70]: input will be received later on today
 
 
::* [https://github.com/hl7-be/referral/issues/54 Issue 54]: there is a document on operations  
 
::* [https://github.com/hl7-be/referral/issues/54 Issue 54]: there is a document on operations  
−
::::* the information will have to be added to the IG, including an API description (using the FHIR standard operations + some specific operations)
+
::::* if there are custom operations we will make them part of the IG is ok for the vendors although the FHIR patch can be used for this
−
::::* in which form do the vendors like to have the API description (in IG or in a cookbook) ? feedback by next week
+
::::* in which form do the vendors like to have the API description (in IG or in a cookbook) ? feedback no yet ready
−
::::* see: https://build.fhir.org/ig/hl7-be/referral/branches/issue-91/OperationDefinition-be-op-cancel
 
  
 
=== Agenda next meeting ===
 
=== Agenda next meeting ===
−
* presentation of valueset by RIZIV (Anne)
+
* issues on valuesets
 +
* UUID issue
 
* continuation of resolution of issues
 
* continuation of resolution of issues
−
* input vendors on issue 54
+
* input vendors on issue 54  
  
−
'''Next meeting: next week Friday 24 Feb at 9AM'''
+
'''Next meeting: next week Friday 24 Feb at 9AM - needs to be recorded for absent people due to school holiday week'''

Latest revision as of 09:09, 17 February 2023

Attendees

  • Anne Nerenhausen
  • Anthony Maton
  • Bart Decuypere
  • Bart Reekmans
  • Ben Goosse
  • Geert Vandenhole
  • Hans De Keersmaeker
  • Jean-Michel Polfliet
  • Julien Beard
  • Katrien Dickx
  • Karlien Erauw
  • Laurent Lamouline
  • Lionel Cremer
  • Maarten Cobbaert
  • Marleen Van Eygen
  • Maxime Daive
  • Philippe Baise
  • Robin Merckx

Excused

  • Benjamien Schmitt
  • Christophe Behaegel
  • Cyprien Janssens
  • Dorsan de Fabricheckers
  • Jacques Yakoub
  • Jean-Francois Coquelet
  • José Costa Teixeira
  • Katleen Smedts
  • Pablo Christiaens
  • Pieter Devolder
  • Richard Francken

Agenda

  • Resolution of issues

Meeting Minutes

  • Valuesets: first version has been presented to eHealth platform
  • available as XLS here in github
  • following the business rules & logical model, a valueset is linked to a template (XLS tabs) and linked to FHIR resource
  • there are only Snomed CT codes in case it is useful & relevant
  • status and status reason of prescription: do not in Snomed CT, FHIR int'l is followed since they are not codeable concepts as they are administrative values
  • status prescription: draft, active, on-hold, revoked, completed, entered-in-error
  • there are valuesets that are a combination of Snomed CT and FHIR
  • for discipline the COBHRA source is used, if preceded by pers it is the role ; still to be decided to split up in 2 valuesets (cardiology cs cardiologue
  • this can have an impact on practionerRole that is part of the core: needs to be investigated
  • discipline will be Snomed CT coded in the future, we don't have them yet
  • changing twice the core profile is not recommended, we could enhance the CD-HCPARTY code list with the values provided in the way of an extension in a first phase (increment) and in a second phase we could add the Snomed codes to the core profile (which is already ongoing)
  • Problem codes values set
  • this is a large one: currently analysed by hospitals and NRC - still ongoing
  • any Snomed code can be added
  • the current GPrefset will be part of it, work is still ongoing and need to be validated by the NRC
  • Route & device: we still need to check to put these
  • Bodysite: will be a transversal valueset
  • will this be aligned with the bodyparts of the woundcare ? this is important for the softs
  • Work on use case :
  • work on one use case (medication line) has been done and is present in the IG (implementation guide)
  • recently the use case on the blood case has been added, is also present in the IG
  • annex 81 will be the next use case that will be tackled
  • Issue 54: there is a document on operations
  • if there are custom operations we will make them part of the IG is ok for the vendors although the FHIR patch can be used for this
  • in which form do the vendors like to have the API description (in IG or in a cookbook) ? feedback no yet ready

Agenda next meeting

  • issues on valuesets
  • UUID issue
  • continuation of resolution of issues
  • input vendors on issue 54

Next meeting: next week Friday 24 Feb at 9AM - needs to be recorded for absent people due to school holiday week

Retrieved from "https://wiki.hl7belgium.org/index.php?title=Minutes_-_Referral_WG_2023-02-17&oldid=2178"