Difference between revisions of "Minutes - Medication WG 2020-04-14"
KarlienErauw (talk | contribs) |
KarlienErauw (talk | contribs) |
||
Line 19: | Line 19: | ||
== Minutes == | == Minutes == | ||
* Review of previous meeting minutes : postponed to next meeting - please send in your comments to Karlien | * Review of previous meeting minutes : postponed to next meeting - please send in your comments to Karlien | ||
− | * Tom's presentation of Farmaflux | + | * Tom's presentation of Farmaflux: see [https://drive.google.com/open?id=1RrCcOewZ3xSIEuh6kvmFhR1Ijq69McA9 here] |
* Q&A on Toms presentation | * Q&A on Toms presentation | ||
− | + | - Reporting on voluntary basis : consequence on integrity of record – patient record is per definition incomplete – privacy is OK | |
− | + | - Data is kept for 12 months: determined by Belgian privacycommission, file has been submitted | |
− | - For clinical assessment a longer history can be of value- 12 months could be changed after consultation of privacycommission – 12 years : other purpose - value for doctors, not for pharmacists | + | - For clinical assessment a longer history can be of value- 12 months could be changed after consultation of privacycommission – 12 years : other purpose - value for doctors, not for pharmacists ; Local pharmacy record has to be kept for at least 10 years, destroyed in 30 years ; Farmaflux is cleaning up after 12 months, archived out of database |
− | + | - Quality control: checks that are done in Farmaflux are: | |
− | + | - CNK ID : valid, valid format | |
− | - Quality control: | + | o Only medication is accepted (registration file – CNK ID tells if it is medication) |
− | + | o Pharmacy never gives INN, translates this into product | |
+ | o Could by replaced by GTIN in the future ? Or use a 2nd number ? Could be interesting discussion pt for this WG | ||
+ | - ISNZ: valid, valid format | ||
+ | - XML is validated, attributes are ok | ||
− | + | * Proposals on next action points: | |
− | |||
Should we work on GoogleDocs to work on attributes in between our next meeting in order to work on our information model ? Suggestions for the next step ? | Should we work on GoogleDocs to work on attributes in between our next meeting in order to work on our information model ? Suggestions for the next step ? | ||
* Jan prepared Json file for model on medication dispense, would like to start translation, would like to check model with provided examples | * Jan prepared Json file for model on medication dispense, would like to start translation, would like to check model with provided examples |
Revision as of 15:58, 24 April 2020
Attendees
- Jan Lenie
- Annemieke Vergauwe
- Will Van Norel
- Richard Francken
- Tom Henkens
- Jens Penny
- José Costa Teixeira
- Karlien Erauw
- Robin Bosman
Agenda
- Review previous meeting minutes
- Demo of Tom on Farmaflux
- Look at collected information
- Determine first action points
Minutes
- Review of previous meeting minutes : postponed to next meeting - please send in your comments to Karlien
- Tom's presentation of Farmaflux: see here
- Q&A on Toms presentation
- Reporting on voluntary basis : consequence on integrity of record – patient record is per definition incomplete – privacy is OK - Data is kept for 12 months: determined by Belgian privacycommission, file has been submitted - For clinical assessment a longer history can be of value- 12 months could be changed after consultation of privacycommission – 12 years : other purpose - value for doctors, not for pharmacists ; Local pharmacy record has to be kept for at least 10 years, destroyed in 30 years ; Farmaflux is cleaning up after 12 months, archived out of database - Quality control: checks that are done in Farmaflux are:
- CNK ID : valid, valid format
o Only medication is accepted (registration file – CNK ID tells if it is medication) o Pharmacy never gives INN, translates this into product o Could by replaced by GTIN in the future ? Or use a 2nd number ? Could be interesting discussion pt for this WG
- ISNZ: valid, valid format - XML is validated, attributes are ok
- Proposals on next action points:
Should we work on GoogleDocs to work on attributes in between our next meeting in order to work on our information model ? Suggestions for the next step ?
- Jan prepared Json file for model on medication dispense, would like to start translation, would like to check model with provided examples
- Proposal to start putting things in the right place, keeping our model alive, checking which metadata we need/want
- Looking at examples (FHIR and other) and check if we have them in our model
- Jan prefers to start working with examples to see whether they are mapped on the model or if they are missing
- Agenda points for next call
- Have a look at Jan’s examples
- Jose will share a draft document with necessary fields to work on
We already have a Google drive HL7 BE Medication, Karlien will make everyone editor & send the link
- Goal is to have a logical model for medication dispense that can be published pretty soon
- Have a look at the Dutch ZIB's (bouwstenen): medicatieverstrekking building block; clinical & logistical side