Difference between revisions of "Minutes - Referral WG 2022-03-22"
From Health Level 7 Belgium Wiki
KarlienErauw (talk | contribs) |
KarlienErauw (talk | contribs) |
||
| Line 72: | Line 72: | ||
::::* how many Snomed CT codes are needed ? it seems that there are +/- 200 | ::::* how many Snomed CT codes are needed ? it seems that there are +/- 200 | ||
::* there will have to be in the implementation guide | ::* there will have to be in the implementation guide | ||
| − | ::* WG decision: if the string value for the result field contains a new line character the content should be rendered in a non-proportional font | + | ::* WG decision: if the string value for the result field contains a new line character the content should be rendered in a non-proportional font. This will be added to the guidance. |
| + | |||
| + | * new issue: plan is to have a new release of the FHIR core resources | ||
| + | ::* canonical url's of the core elements will change | ||
| + | ::* does this FHIR group want to use the new/future version that will be released in the upcoming weeks, i.e. evolve to the 2.X.X version of the Belgian Profiles Standards | ||
| + | ::* WG does not want take a decision now | ||
| + | |||
| + | * note field at diagnostic report level is already available | ||
'''Agenda for next meeting''': | '''Agenda for next meeting''': | ||
* come to a consensus on the open issues - please have a look at the proposed solution for the issues in status "To be validated by WG" | * come to a consensus on the open issues - please have a look at the proposed solution for the issues in status "To be validated by WG" | ||
| − | '''Next Meeting - | + | '''Next Meeting - on Tuesday April 19 at 4PM as the Easter break is coming up - if plenty of new issues arise we'll meet also on April 12''' |
Revision as of 16:11, 22 March 2022
Attendees
- Dr Alain Derom
- Bart Decuypere
- Frederik De Kegel
- Frederik Lenaerts
- Hans De Keersmaecker
- Jean-Michel Polfiet
- Jos Bellen
- Karlien Erauw
- Kristof Jaubin
- Lotte Adriaensen
- Nico Vannieuwenhuyze (arrived late)
- Olivier Lothaire
- Peter Laridon
- Philippe Cauchie
- Stefan Waegemans
- Sven Bisaro
- Thibault Mahieu
- Tom Tollenaere
Excused/Not present
- Alexis Van Zeveren
- Bart Havermans
- Benny Verhamme
- Filip Migom
- Frédéric Istace
- Hendrik De Moor
- Joost Van Averbeke
- José Costa Teixeira
- Mieke Buckinx
- Nick Hermans
- Paul Neyens
- Richard Francken
- Robert Nicolas
- Roland Vueghs
- Theo Schumacher
- Tom Fiers
- Toon Schiemsky
- Veerle Claessens
- Werner De Mulder
- Yulia Shornikova
Agenda
- Discuss and resolve open issues
Minutes
Resolution of open issues: https://github.com/hl7-be/hl7-be-fhir-laboratory-report/projects/1
- Issue 98 - accreditation comment
- what is really required for the Belac accreditation ?
- do we need a general accr comment for the entire report
- if we keep the comment on the result level
- Answers - was already covered before, see all BELAC details here
- Belac requires your accr nbr
- Belac requires info at test level
- Belac requires to put more info in the "footer" ; behind every test you can put more details
- experiences abroad: see question in FHIR chat - CLIA in the US, see here
- Issue 105 - DNA info :
- add it to note to BeLaboratroyObservation level
- validate tomorrow with UZ Gent on 23/3
- Issue 105 - microbiology reporting :
- it is in the scope of the pilot
- structured microbiology lab reporting might be very difficult for some lab/LIS vendors
- for some labs it would require a big change in the microbiology reporting
- it is not an official viewpoint of the vendors
- blob is a an option until the lab is ready for structured microbiology (the labs will need a lot of time for this change)
- receiver will be able to parse it but not be able to save it in a unstructured way ; might not be a big problem
- structured microbiology reporting is possible and the pilot has a proposal/way of working
- does Belgium will only do this in an unstructured way ? no, structured microbiology reporting should be looked into as this is valuable
- how many Snomed CT codes are needed ? it seems that there are +/- 200
- there will have to be in the implementation guide
- WG decision: if the string value for the result field contains a new line character the content should be rendered in a non-proportional font. This will be added to the guidance.
- new issue: plan is to have a new release of the FHIR core resources
- canonical url's of the core elements will change
- does this FHIR group want to use the new/future version that will be released in the upcoming weeks, i.e. evolve to the 2.X.X version of the Belgian Profiles Standards
- WG does not want take a decision now
- note field at diagnostic report level is already available
Agenda for next meeting:
- come to a consensus on the open issues - please have a look at the proposed solution for the issues in status "To be validated by WG"
Next Meeting - on Tuesday April 19 at 4PM as the Easter break is coming up - if plenty of new issues arise we'll meet also on April 12
