Difference between revisions of "Minutes - Referral WG 2022-02-01"

From Health Level 7 Belgium Wiki
(Created page with "==== Attendees ==== * TBD * Bart Decuypere * Frédéric Istace * Frederik De Kegel * Frederik Lenaerts * Hans De Keersmaecker * Hendrik De Moor * Jean-Michel Polfiet * Jo...")
 
 
(5 intermediate revisions by the same user not shown)
Line 1: Line 1:
 
==== Attendees ====
 
==== Attendees ====
* TBD
+
* Dr Alain Derom
 
* Bart Decuypere
 
* Bart Decuypere
* Frédéric Istace
 
* Frederik De Kegel
 
 
* Frederik Lenaerts  
 
* Frederik Lenaerts  
 
* Hans De Keersmaecker  
 
* Hans De Keersmaecker  
* Hendrik De Moor
 
 
* Jean-Michel Polfiet  
 
* Jean-Michel Polfiet  
* Joost Van Averbeke
+
* José Costa Teixeira - joined late
* José Costa Teixeira  
 
 
* Karlien Erauw  
 
* Karlien Erauw  
 
* Kristof Jaubin  
 
* Kristof Jaubin  
Line 16: Line 12:
 
* Peter Laridon
 
* Peter Laridon
 
* Philippe Cauchie  
 
* Philippe Cauchie  
* Roland Vueghs
 
 
* Sven Bisaro
 
* Sven Bisaro
 
* Thibault Mahieu  
 
* Thibault Mahieu  
 +
* Tom Fiers
 
* Tom Tollenaere  
 
* Tom Tollenaere  
* Veerle Claessens
 
 
* Yulia Shornikova  
 
* Yulia Shornikova  
 +
* Werner De Mulder
  
 
==== Excused/Not present ====  
 
==== Excused/Not present ====  
* Dr Alain Derom
 
 
* Alexis Van Zeveren
 
* Alexis Van Zeveren
 
* Benny Verhamme  
 
* Benny Verhamme  
 +
* Frédéric Istace
 +
* Frederik De Kegel
 
* Filip Migom
 
* Filip Migom
 +
* Hendrik De Moor
 +
* Joost Van Averbeke
 
* Jos Bellen  
 
* Jos Bellen  
 
* Mieke Buckinx
 
* Mieke Buckinx
Line 33: Line 32:
 
* Nico Vannieuwenhuyze  
 
* Nico Vannieuwenhuyze  
 
* Paul Neyens
 
* Paul Neyens
* Peter Laridon
 
 
* Richard Francken  
 
* Richard Francken  
 
* Robert Nicolas
 
* Robert Nicolas
 +
* Roland Vueghs
 
* Theo Schumacher  
 
* Theo Schumacher  
* Tom Fiers
 
 
* Toon Schiemsky  
 
* Toon Schiemsky  
 
* Richard Francken  
 
* Richard Francken  
 
* Stefan Waegemans  
 
* Stefan Waegemans  
* Werner De Mulder
+
* Veerle Claessens
  
 
==== Agenda ====
 
==== Agenda ====
* Discuss proposed solutions on issues #64 and #65 as sent out by email on Jan 14
+
* Discuss and resolve open issues
  
 
==== 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:  
+
* Update from last week's resolutions:
::* 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
+
::* Issue #75: not put clinical information in the narrative - is confirmed
::* 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:
+
::* Issue 64 & 65: proposed solution of AnnotationCode has been tested and seems ok
::* 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
+
* Issue 87: new issue raised by Thibault
::* 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
+
::* linking requests to multiple specimens
::* 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
+
::* FHIR int'l specification: cardinality is 0:1 so max 1 specimen - int'l specification cannot be  
 +
::::* add field to put additionalSpecimens
 +
::::* every lab does this daily so we need to check how this is dealt with internationally
 +
::::* do we need to link the results to the sample ?
  
* Issue 65 : proposed solution:
+
* Issue 86: UCUM vs display value
::* 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
+
::* unit is the display value, code contains the UCUM unit
::* https://build.fhir.org/ig/hl7-be/hl7-be-fhir-laboratory-report/branches/issue-65/StructureDefinition-be-observation-laboratory.html#tabs-diff
 
  
* The group agrees on this resolutions using annotation code
+
* Issue 81: ObservationInterpretation coding system
* The following are the agreed values for the valueset to start with: lab-test-accreditation, lab-test-subcontractor , lab-referencerange-comment
+
::* limit to HH - H - N - L -LL which is a subset of the indicated codeSystem https://terminology.hl7.org/3.0.0/CodeSystem-v3-ObservationInterpretation.html
* There are comments regarding the test that are put in the note field
+
::* this one can be used now
::* the note can still be used as a plain text field since annotation code is optional
+
::::* Thibault would like to add A and AA to the list - will be added
::* plain text with 2 annotation code is possible as 3 notes as it is 1 to many
+
::* other values could be added later on
  
* Observation - text: markdown : you can plain text or any markdown (string <> plain text - html can be put in string)
+
* Issue 82: add the use of Quantity:code/unit to guidance
::* end user can see weird characters
+
::* the use of Quantity:code is mandatory and will be used by the visualizer, the use of Quantity:unit is optional
::* We try is we can put markdown as string as it is not our objective to use markdown in Belgium : is not possible, so we need to add something in guidance : plain text without markdown is strongly recommended
+
::* the Guidance will be modified soon
  
* Issue #75: empty narrative
+
* Issue 83: use of eHealthBox metadata
::* the lab must enter data in the narrative - if we put info in the narrative then we have to test that the info is correct !
+
::* not related to FHIR so a N/A issue for this WG
::::* narratives should not be in the scope of the testing
+
::* when sending a prtocol some metadata will be sent
::::* risk that receiving party will use the narrative instead of the coded info
+
::::* HC-FunctionalType= "fhir-lab"
::::* up until now nothing has been set what part of the protocol to put where in the narrative
+
::::* CM-GeneratingSoftware= ""
::* narrative can be empty for machine-to-machine communication
+
::::* CM-GeneratingSoftwareVersion= ""
::* change narrative into empty
 
  
* Issue 74 : embed info is possible in 2 ways in FHIR - proposal :
+
* Issue 21: still open because it has impact on the LabOrder
::* use presented form to send the protocol/human readable copy here (in PDF/word)
+
::* will be dealt with once we start with structured requests/orders
::* use media for other annexes
 
  
 +
* '''Action items''':
 +
::* check out issue on multiple specimens and how this is dealt with at int'l level since cardinality is 0:1
  
 
'''Next Meeting: on Tuesday Feb 15 4PM'''
 
'''Next Meeting: on Tuesday Feb 15 4PM'''

Latest revision as of 13:08, 14 February 2022

Attendees

  • Dr Alain Derom
  • Bart Decuypere
  • Frederik Lenaerts
  • Hans De Keersmaecker
  • Jean-Michel Polfiet
  • José Costa Teixeira - joined late
  • Karlien Erauw
  • Kristof Jaubin
  • Lotte Adriaensen
  • Olivier Lothaire
  • Peter Laridon
  • Philippe Cauchie
  • Sven Bisaro
  • Thibault Mahieu
  • Tom Fiers
  • Tom Tollenaere
  • Yulia Shornikova
  • Werner De Mulder

Excused/Not present

  • Alexis Van Zeveren
  • Benny Verhamme
  • Frédéric Istace
  • Frederik De Kegel
  • Filip Migom
  • Hendrik De Moor
  • Joost Van Averbeke
  • Jos Bellen
  • Mieke Buckinx
  • Nick Hermans
  • Nico Vannieuwenhuyze
  • Paul Neyens
  • Richard Francken
  • Robert Nicolas
  • Roland Vueghs
  • Theo Schumacher
  • Toon Schiemsky
  • Richard Francken
  • Stefan Waegemans
  • Veerle Claessens

Agenda

  • Discuss and resolve open issues

Minutes

  • Up-to-date list of issues can be consulted here
  • Update from last week's resolutions:
  • Issue #75: not put clinical information in the narrative - is confirmed
  • Issue 64 & 65: proposed solution of AnnotationCode has been tested and seems ok
  • Issue 87: new issue raised by Thibault
  • linking requests to multiple specimens
  • FHIR int'l specification: cardinality is 0:1 so max 1 specimen - int'l specification cannot be
  • add field to put additionalSpecimens
  • every lab does this daily so we need to check how this is dealt with internationally
  • do we need to link the results to the sample ?
  • Issue 86: UCUM vs display value
  • unit is the display value, code contains the UCUM unit
  • Issue 81: ObservationInterpretation coding system
  • Thibault would like to add A and AA to the list - will be added
  • other values could be added later on
  • Issue 82: add the use of Quantity:code/unit to guidance
  • the use of Quantity:code is mandatory and will be used by the visualizer, the use of Quantity:unit is optional
  • the Guidance will be modified soon
  • Issue 83: use of eHealthBox metadata
  • not related to FHIR so a N/A issue for this WG
  • when sending a prtocol some metadata will be sent
  • HC-FunctionalType= "fhir-lab"
  • CM-GeneratingSoftware= ""
  • CM-GeneratingSoftwareVersion= ""
  • Issue 21: still open because it has impact on the LabOrder
  • will be dealt with once we start with structured requests/orders
  • Action items:
  • check out issue on multiple specimens and how this is dealt with at int'l level since cardinality is 0:1

Next Meeting: on Tuesday Feb 15 4PM

Meetings are happening again biweekly