Difference between revisions of "Minutes - Referral WG 2022-01-18"
From Health Level 7 Belgium Wiki
KarlienErauw (talk | contribs) |
KarlienErauw (talk | contribs) |
||
| Line 45: | Line 45: | ||
===== Minutes ===== | ===== Minutes ===== | ||
* Up-to-date list of issues can be consulted [https://github.com/hl7-be/hl7-be-fhir-laboratory-report/issues here] | * Up-to-date list of issues can be consulted [https://github.com/hl7-be/hl7-be-fhir-laboratory-report/issues here] | ||
| − | ''' | + | ''' Issue 64 : proposed solution:''' |
* José discussed with other colleagues and here’s the proposed solution: | * José discussed with other colleagues and here’s the proposed solution: | ||
https://chat.fhir.org/#narrow/stream/179256-Orders-and.20Observation.20WG/topic/Observation.20comments | https://chat.fhir.org/#narrow/stream/179256-Orders-and.20Observation.20WG/topic/Observation.20comments | ||
| Line 63: | Line 63: | ||
https://build.fhir.org/ig/hl7-be/hl7-be-fhir-laboratory-report/branches/issue-64/ValueSet-be-vs-coded-annotation-types.html | https://build.fhir.org/ig/hl7-be/hl7-be-fhir-laboratory-report/branches/issue-64/ValueSet-be-vs-coded-annotation-types.html | ||
| − | ''' | + | ''' Issue 65 : proposed solution:''' |
* The solution is simple after we have issue 64 resolved: We simply use the CodedAnnotation in the ReferenceRange (as an extension). | * The solution is simple after we have issue 64 resolved: We simply use the CodedAnnotation in the ReferenceRange (as an extension). | ||
So we extend the element Observation.referenceRange to include an extension named BeReferenceRangeComment, which simply adds an element of type codedAnnotation to referenceRange | So we extend the element Observation.referenceRange to include an extension named BeReferenceRangeComment, which simply adds an element of type codedAnnotation to referenceRange | ||
Revision as of 16:07, 14 January 2022
Attendees
- TBD !!!
- Dr Alain Derom
- Frederik De Kegel
- Frederik Lenaerts
- Hans De Keersmaecker
- Jean-Michel Polfiet
- Jos Bellen
- José Costa Teixeira
- Karlien Erauw
- Kristof Jaubin
- Lotte Adriaensen
- Olivier Lothaire
- Philippe Cauchie
- Richard Francken
- Theo Schumacher
- Thibault Mahieu
- Tom Tollenaere
- Toon Schiemsky
- Werner De Mulder
Excused/Not present
- TBD
- Alexis Van Zeveren
- Bart Decuypere
- Benny Verhamme
- Filip Migom
- Frédéric Istace
- Joost Van Averbeke
- Jos Bellen
- Mieke Buckinx
- Nick Hermans
- Nico Vannieuwenhuyze
- Paul Neyens
- Peter Laridon
- Robert Nicolas
- Tom Fiers
- Richard Francken
- Stefan Waegemans
Agenda
- Discuss proposed solutions on issues #64 and #65 as sent out on Jan 14
Minutes
- Up-to-date list of issues can be consulted here
Issue 64 : proposed solution:
- José discussed with other colleagues and here’s the proposed solution:
- We can have a data type CodedAnnotation which is an extension from the Annotation. From then on, we can add “tags” to any of these annotations, wherever we use them. I made the commit to show the solution – here’s the drill-down:
- The Observation.note is no longer an Annotation but the new data type called BeCodedAnnotation
- This BeCodedAnnotation is the same as Annotation but appended an extension called annotation-code
- The annotation-code is an extension defined as having a CodeableConcept
- This is bound by a valueset - we need to define the values for those tags. We can do it anytime soon (or leave as is, because the binding is not required).
Issue 65 : proposed solution:
- The solution is simple after we have issue 64 resolved: We simply use the CodedAnnotation in the ReferenceRange (as an extension).
So we extend the element Observation.referenceRange to include an extension named BeReferenceRangeComment, which simply adds an element of type codedAnnotation to referenceRange
Next Meeting: on Tuesday Feb 1 4PM ! TBC
