Difference between revisions of "Minutes - Referral WG 2020-03-08"
From Health Level 7 Belgium Wiki
KarlienErauw (talk | contribs) |
KarlienErauw (talk | contribs) |
||
| (3 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
===== Attendees ===== | ===== Attendees ===== | ||
* Robin Bosman | * Robin Bosman | ||
| − | + | * Benny Verhamme | |
| − | * Benny Verhamme | ||
| − | |||
* Frederik Lenaerts | * Frederik Lenaerts | ||
* Gaston Verelst | * Gaston Verelst | ||
| Line 9: | Line 7: | ||
* Jean-Michel Polfiet | * Jean-Michel Polfiet | ||
* Joost Van Averbeke | * Joost Van Averbeke | ||
| − | + | * José Costa Teixeira | |
| − | * José Costa Teixeira | ||
* Karlien Erauw | * Karlien Erauw | ||
* Kristof Jaubin | * Kristof Jaubin | ||
* Olivier Lothaire | * Olivier Lothaire | ||
| − | + | * Peter Laridon (arrived at 4.30PM) | |
| − | * Peter Laridon | + | * Thibault Mahieu |
| − | + | * Tom Fiers | |
| − | * Thibault Mahieu | ||
| − | * Tom Fiers | ||
===== Excused/Not present ===== | ===== Excused/Not present ===== | ||
* Dr Alain Derom | * Dr Alain Derom | ||
| + | * Frank Vandewiele | ||
* Hendrik Plaetinck | * Hendrik Plaetinck | ||
| + | * Jos Bellen | ||
| + | * Paul Neyens | ||
| + | * Theo Schumacher | ||
===== Agenda ===== | ===== Agenda ===== | ||
| Line 29: | Line 28: | ||
===== Minutes ===== | ===== Minutes ===== | ||
| − | * | + | * feedback of HL7 international on https://build.fhir.org/ig/hl7-be/hl7-be-fhir-laboratory-report/Observation-obsDynamic1.xml.html |
| − | * | + | ::* what if we have a code in the element code and we need to express extra information like relative time, do we need to use an extension and is this the only option ? You can also use Components for that, you can qualify the central codes in an observation. HL7 International shall clarify this |
| + | ::::* glucose is not a good example for that | ||
| + | ::::* relativeTimeQualifier is now a component in the [http://build.fhir.org/ig/hl7-be/hl7-be-fhir-laboratory-report/StructureDefinition-be-observation-laboratory.html lab result profile] | ||
| + | |||
| + | ::* LIS systems will produce content (bundles, contained,...): will the receivers be able to handle all this? This should not be so difficult to handle | ||
| + | |||
| + | |||
| + | * Examples for creatinine clearance & microbiology : have been provided by Benny, thanks for that ; Robin has worked on it, unfortunately not yet published due to HL7 technical issue, they will be published as soon as technical possible | ||
| + | * There are now more examples published, see them all on the bottom of the page: | ||
::* https://build.fhir.org/ig/hl7-be/hl7-be-fhir-laboratory-report/Observation-obsDynamic0.xml.html | ::* https://build.fhir.org/ig/hl7-be/hl7-be-fhir-laboratory-report/Observation-obsDynamic0.xml.html | ||
::* https://build.fhir.org/ig/hl7-be/hl7-be-fhir-laboratory-report/Observation-obsDynamic1.xml.html | ::* https://build.fhir.org/ig/hl7-be/hl7-be-fhir-laboratory-report/Observation-obsDynamic1.xml.html | ||
| Line 37: | Line 44: | ||
::* https://build.fhir.org/ig/hl7-be/hl7-be-fhir-laboratory-report/Observation-obsUrineScreening.xml.html | ::* https://build.fhir.org/ig/hl7-be/hl7-be-fhir-laboratory-report/Observation-obsUrineScreening.xml.html | ||
| − | * | + | * A possible solution can be: a laboratory report can be diagnostic report with FHIR instance and all will be there as contained resource. Let's discuss this next time |
| − | : | + | * Robin will more work on the contained example as well as examples on logical reference |
| − | |||
| − | * | ||
| − | |||
| − | * Action points: | + | * Action points for next meeting: |
| − | ::* | + | ::* come prepared with feedback on today's discussed topics |
| − | |||
| − | '''Next Meeting:''' Monday March | + | '''Next Meeting:''' Monday March 22 at 4PM |
Latest revision as of 12:27, 12 April 2021
Attendees
- Robin Bosman
- Benny Verhamme
- Frederik Lenaerts
- Gaston Verelst
- Hans De Keersmaecker
- Jean-Michel Polfiet
- Joost Van Averbeke
- José Costa Teixeira
- Karlien Erauw
- Kristof Jaubin
- Olivier Lothaire
- Peter Laridon (arrived at 4.30PM)
- Thibault Mahieu
- Tom Fiers
Excused/Not present
- Dr Alain Derom
- Frank Vandewiele
- Hendrik Plaetinck
- Jos Bellen
- Paul Neyens
- Theo Schumacher
Agenda
- updated items since last meeting
- examples
Minutes
- feedback of HL7 international on https://build.fhir.org/ig/hl7-be/hl7-be-fhir-laboratory-report/Observation-obsDynamic1.xml.html
- what if we have a code in the element code and we need to express extra information like relative time, do we need to use an extension and is this the only option ? You can also use Components for that, you can qualify the central codes in an observation. HL7 International shall clarify this
- glucose is not a good example for that
- relativeTimeQualifier is now a component in the lab result profile
- LIS systems will produce content (bundles, contained,...): will the receivers be able to handle all this? This should not be so difficult to handle
- Examples for creatinine clearance & microbiology : have been provided by Benny, thanks for that ; Robin has worked on it, unfortunately not yet published due to HL7 technical issue, they will be published as soon as technical possible
- There are now more examples published, see them all on the bottom of the page:
- https://build.fhir.org/ig/hl7-be/hl7-be-fhir-laboratory-report/Observation-obsDynamic0.xml.html
- https://build.fhir.org/ig/hl7-be/hl7-be-fhir-laboratory-report/Observation-obsDynamic1.xml.html
- https://build.fhir.org/ig/hl7-be/hl7-be-fhir-laboratory-report/Observation-obsDynamic2.xml.html
- https://build.fhir.org/ig/hl7-be/hl7-be-fhir-laboratory-report/Observation-obsKetonen.xml.html
- https://build.fhir.org/ig/hl7-be/hl7-be-fhir-laboratory-report/Observation-obsUrineScreening.xml.html
- A possible solution can be: a laboratory report can be diagnostic report with FHIR instance and all will be there as contained resource. Let's discuss this next time
- Robin will more work on the contained example as well as examples on logical reference
- Action points for next meeting:
- come prepared with feedback on today's discussed topics
Next Meeting: Monday March 22 at 4PM
