Minutes - Referral WG 2022-01-18

Attendees

• TBD !!! 19+1 lotte + tom ipv stefan (medina)
• Dr Alain Derom o
• Frederik De Kegel
• Frederik Lenaerts
• Hans De Keersmaecker
• Hendrik De Moor
• Jean-Michel Polfiet
• Jos Bellen o
• José Costa Teixeira
• Karlien Erauw
• Kristof Jaubin
• Lotte Adriaensen
• Olivier Lothaire
• Peter Laridon
• Philippe Cauchie
• Richard Francken o
• Roland Vueghs
• Sven Bisaro
• Theo Schumacher o
• Thibault Mahieu
• Tom Tollenaere
• Toon Schiemsky o
• Yulia Shornikova
• Veerle Claessens
• Werner De Mulder o

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 by email on Jan 14

Minutes

• Up-to-date list of issues can be consulted here

Issue 64 : proposed solution: : to code

• 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

• 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

https://build.fhir.org/ig/hl7-be/hl7-be-fhir-laboratory-report/branches/issue-64/StructureDefinition-be-observation-laboratory.html#tabs-diff

• This BeCodedAnnotation is the same as Annotation but appended an extension called annotation-code

https://build.fhir.org/ig/hl7-be/hl7-be-fhir-laboratory-report/branches/issue-64/StructureDefinition-coded-annotation.html#tabs-diff

• The annotation-code is an extension defined as having a CodeableConcept

https://build.fhir.org/ig/hl7-be/hl7-be-fhir-laboratory-report/branches/issue-64/StructureDefinition-annotation-code.html#tabs-diff

• 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).

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).

So we extend the element Observation.referenceRange to include an extension named BeReferenceRangeComment, which simply adds an element of type codedAnnotation to referenceRange

• https://build.fhir.org/ig/hl7-be/hl7-be-fhir-laboratory-report/branches/issue-65/StructureDefinition-be-observation-laboratory.html#tabs-diff

other labs can have other cases which might need other codes. They can put random codes or document

• 1 valueset as it is one datatype. These are the values as agreed to start with: lab-test-accreditation, lab-test-subcontractor , lab-referenceRange-comment
• there are comments regarding the test that are put in the note field

• the note can still be used as a plain text field
• plain text with 2 annotation code is possible as 3 notes as it is 1 to many
• annotation code is optional

• Observation - text: markdown : you can plain text or any markdown (string <> plain text - html can be put in string)

• end user can see weird characters

Next Meeting: on Tuesday Feb 1 4PM ! TBC