Difference between revisions of "Minutes - Medication WG 2023-01-31"
From Health Level 7 Belgium Wiki
KarlienErauw (talk | contribs) |
KarlienErauw (talk | contribs) |
||
| Line 40: | Line 40: | ||
::* how do we handle packaging ? | ::* how do we handle packaging ? | ||
::* here's a [https://docs.google.com/document/d/1zE6XajrjaInuDHA6yT6plZAx7AimlBIT/edit list that is currently used on the field] | ::* here's a [https://docs.google.com/document/d/1zE6XajrjaInuDHA6yT6plZAx7AimlBIT/edit list that is currently used on the field] | ||
| − | ::* all participants are asked to [https://github.com/hl7-be/medication-record/issues/24#issuecomment-1402685781 review the work done] | + | ::* all participants are asked to [https://github.com/hl7-be/medication-record/issues/24#issuecomment-1402685781 review the work done] and the document that is referenced in the issue |
| − | ::* can the list be turned into 2 parts (one without questions, another one with questions) so that we can compile it to one list and afterwards we can ask feedback to NRC | + | ::* can the list be turned into 2 parts (one without questions, another one with questions to raise to eHealth platform-kmehr experts TBC) so that we can compile it to one list and afterwards we can ask feedback to NRC |
| − | * | + | * The current mapping from the current kmehr medication scheme (the parts that matter) to FHIR resources |
| − | |||
::* see https://build.fhir.org/ig/hl7-be/medication-record/medicationrecord-fhir-resources.html | ::* see https://build.fhir.org/ig/hl7-be/medication-record/medicationrecord-fhir-resources.html | ||
::* kmehr: see https://www.ehealth.fgov.be/standards/kmehr/en/transactions/medication-scheme-element | ::* kmehr: see https://www.ehealth.fgov.be/standards/kmehr/en/transactions/medication-scheme-element | ||
| − | ::* | + | ::* there is some documentation missing on the kmehr medication scheme |
| − | ::::* a | + | ::* the FHIR medication scheme has to be at least functional as the current kmehr MS |
| − | + | ::* the current MS is around messages and as such sender & receiver - this will be different in FHIR | |
| + | ::* FHIR MS will be a document that can be consulted many times | ||
| + | ::* author in kmehr context: the author that decides that the content is good enough to send the message | ||
| + | ::::* we will recommend that in FHIR we need an "author" that is responsible for the whole of the MS | ||
| + | ::::* FHIR has a lifecycle that currently does not exist | ||
| + | ::* the FHIR MS will be a bundle | ||
'''Agenda items for next meeting''' | '''Agenda items for next meeting''' | ||
* review valuesets | * review valuesets | ||
| − | |||
* review logical model for medication scheme (to prepare by José) | * review logical model for medication scheme (to prepare by José) | ||
| − | '''Next meeting | + | '''Next meeting 7 Feb at 11AM''' |
Revision as of 11:16, 31 January 2023
Attendees
- Bart Decuypere
- Jan Lenie
- Jens Penny
- José Costa Teixeira
- Karlien Erauw
- Lodewijk Sioen
- Pablo Christiaens
- Thomas Van Langendonck
- Tom Henkens
Excused/Not present
- Annemieke Vergauwe
- Anne Nerenhausen
- Bruno Casneuf
- Dieter Sauvillers
- Hanne Vuegen
- Jean-Michel Polfliet
- Katrien Thorré
- Lars Vanreppelen
- Richard Francken
- Marc Buckens
- Nick Hermans
- Nils Devos
- Tom De Backer
- Walter Bollaert
- Will van Norel
Agenda
- Update on work done on value set
- Mapping from the current kmehr medication scheme into FHIR
Minutes
- Update on work done value sets : see here
- NHS recommends UCUM if available
- Jens started with the kmehr codes (as we will need a mapping with kmehr as everything is in kmehr now and we don't want to lose functionality) and proposes to extend it to encompass ucum
- ucum provides endless combinations, where will be stop this ?
- kmehr was not complete
- Belgian Snomed CT is available from here, choosing the Belgian version
- how do we handle packaging ?
- here's a list that is currently used on the field
- all participants are asked to review the work done and the document that is referenced in the issue
- can the list be turned into 2 parts (one without questions, another one with questions to raise to eHealth platform-kmehr experts TBC) so that we can compile it to one list and afterwards we can ask feedback to NRC
- The current mapping from the current kmehr medication scheme (the parts that matter) to FHIR resources
- see https://build.fhir.org/ig/hl7-be/medication-record/medicationrecord-fhir-resources.html
- kmehr: see https://www.ehealth.fgov.be/standards/kmehr/en/transactions/medication-scheme-element
- there is some documentation missing on the kmehr medication scheme
- the FHIR medication scheme has to be at least functional as the current kmehr MS
- the current MS is around messages and as such sender & receiver - this will be different in FHIR
- FHIR MS will be a document that can be consulted many times
- author in kmehr context: the author that decides that the content is good enough to send the message
- we will recommend that in FHIR we need an "author" that is responsible for the whole of the MS
- FHIR has a lifecycle that currently does not exist
- the FHIR MS will be a bundle
Agenda items for next meeting
- review valuesets
- review logical model for medication scheme (to prepare by José)
Next meeting 7 Feb at 11AM
