Difference between revisions of "Minutes - Referral WG 2022-01-18"
From Health Level 7 Belgium Wiki
KarlienErauw (talk | contribs) |
KarlienErauw (talk | contribs) |
||
| Line 1: | Line 1: | ||
===== Attendees ===== | ===== Attendees ===== | ||
| − | * TBD | + | * TBD |
| − | * | + | * Bart Decuypere |
| + | * Frédéric Istace | ||
* Frederik De Kegel | * Frederik De Kegel | ||
* Frederik Lenaerts | * Frederik Lenaerts | ||
| Line 7: | Line 8: | ||
* Hendrik De Moor | * Hendrik De Moor | ||
* Jean-Michel Polfiet | * Jean-Michel Polfiet | ||
| − | |||
* José Costa Teixeira | * José Costa Teixeira | ||
* Karlien Erauw | * Karlien Erauw | ||
| Line 15: | Line 15: | ||
* Peter Laridon | * Peter Laridon | ||
* Philippe Cauchie | * Philippe Cauchie | ||
| − | |||
* Roland Vueghs | * Roland Vueghs | ||
* Sven Bisaro | * Sven Bisaro | ||
| − | |||
* Thibault Mahieu | * Thibault Mahieu | ||
* Tom Tollenaere | * Tom Tollenaere | ||
| − | * | + | * Veerle Claessens |
* Yulia Shornikova | * Yulia Shornikova | ||
| − | |||
| − | |||
===== Excused/Not present ===== | ===== Excused/Not present ===== | ||
| − | * | + | * Dr Alain Derom |
* Alexis Van Zeveren | * Alexis Van Zeveren | ||
| − | |||
* Benny Verhamme | * Benny Verhamme | ||
* Filip Migom | * Filip Migom | ||
| − | |||
* Joost Van Averbeke | * Joost Van Averbeke | ||
* Jos Bellen | * Jos Bellen | ||
| Line 40: | Line 34: | ||
* Paul Neyens | * Paul Neyens | ||
* Peter Laridon | * Peter Laridon | ||
| + | * Richard Francken | ||
* Robert Nicolas | * Robert Nicolas | ||
| + | * Theo Schumacher | ||
* Tom Fiers | * Tom Fiers | ||
| + | * Toon Schiemsky | ||
* Richard Francken | * Richard Francken | ||
* Stefan Waegemans | * Stefan Waegemans | ||
| − | + | * Werner De Mulder | |
===== Agenda ===== | ===== Agenda ===== | ||
| Line 51: | Line 48: | ||
===== 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:''' : | + | * ''' 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 | ||
| − | + | ::* 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: | |
| − | * 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 |
| − | |||
| − | * 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 | 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 | |
| − | * 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 | 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 | |
| − | * 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 | 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). | |
| − | * 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 | 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:''' | + | *''' 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 | ||
| − | * https://build.fhir.org/ig/hl7-be/hl7-be-fhir-laboratory-report/branches/issue-65/StructureDefinition-be-observation-laboratory.html#tabs-diff | + | ::* 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 resolution using annotation code | |
| − | * | + | * The following are the agreed values for the valueset 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 | + | ::* the note can still be used as a plain text field since annotation code is optional |
::* plain text with 2 annotation code is possible as 3 notes as it is 1 to many | ::* plain text with 2 annotation code is possible as 3 notes as it is 1 to many | ||
| − | |||
* Observation - text: markdown : you can plain text or any markdown (string <> plain text - html can be put in string) | * Observation - text: markdown : you can plain text or any markdown (string <> plain text - html can be put in string) | ||
| Line 86: | Line 77: | ||
* Issue #75: empty narrative | * Issue #75: empty narrative | ||
| − | ::* the lab must enter data in the narrative | + | ::* 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 ! |
| − | |||
::::* narratives should not be in the scope of the testing | ::::* narratives should not be in the scope of the testing | ||
::::* risk that receiving party will use the narrative instead of the coded info | ::::* risk that receiving party will use the narrative instead of the coded info | ||
::::* up until now nothing has been set what part of the protocol to put where in the narrative | ::::* up until now nothing has been set what part of the protocol to put where in the narrative | ||
::* narrative can be empty for machine-to-machine communication | ::* narrative can be empty for machine-to-machine communication | ||
| + | ::* change narrative into empty | ||
| − | * Issue 74 : embed info is possible in 2 ways in FHIR | + | * Issue 74 : embed info is possible in 2 ways in FHIR - proposal : |
| − | ::* | + | ::* use presented form to send the protocol/human readable copy here (in PDF/word) |
| − | ::* other annexes | + | ::* use media for other annexes |
| − | '''Next Meeting: | + | '''Next Meeting: on Tuesday Feb 1 4PM''' |
| + | Meetings will happen again biweekly | ||
Revision as of 18:14, 18 January 2022
Attendees
- TBD
- Bart Decuypere
- Frédéric Istace
- Frederik De Kegel
- Frederik Lenaerts
- Hans De Keersmaecker
- Hendrik De Moor
- Jean-Michel Polfiet
- José Costa Teixeira
- Karlien Erauw
- Kristof Jaubin
- Lotte Adriaensen
- Olivier Lothaire
- Peter Laridon
- Philippe Cauchie
- Roland Vueghs
- Sven Bisaro
- Thibault Mahieu
- Tom Tollenaere
- Veerle Claessens
- Yulia Shornikova
Excused/Not present
- Dr Alain Derom
- Alexis Van Zeveren
- Benny Verhamme
- Filip Migom
- Joost Van Averbeke
- Jos Bellen
- Mieke Buckinx
- Nick Hermans
- Nico Vannieuwenhuyze
- Paul Neyens
- Peter Laridon
- Richard Francken
- Robert Nicolas
- Theo Schumacher
- Tom Fiers
- Toon Schiemsky
- Richard Francken
- Stefan Waegemans
- Werner De Mulder
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: :
- 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
- the group agrees on this resolution using annotation code
- The following are the agreed values for the valueset 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 since annotation code is optional
- plain text with 2 annotation code is possible as 3 notes as it is 1 to many
- 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
- 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
- Issue #75: empty narrative
- 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 !
- narratives should not be in the scope of the testing
- risk that receiving party will use the narrative instead of the coded info
- up until now nothing has been set what part of the protocol to put where in the narrative
- narrative can be empty for machine-to-machine communication
- change narrative into empty
- Issue 74 : embed info is possible in 2 ways in FHIR - proposal :
- use presented form to send the protocol/human readable copy here (in PDF/word)
- use media for other annexes
Next Meeting: on Tuesday Feb 1 4PM
Meetings will happen again biweekly
