Difference between revisions of "Minutes - Referral WG 2022-03-31"
From Health Level 7 Belgium Wiki
KarlienErauw (talk | contribs) |
KarlienErauw (talk | contribs) |
||
| (7 intermediate revisions by the same user not shown) | |||
| Line 19: | Line 19: | ||
=== Meeting Minutes === | === Meeting Minutes === | ||
| − | * RIZIV has | + | * RIZIV has updated the logical model and has communicated this to the members of group last week. Hans has reviewed the document. We are going over all the questions and comment on them, [https://docs.google.com/document/d/1Jv22v42LYZ9urDHAjyqdREjay1us2X10/edit?usp=sharing&ouid=105469359652835948544&rtpof=true&sd=true see comments and output of today's discussion here] |
| − | + | ||
| − | * [https://github.com/hl7-be/hl7-be-fhir-referral-prescription/issues | + | * Resolution of [https://github.com/hl7-be/hl7-be-fhir-referral-prescription/issues github issues]: |
* [https://github.com/hl7-be/hl7-be-fhir-referral-prescription/issues/39 Issue #39 - body laterality free text] | * [https://github.com/hl7-be/hl7-be-fhir-referral-prescription/issues/39 Issue #39 - body laterality free text] | ||
::* free text is not recommended | ::* free text is not recommended | ||
| − | ::* where can it be found in the Business Rules document ? it is added in the new version of the document but still requires validation by the NRC and the WG business rules ; work is still ongoing with careproviders in which requests body laterality is useful. To be determined later. | + | ::* where can it be found in the Business Rules document ? it is added in the new version of the document but still requires validation by the NRC and the WG business rules ; work is also still ongoing with careproviders in which requests body laterality is useful. To be determined later. |
| − | * [https://github.com/hl7-be/hl7-be-fhir-referral-prescription/pull/18 Issue 18 service requested will be own valueset] | + | * [https://github.com/hl7-be/hl7-be-fhir-referral-prescription/pull/18 Issue 18 - service requested will be own valueset] |
::* all business rules are listed, will be presented by RIZIV to the business WG, feedback will come soon | ::* all business rules are listed, will be presented by RIZIV to the business WG, feedback will come soon | ||
::* remains open | ::* remains open | ||
| Line 32: | Line 32: | ||
* [https://github.com/hl7-be/hl7-be-fhir-referral-prescription/issues/3 Issue 3 - ExecutionPeriod] | * [https://github.com/hl7-be/hl7-be-fhir-referral-prescription/issues/3 Issue 3 - ExecutionPeriod] | ||
::* there are slides about the meaning of the different execution periods on which there was a question by José | ::* there are slides about the meaning of the different execution periods on which there was a question by José | ||
| − | ::* See here: timeline of a prescription | + | ::* [https://drive.google.com/file/d/1mv7V-FPrb3BdgYp3CN-iaT1EpCWQXkZE/view?usp=sharing See here: timeline of a prescription (RIZIV slide)] |
::::* dates can be anti-dated | ::::* dates can be anti-dated | ||
::::* a prescription can f.e. be started 5 days in the past = validation start date | ::::* a prescription can f.e. be started 5 days in the past = validation start date | ||
::::* validation end date = last day that the prescription has to be started | ::::* validation end date = last day that the prescription has to be started | ||
| − | ::::* both mark the "validation period", see here | + | ::::* both mark the "validation period", [https://drive.google.com/file/d/1U36JN7rRghHsTXWtu3Ve7S1uYLMGDXvo/view?usp=sharing see here (RIZIV slide)] |
::::* recorded date = fixed date | ::::* recorded date = fixed date | ||
::::* treatment end date: can be overruled by the prescriber - ends the "treatment period" | ::::* treatment end date: can be overruled by the prescriber - ends the "treatment period" | ||
| Line 42: | Line 42: | ||
::* issue can be closed, will have to be dealt with later upon profiling, given input is sufficient | ::* issue can be closed, will have to be dealt with later upon profiling, given input is sufficient | ||
| − | + | ''' Agenda next meeting''' | |
| − | + | * resolution of issues in github | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | ''' | ||
| − | * | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | '''Next meeting : | + | '''Next meeting : April 28 at 4PM''' |
Latest revision as of 14:38, 28 April 2022
Contents
Attendees
- Anne Nerenhausen
- Bart Decuypere
- Benjamien Schmitt
- Hans De Keersmaecker
- Karlien Erauw
- Maarten Cobbaert
- Marleen Van Eygen
- Robin van Everdingen (Interoplab.NL)
- Tim Weltens
Excused
- Jean-Michel Polfliet
- José Costa Teixeira
Agenda
- Feedback on logical model
- Resolution of github issues
Meeting Minutes
- RIZIV has updated the logical model and has communicated this to the members of group last week. Hans has reviewed the document. We are going over all the questions and comment on them, see comments and output of today's discussion here
- Resolution of github issues:
- Issue #39 - body laterality free text
- free text is not recommended
- where can it be found in the Business Rules document ? it is added in the new version of the document but still requires validation by the NRC and the WG business rules ; work is also still ongoing with careproviders in which requests body laterality is useful. To be determined later.
- all business rules are listed, will be presented by RIZIV to the business WG, feedback will come soon
- remains open
- there are slides about the meaning of the different execution periods on which there was a question by José
- See here: timeline of a prescription (RIZIV slide)
- dates can be anti-dated
- a prescription can f.e. be started 5 days in the past = validation start date
- validation end date = last day that the prescription has to be started
- both mark the "validation period", see here (RIZIV slide)
- recorded date = fixed date
- treatment end date: can be overruled by the prescriber - ends the "treatment period"
- the validation period and treatment period are not referenced in the business rules document
- issue can be closed, will have to be dealt with later upon profiling, given input is sufficient
Agenda next meeting
- resolution of issues in github
Next meeting : April 28 at 4PM
