Difference between revisions of "Minutes - Referral WG 2020-11-14"
From Health Level 7 Belgium Wiki
KarlienErauw (talk | contribs) |
KarlienErauw (talk | contribs) |
||
(19 intermediate revisions by the same user not shown) | |||
Line 1: | Line 1: | ||
===== Attendees ===== | ===== Attendees ===== | ||
− | * Robin Bosman | + | * Robin Bosman |
− | * Frederik De Kegel | + | * Frederik De Kegel |
− | * Paul Neyens | + | * Paul Neyens |
− | * Dr Alain Derom | + | * Dr Alain Derom |
− | * Karlien Erauw | + | * Karlien Erauw |
− | * Thibault Mahieu | + | * Thibault Mahieu |
− | * Dieter De Gruyter | + | * Dieter De Gruyter |
− | * Joost Van Averbeke (MIPS) | + | * Joost Van Averbeke (MIPS) |
− | * Hans De Keersmaecker | + | * Hans De Keersmaecker |
− | * Benny Verhamme | + | * Benny Verhamme |
− | * Theo Schumacher | + | * Theo Schumacher |
− | * Peter Laridon | + | * Peter Laridon |
− | |||
− | |||
− | |||
− | |||
− | |||
* Frederik Lenaerts | * Frederik Lenaerts | ||
− | * | + | * José Costa Teixeira |
− | |||
− | |||
===== Excused ===== | ===== Excused ===== | ||
− | |||
* Mieke Buckinx | * Mieke Buckinx | ||
===== Agenda ===== | ===== Agenda ===== | ||
− | * | + | * incoming issues |
+ | * labo ordering | ||
===== Minutes ===== | ===== Minutes ===== | ||
− | * Discussion of the [https://github.com/hl7-be/hl7-be-fhir-laboratory-report/issues/ issues] raised since the previous meeting: | + | * Discussion of the [https://github.com/hl7-be/hl7-be-fhir-laboratory-report/issues/ issues] raised since the previous meeting: no issues were raised since last meeting |
− | + | * Welcome and quick wrap-up to newcomer Joost from MIPS | |
− | + | * Changes in the implementation guide can be followed up [http://build.fhir.org/ig/hl7-be/hl7-be-fhir-laboratory-report/changes.html here] | |
− | + | * Narrative: is this mandatory ? see [http://build.fhir.org/ig/hl7-be/hl7-be-fhir-laboratory-report/guidance.html guidance], FHIR's philosophy is to have one | |
− | ::* [ | + | * Labo ordering, link is included in the guidance, see also [http://build.fhir.org/ig/hl7-be/hl7-be-fhir-referral-prescription/StructureDefinition-be-lab-prescription.html here]: presentation of the different resources |
− | + | ::* based on the ServiceRequest, used for non-medication issues | |
− | * | + | ::* see [http://build.fhir.org/ig/hl7-be/hl7-be-fhir-referral-prescription/ServiceRequest-laboratory-order-example1.xml.html example] |
+ | ::* use of contained resources <> labo report uses bundle : we will evolve in Belgium to a "server" that will handle all referral prescriptions, UHMEP identifier is the reference ID in this system that RIZIV is working on | ||
+ | ::* other FHIR instances are included in the ServiceRequest using the FHIR contained mechanism (using hashtags #) | ||
+ | ::::* not decided if contained mechanism will be mandatory or if bundles will be used | ||
+ | ::* requisition: if multiple orders/prescriptions exist using the same identifier | ||
+ | ::* category will be LaboratoryTest | ||
+ | ::* priority is optional | ||
+ | ::::* in CDA something was foreseen so this has to be included | ||
+ | ::::* f.e. result has to be communicated by phone (does not include urgent) | ||
+ | ::* subject = the patient | ||
+ | ::* encounter: is optional, can be removed | ||
+ | ::* occurence: can this be practical for "kweek" ? or for diabetic day curves | ||
+ | ::* insurance: can have multiple occurences (0..x) | ||
+ | ::* if labo order is needed as a pre-condition for a life insurance, the insurance company will pay and not RIZIV, how will this be handled in the order | ||
+ | ::* bodySite: is this relevant for a labo order ? as this is already included in the specimen - better to remove it as it can cause confusion | ||
+ | ::* patientInstruction: when patient has to be sober or medication cannot be taken 3 days prior | ||
+ | ::* important to keep link with specimen | ||
+ | ::* you can have multiple codes per requester - to be doublechecked | ||
− | * '''Next Meeting:''' Monday | + | * '''Next Meeting:''' Monday January 11 at 4PM |
− | * '''Action points for all:''' please | + | * '''Action points for all:''' please have a closer look at the labo order (through thinking of reallife examples) and provide us with your feedback [http://mailto:karlien.erauw@agoria.be by email (karlien.erauw@agoria.be)] or through this [https://docs.google.com/forms/d/e/1FAIpQLSdrWQl4Uhu7SbtCrEYdXI1cOEmPpKyKSVl7apgNIDIRm-kZ1g/viewform?entry.1353807103=HL7.COUNTRY.FHIR.IG%5CGuidance%20-%20FHIR%20v4.0.1&entry.247644557=The%20laboratory%20order feedback form] |
Latest revision as of 14:56, 11 January 2021
Contents
Attendees
- Robin Bosman
- Frederik De Kegel
- Paul Neyens
- Dr Alain Derom
- Karlien Erauw
- Thibault Mahieu
- Dieter De Gruyter
- Joost Van Averbeke (MIPS)
- Hans De Keersmaecker
- Benny Verhamme
- Theo Schumacher
- Peter Laridon
- Frederik Lenaerts
- José Costa Teixeira
Excused
- Mieke Buckinx
Agenda
- incoming issues
- labo ordering
Minutes
- Discussion of the issues raised since the previous meeting: no issues were raised since last meeting
- Welcome and quick wrap-up to newcomer Joost from MIPS
- Changes in the implementation guide can be followed up here
- Narrative: is this mandatory ? see guidance, FHIR's philosophy is to have one
- Labo ordering, link is included in the guidance, see also here: presentation of the different resources
- based on the ServiceRequest, used for non-medication issues
- see example
- use of contained resources <> labo report uses bundle : we will evolve in Belgium to a "server" that will handle all referral prescriptions, UHMEP identifier is the reference ID in this system that RIZIV is working on
- other FHIR instances are included in the ServiceRequest using the FHIR contained mechanism (using hashtags #)
- not decided if contained mechanism will be mandatory or if bundles will be used
- requisition: if multiple orders/prescriptions exist using the same identifier
- category will be LaboratoryTest
- priority is optional
- in CDA something was foreseen so this has to be included
- f.e. result has to be communicated by phone (does not include urgent)
- subject = the patient
- encounter: is optional, can be removed
- occurence: can this be practical for "kweek" ? or for diabetic day curves
- insurance: can have multiple occurences (0..x)
- if labo order is needed as a pre-condition for a life insurance, the insurance company will pay and not RIZIV, how will this be handled in the order
- bodySite: is this relevant for a labo order ? as this is already included in the specimen - better to remove it as it can cause confusion
- patientInstruction: when patient has to be sober or medication cannot be taken 3 days prior
- important to keep link with specimen
- you can have multiple codes per requester - to be doublechecked
- Next Meeting: Monday January 11 at 4PM
- Action points for all: please have a closer look at the labo order (through thinking of reallife examples) and provide us with your feedback by email (karlien.erauw@agoria.be) or through this feedback form