Difference between revisions of "Minutes - Medication WG 2020-04-14"

From Health Level 7 Belgium Wiki
 
(2 intermediate revisions by one other user not shown)
Line 22: Line 22:
 
* '''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
 
::* 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
+
::* Data is kept for 12 months: determined by Belgian privacy commission, 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  
 
::::Local pharmacy record has to be kept for at least 10 years, destroyed in 30 years  
Line 32: Line 32:
 
::::::Could by replaced by GTIN in the future ? Or use a 2nd number ? Could be interesting discussion point for this WG
 
::::::Could by replaced by GTIN in the future ? Or use a 2nd number ? Could be interesting discussion point for this WG
 
::::*ISNZ: valid, valid format
 
::::*ISNZ: valid, valid format
::::*XML is validated, attributes are ok
+
 
 
::* What are the medata:
 
::* What are the medata:
 
::::* key and value
 
::::* key and value
Line 38: Line 38:
 
::::* new keys can be added quite easily in the future without having to change the model
 
::::* new keys can be added quite easily in the future without having to change the model
 
::*A message can have multiple dispensations
 
::*A message can have multiple dispensations
::::* within each session multiple products
+
:::* within each session multiple reports
 
::::* patient ID will be the same and appear multiple times
 
::::* patient ID will be the same and appear multiple times
 
::::* no central reconciliation is done therefore the patient ID comes back multiple times
 
::::* no central reconciliation is done therefore the patient ID comes back multiple times
::::* no interlink between products if they determine each other’s posology
+
::::* no interlink between products if they affect each other’s posology
  
* '''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 ?
+
::* A "data quality" / Reliability factor is available in the file, for now it always reports 50%.
 +
 
 +
* '''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
 
::* 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
+
::* Proposal to start putting things in the right place, keeping our model up to date, checking which data and metadata we need/want
 
::* Looking at examples (FHIR and other) and check if we have them in our model
 
::* 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
 
::* Jan prefers to start working with examples to see whether they are mapped on the model or if they are missing
 +
::* Have a look at the Dutch ZIB's (bouwstenen): medicatieverstrekking building block; clinical & logistical side
 +
 
*  '''Agenda points for next call'''
 
*  '''Agenda points for next call'''
 
::*Have a look at Jan’s examples
 
::*Have a look at Jan’s examples
Line 53: Line 57:
 
::::We already have a Google drive [https://drive.google.com/open?id=1hVBJB79XIyS7NiDlZj2odZgXuCegZXdv HL7 BE Medication]
 
::::We already have a Google drive [https://drive.google.com/open?id=1hVBJB79XIyS7NiDlZj2odZgXuCegZXdv HL7 BE Medication]
 
::::Karlien will make everyone editor & send the link
 
::::Karlien will make everyone editor & send the link
::* Have a look at the Dutch ZIB's (bouwstenen): medicatieverstrekking building block; clinical & logistical side
+
::* Goal is to have a logical model for medication dispense (and a profile) that can be published pretty soon

Latest revision as of 11:50, 25 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
  • Presentation of Farmaflux by Tom: 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 privacy commission, 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
Only medication is accepted (registration file – CNK ID tells if it is medication)
Pharmacy never gives INN, translates this into product
Could by replaced by GTIN in the future ? Or use a 2nd number ? Could be interesting discussion point for this WG
  • ISNZ: valid, valid format
  • What are the medata:
  • key and value
  • not used a lot as for the moment
  • new keys can be added quite easily in the future without having to change the model
  • A message can have multiple dispensations
  • within each session multiple reports
  • patient ID will be the same and appear multiple times
  • no central reconciliation is done therefore the patient ID comes back multiple times
  • no interlink between products if they affect each other’s posology
  • A "data quality" / Reliability factor is available in the file, for now it always reports 50%.
  • 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 up to date, checking which data and 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
  • Have a look at the Dutch ZIB's (bouwstenen): medicatieverstrekking building block; clinical & logistical side
  • 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 (and a profile) that can be published pretty soon