Difference between revisions of "Minutes - Referral WG 2022-01-05"
From Health Level 7 Belgium Wiki
KarlienErauw (talk | contribs) |
KarlienErauw (talk | contribs) |
||
Line 58: | Line 58: | ||
* [https://github.com/hl7-be/referral/issues/168 Issue 168 - add example scenarios] | * [https://github.com/hl7-be/referral/issues/168 Issue 168 - add example scenarios] | ||
− | ::* [https://docs.google.com/spreadsheets/d/1WJlP1WmTRc_qbGpQJsSaffWZykqchv-x/edit?usp=sharing&ouid=100968134423355597040&rtpof=true&sd=true | + | ::* 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] | ||
+ | ::* part of architecture | ||
+ | |||
+ | * [https://github.com/hl7-be/referral/issues/136 Issue 136- result receiver] | ||
+ | ::* there is an extension on the service request whether the prescriber of the referral has to be notified/when he wants feedback | ||
+ | ::* do we want to make the result optional/mandatory, what would be default value ? | ||
+ | ::* technical solution has to be as simple as possible | ||
+ | ::* it will be mandatory, profiles will need to be checked | ||
+ | |||
+ | * [https://github.com/hl7-be/referral/issues/136 Issue 130- prescription number] | ||
+ | ::* who is going to provide the UUID, client or back-end software - to be discussed next week as Anthony has left | ||
=== Agenda next meeting === | === Agenda next meeting === |
Latest revision as of 16:05, 12 January 2023
Attendees
- Anne Nerenhausen
- Anthony Maton
- Bart Decuypere
- Benjamien Schmitt
- Christophe Behaegel
- Cyprien Janssens
- Hans De Keersmaeker
- Jacques Yakoub
- Jean-Michel Polfliet
- José Costa Teixeira
- Julien Beard
- Karlien Erauw
- Maarten Cobbaert
- Maxime Daive
- Philippe Baise (joined partially)
Excused
- Bart Reekmans
- Ben Goosse
- Dorsan De Fabribeckers
- Geert Vandenhole
- Jean-Francois Coquelet
- Katleen Smedts
- Laurent Lamouline
- Lionel Cremer
- Marleen Van Eygen
- Pieter Devolder
- Richard Francken
Agenda
- resolution of issues
Meeting Minutes
- We agree to schedule the meetings on a weekly basis on Thursday at 3Pm
- Issue 190 on Request Group: see
- still open: how will we retrieve the request group from the service request- use extension or API feature as reverseInclude - this will be part of the architecture overview presentation by Anthony, foreseen for the meeting in 2/3 weeks ; still under investigation
- some preparatory work will be done between the technical people (Athony, José, Bart, ...) to prepare the work/proposals that will afterwards presented in this WG
- Issue 194 New issue will be looked into and presented next week
- Issue 193 - more than 1 medication in case of wound care
- there is unclarity whether or not to use request: will be part of the technical discussion/meeting
- still awaiting info
- we think that both the structure and the businessrules can change because of evolutions in the legislation
- there will be different versions of templates that could result in different versions of profiles, several publications...
- await architecture diagram
- RIZIV will check if the solution of start time + duration is sufficient to replace the start time + end time need: no update yet
- 2nd part on references : remains open as still not found a mature solution - FHIR WG architecture & infra needs to come up with guidelines
- the info here can be the basis for a text version (in the upcoming weeks)
- info on example scenarios: https://build.fhir.org/examplescenario-example.html
- 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
- part of architecture
- there is an extension on the service request whether the prescriber of the referral has to be notified/when he wants feedback
- do we want to make the result optional/mandatory, what would be default value ?
- technical solution has to be as simple as possible
- it will be mandatory, profiles will need to be checked
- who is going to provide the UUID, client or back-end software - to be discussed next week as Anthony has left
Agenda next meeting
- continuation of resolution of issues
Next meeting: next week Thursday 12 Jan at 3PM