Difference between revisions of "Minutes - Referral WG 2022-10-20"
From Health Level 7 Belgium Wiki
KarlienErauw (talk | contribs) |
KarlienErauw (talk | contribs) |
||
| (5 intermediate revisions by the same user not shown) | |||
| Line 31: | Line 31: | ||
* issue with high priority: https://github.com/hl7-be/referral/issues/70 | * issue with high priority: https://github.com/hl7-be/referral/issues/70 | ||
::* Discussion of interaction with Snomed CT - if available in Snomed CT, we don't need to foresee it in the FHIR profile ; if not available in Snomed CT, we need to foresee it in the FHIR profile | ::* Discussion of interaction with Snomed CT - if available in Snomed CT, we don't need to foresee it in the FHIR profile ; if not available in Snomed CT, we need to foresee it in the FHIR profile | ||
| − | ::* RIZIV/INAMI will provide the list of SNOMED CT codes corresponding to the list that is now present in the Business Rules document (0.17), so that it becomes possible to analyse the impact on the further | + | ::* RIZIV/INAMI will provide the list of SNOMED CT codes corresponding to the list that is now present in the Business Rules document (0.17), so that it becomes possible to analyse the impact on the further FHIR structure. |
* update on Request Group: | * update on Request Group: | ||
::* updates have been made to the guidance documentation | ::* updates have been made to the guidance documentation | ||
| − | ::* HL7 did not meet yet, although a new concept has been introduced: https://build.fhir.org/requestorchestration | + | ::* HL7 did not meet yet, although a new concept has been introduced: https://build.fhir.org/requestorchestration, looks far too fancy for what we want |
* Annex 81: provided by Jacques Yakoub - for this annex there are some specific value codes: transition is made to the Snomed CT codes. Code for Annex 81 is present in the business rules document and will have to be validated with Snomed CT. Snomed CT does have a long release cycle though so it is important to have a list ready asap... | * Annex 81: provided by Jacques Yakoub - for this annex there are some specific value codes: transition is made to the Snomed CT codes. Code for Annex 81 is present in the business rules document and will have to be validated with Snomed CT. Snomed CT does have a long release cycle though so it is important to have a list ready asap... | ||
| Line 52: | Line 52: | ||
::::* in FHIR incomplete dates can be entered | ::::* in FHIR incomplete dates can be entered | ||
::::* can be seen as an implementation preference | ::::* can be seen as an implementation preference | ||
| + | ::::* nomenclatuur needs a fixed date | ||
| + | ::* 1/ subject, requester, performer: invariant will be created with today's remarks that can be discussed | ||
| + | ::* 2/ validity...: can be implemented | ||
| + | ::* 3/ statusReason: is technical, no discussion needed | ||
=== Agenda next meeting === | === Agenda next meeting === | ||
Latest revision as of 15:24, 20 October 2022
Attendees
- Bart Decuypere
- Benjamien Schmitt
- Christophe Behaegel
- Dorsan De Fabribeckers De Cortils Et Grâce, smals
- Hans De Keersmaecker
- Jacques Yaboub, smals
- Jean-Francois Coquelet
- Karlien Erauw
- Laurent Lamouline, smals
- Maarten Cobbaert
- Marleen Van Eygen
- Philippe Baise
Excused
- Anne Nerenhausen
- Bart Reekmans
- Geert Vandenhole
- Jean-Michel Polfliet
- José Costa Teixeira
- Katleen Smedts
- Pieter Devolder
- Richard Francken
Agenda
- resolution of issues
Meeting Minutes
- no feedback on the latest version of at business rules 0.17 document
- latest version of issues : https://github.com/hl7-be/referral/issues/
- issue with high priority: https://github.com/hl7-be/referral/issues/70
- Discussion of interaction with Snomed CT - if available in Snomed CT, we don't need to foresee it in the FHIR profile ; if not available in Snomed CT, we need to foresee it in the FHIR profile
- RIZIV/INAMI will provide the list of SNOMED CT codes corresponding to the list that is now present in the Business Rules document (0.17), so that it becomes possible to analyse the impact on the further FHIR structure.
- update on Request Group:
- updates have been made to the guidance documentation
- HL7 did not meet yet, although a new concept has been introduced: https://build.fhir.org/requestorchestration, looks far too fancy for what we want
- Annex 81: provided by Jacques Yakoub - for this annex there are some specific value codes: transition is made to the Snomed CT codes. Code for Annex 81 is present in the business rules document and will have to be validated with Snomed CT. Snomed CT does have a long release cycle though so it is important to have a list ready asap...
- https://github.com/hl7-be/referral/issues/
- we discuss the timing datatype discussion that was started by Bart for this WG
- the suggestions on the FHIR chat are not sufficient
- there are at least different 3 use cases that we have to formulate and move forward to HL7 int'l to check if they are covering them
- accept only SSIN as identifier : this might cause issues if an SSIN is not immediately available but receives once afterwards, a SSIN can also change
- a SSIN can get updated in GP softs through RN consult webservice
- will have to be further investigated
- functionality PIX Patient Identity Cross-referencing: https://profiles.ihe.net/ITI/PIXm/index.html
- limit format of dates that are entered
- in FHIR incomplete dates can be entered
- can be seen as an implementation preference
- nomenclatuur needs a fixed date
- 1/ subject, requester, performer: invariant will be created with today's remarks that can be discussed
- 2/ validity...: can be implemented
- 3/ statusReason: is technical, no discussion needed
Agenda next meeting
- updates from HL7 international on RequestGroup
- review issues
Next meeting (to make some progress): NEXT Week Thursday Oct 27 at 4PM
