Pharm Tech Minutes 2011.04.12-13: Difference between revisions

From IHE Wiki
Jump to navigation Jump to search
← Older edit
Simon.letellier (talk | contribs)
editor
2,522 edits
Simon.letellier (talk | contribs)
editor
2,522 edits
 
(38 intermediate revisions by the same user not shown)
Line 34: Line 34:


== Greetings ==
== Greetings ==
This minutes are available in '''[ftp://ftp.ihe.net/Pharmacy/Meetings/Meeting1314April2011/IHE-Pharmacy-Group-F2F-12-13-April-2011-Pisa.pdf pdf format - 17 pages]'''.


=='''Presentation:''' XDW Profile==
=='''Presentation:''' XDW Profile==
By Luca Zalunardo and Arianna Cocchiglia.
[ftp://ftp.ihe.net/Pharmacy/Meetings/Meeting1314April2011/XDW_slidesPisa_pharmacy.pdf Presentation PDF format - 11 slides] by Luca Zalunardo and Arianna Cocchiglia.


=='''Report''' of vendors testing HMW profile==
==Report of vendors testing HMW profile==


Representatives of vendors:
Representatives of vendors:
* Solinfo (Italy)
::* Solinfo (Italy)
* Glintt  (Portugal)
::* Glintt  (Portugal)
* Dedalus (Italy)
::* Dedalus (Italy)


Report their feedback to the Pharmacy profiles and the Connectathon.
Report their feedback to the Pharmacy profiles and the Connectathon.


== '''Presentation''': Status of ePrescription/eDispensation in epSOS ==
== '''Presentation''': Status of ePrescription/eDispensation in epSOS ==
The presentation by Marcello Melgara was based on epSOS ePrescription : functional service requirements   
:The presentation by Marcello Melgara was based on [http://www.epsos.eu/fileadmin/content/pdf/deliverables/D3.1.2_Final_Definition_of_Functional_Service_Requirements_ePrescription.pdf epSOS ePrescription : functional service requirements (pdf document)].
 
=='''Roadmap''': Discussing of Work-packages for 2011==
 
===COMMON===
 
* '''Clinical trials'''
::Linkage “Pharmacy” with current profiles dealing with clinical trial.
::'''Discussion''': Not most important, but in some hospitals a big time-consuming issue.
::'''Decision''': Start with a whitepaper what is needed for TC. Not this year.
 
* '''Handling instructions'''
e.g. Cold chain, ...
::'''Discussion''': If it’s an attribute of the product, of the supply chain or of part of Handling and Administration instructions.
::'''Question''': Shall Instructions be in prescriptions only or also in other documents. IHE must clarify the Technical Framework that this has been addressed.
   
::'''Decision''': Low priority but small task - This period if possible
 
* '''Linkage to “Vaccines/Immunizations”'''
::'''Decision''': Important, but not this year!
 
===CMPD / HMW===
 
* '''Workflow'''
 
::Incorporate XDW Profile for missing workflow and status management -> Dependency issue with XDW roadmap.
   
   
http://www.epsos.eu/fileadmin/content/pdf/deliverables/D3.1.2_Final_Definition_of_Functional_Service_Requirements_ePrescription.pdf
::'''Discussion''': Very important especially for CMPD but a lot of work. Shall a whitepaper be written for the use of XDW in PHARM.
::'''Decision''': Urgent joint work XDW/PHARM beginning with a Whitepaper for use-cases. Confirmed by both WGs.


===Roadmap: Discussing of Work-packages for 2011====
* '''Query current medication / Medication reconciliation'''


6.1 COMMON
::'''Discussion''': It’s important how this is presented (text!). We can just deliver, what we “know” not what he actually “takes”. Be careful in phrasing this! Users have to be clear what they get and not get. HL7 introduced a “Medication statement”. Patient tells which medication he takes.
::'''Decision''': Most important use-case, should be in this period


6.1.1 Clinical trials
* '''Substitution Handling: Exact Definition'''
Linkage “Pharmacy” with current profiles dealing with clinical trial.
Discussion: Not most important, but in some hospitals a big time-consuming issue.
Decision: Start with a whitepaper what is needed for TC. Not this year.


6.1.2 Handling instructions
::Exact task: Work out and exactly clarify what a “Substitution is”.  
e.g. Cold chain, ...
Discussion: If it’s an attribute of the product, of the supply chain or of part of Handling and Administration instructions.
::Create samples.
Question: Shall Instructions be in prescriptions only or also in other documents. IHE must clarify the Technical Framework that this has been addressed.
Decision: Low priority but small task - This period if possible
6.1.3 Linkage to “Vaccines/Immunizations”
Decision: Important, but not this year!


6.2 CMPD / HMW
::'''Decision''': In this period
6.2.1 Workflow
Incorporate XDW Profile for missing workflow and status management -> Dependency issue with XDW roadmap.
Discussion: Very important especially for CMPD but a lot of work. Shall a whitepaper be written for the use of XDW in PHARM.
Decision: Urgent joint work XDW/PHARM beginning with a Whitepaper for use-cases. Confirmed by both WGs.


6.2.2 Query current medication
*'''Use-case: Community - Hospital'''
Medication reconciliation.
Discussion: It’s important how this is presented (text!). We can just deliver, what we “know” not what he actually “takes”. Be careful in phrasing this! Users have to be clear what they get and not get. HL7 introduced a “Medication statement”. Patient tells which medication he takes.
Decision: Most important use-case, should be in this period


6.2.3 Substitution Handling: Exact Definition
::Connection to ''Query current medication'': At point of admission it shall be known the medication status
Exact task: Work out and exactly clarify what a “Substitution is”. Create samples.
::Several use-cases.  
Decision: In this period
::Is the current specification ready for covering these?


6.2.4 Use-case: Community - Hospital
::'''Decision''': Creation of use-cases this period – then further decision
Connection to Query current medication: At point of admission it shall be known the medication status
Several use-cases. Is the current specification ready for covering these?
Decision: Creation of use-cases this period – then further decision


6.3 CMPD only
===CMPD only===


6.3.1 Exceptional cases
* Exceptional cases
e.g.: Prescription is not validated by pharmacist, Medication cannot be dispensed, etc.
e.g.: Prescription is not validated by pharmacist, Medication cannot be dispensed, etc.
Results in writing specific use-cases and check if the current specification can handle them.
Results in writing specific use-cases and check if the current specification can handle them.
Decision: Some use-cases shall be created – then further decision
::'''Decision''': Some use-cases shall be created – then further decision
 
===CONTENT PROFILES===
 
*'''Substitution-Structure'''
 
::There is still the open issue, that substitution handling could be stated different as current, using current HL7 MedicationOrder (PORX_RM010120UV) structures.
 
::'''Open Issue'''
::This element might change. Structure is still in discussion with PCC and HL7 Structured Document group.
 
::Derived from "MedicationOrder" CMET (PORX_RM010120UV).
::http://www.hl7.org/v3ballot/html/domains/uvrx/editable/PORX_RM010120UV.htm
 
::'''Decision''': Sidetrack, we have a solution. No pressure on it. Nice to have.
 
*'''Non-medication products'''
 
::Same discussion in HL7.
::'''Discussion''': There is currently no harmonization in non-medication products (braces, bandages etc.) medical devices on international level. Such products don’t have a number, etc.
::'''Decision''': JB will check the optionalities to check, if current specification could carry such items. Then further decision.
 
*'''Preparations / Cytotoxics'''
 
::'''Problem''': Can be a mixture of everything (Products, Substances, other things). Problem is complex.
 
::'''Decision''': This period.
 
* '''Cancelling of already dispensed items which don’t have a prescription'''
 
::'''Decision''': This period.
 
* '''How to deal with dispenses on behalf of pre which are not here yet'''


6.4 CONTENT PROFILES
::'''Decision''': This period.
::Jose volunteers.


6.4.1 Substitution-Structure
===HMW only===
There is still the open issue, that substitution handling could be stated different as current, using current HL7 MedicationOrder (PORX_RM010120UV) structures.


Open Issue
* '''Message to be sent to many actors?'''
This element might change. Structure is still in discussion with PCC and HL7 Structured Document group.


Derived from "MedicationOrder" CMET (PORX_RM010120UV).
::'''Decision''': Not this year.
http://www.hl7.org/v3ballot/html/domains/uvrx/editable/PORX_RM010120UV.htm


Decision: Sidetrack, we have a solution. No pressure on it. Nice to have.
* '''HL7v2 question: Insufficient fields for Order, Order session, Prescription ...'''


6.4.2 Non-medication products
::'''Decision''': Will be taken offline. Further discussed by Tom and Jose
Same discussion in HL7.
Discussion: There is currently no harmonization in non-medication products (braces, bandages etc.) medical devices on international level. Such products don’t have a number, etc.
Decision: JB will check the optionalities to check, if current specification could carry such items. Then further decision.  


6.4.3 Preparations / Cytotoxics
* '''Administration report to dispenser – Purpose?'''
Problem: Can be a mixture of everything (Products, Substances, other things). Problem is complex.
Decision: This period.


6.4.4 Cancelling of already dispensed items which don’t have a prescription
::'''Decision''': High priority
Decision: This period.


6.4.5 How to deal with dispenses on behalf of pre which are not here yet
* '''Prescription protocols'''
Decision: This period.
Jose volunteers.


6.5 HMW only
::'''Decision''': Not much work, Jose volunteers


6.5.1 Message to be sent to many actors?
* '''Cytotoxics'''
Decision: Not this year.


6.5.2 HL7v2 question: Insufficient fields for Order, Order session, Prescription ...
::'''Discussion''': Impact on optionality, needs documenting.
Decision: Will be taken offline. Further discussed by Tom and Jose


6.5.3 Administration report to dispenser – Purpose?
::'''Decision''': Should be this year.
Decision: High priority


6.5.4 Prescription protocols
* '''Administration of perfusion'''
Decision: Not much work, Jose volunteers


6.5.5 Cytotoxics
::'''Decision''': This year.
Discussion: Impact on optionality, needs documenting.
Decision: Should be this year.


6.5.6 Administration of perfusion
* '''Multiple systems in same hospital'''
Decision: This year.


6.5.7 Multiple systems in same hospital
::e.g. Chemotherapy and normal pharmacy system
e.g. Chemotherapy and normal pharmacy system
Decision: Draft solution this year, to see if good for inclusion


6.5.8 Documents in hospital system?
::'''Decision''': Draft solution this year, to see if good for inclusion
Discussion: Too much work. This would result in a NEW profile.
Decision: Not this year. Currently no volunteers.


6.5.9 Update to HL7v3 messages
* '''Documents in hospital system?'''
Discussion: Would probably result in a new profile.
Decision: Not this year.


6.5.10 Supply chain
::'''Discussion''': Too much work. This would result in a NEW profile.
Discussion: Big interest of vendors. It’s not about how to solve the supply chain, but how to “inform” the supply chain. A whitepaper should be written. Vendors should be involved. Is a cross-domain topic, possible liaison with ITI?
Decision: Whitepaper started this year.


6.5.11 Referentials / Formularies
::'''Decision''': Not this year. Currently no volunteers.
Discussion: It’s an implicit prerequisite in IHE to have common codelists and catalogs. Out of scope? Profiles should not require specific codesets, should be up to national extensions/specifications.
Decision: This assumption is sufficient.


6.5.12 Exceptional cases
* '''Update to HL7v3 messages'''
Discussion: e.g.: Prescription is not validated by pharmacist, Medication cannot be dispensed, etc.
 
Results in writing specific use-cases and check if the current specification can handle them.
::'''Discussion''': Would probably result in a new profile.
Decision: Some use-cases shall be created – then further decision


::'''Decision''': Not this year.


== Prioritizing ==
* '''Supply chain'''


::'''Discussion''': Big interest of vendors. It’s not about how to solve the supply chain, but how to “inform” the supply chain. A whitepaper should be written. Vendors should be involved. Is a cross-domain topic, possible liaison with ITI?


Changes in the WG task list
::'''Decision''': Whitepaper started this year.


* '''Referentials / Formularies'''


::'''Discussion''': It’s an implicit prerequisite in IHE to have common codelists and catalogs. Out of scope? Profiles should not require specific codesets, should be up to national extensions/specifications.


== Presentation “FamaSafe” ==
::'''Decision''': This assumption is sufficient.


Presentation by Lapo Bertini (Dedalus, Italy) about their implementation of Pharmacy hospital profiles.
* '''Exceptional cases'''
::'''Discussion''': e.g.: Prescription is not validated by pharmacist, Medication cannot be dispensed, etc.
::Results in writing specific use-cases and check if the current specification can handle them.
::'''Decision''': Some use-cases shall be created – then further decision


== Prioritizing ==
   
   
:Changes in the [ftp://ftp.ihe.net/Pharmacy/yr2_2010-2011/Planning%20Committee/IHE%20Pharmacy%20prios%202010-2011-summary.xls work plan 2011-2012 (xls file)]


=== Next F2F Meetings ===
== '''Presentation''': “FamaSafe” ==


1. Paris/Vienna
:[ftp://ftp.ihe.net/Pharmacy/Meetings/Meeting1314April2011/WIP-FamaSafe-IHE-Pisa-2011-LB.pdf Presentation in PDF format - 10 slides] by Lapo Bertini (Dedalus, Italy) about their implementation of Pharmacy hospital profiles.
• Date: 28.-29.06.2011
2. Vienna/Paris
• Date: 04.-05.10.2011


Decision about Paris/Vienna switch triggered by Jacqueline depending on availability of guests.
==Planning next meetings ==
Report of Jacqueline about this until next week -> then decision.
 
=== F2F meetings===
 
* Paris/Vienna
::Date: 28.-29.06.2011
* Vienna/Paris
::Date: 04.-05.10.2011
::Decision about Paris/Vienna switch triggered by Jacqueline depending on availability of guests.
::Report of Jacqueline about this until next week -> then decision.


9.1 General compromise on future meeting places
===General compromise on future meeting places===
• 3 F2F meetings per year:
*3 F2F meetings per year:
o 1 at the CAT
**1 at the CAT
o 1 at Paris or Brussels
**1 at Paris or Brussels
o 1 at  an “other” location
**1 at  an “other” location


9.2 List of candidates for future F2F on “other” location:
===List of candidates for future F2F on “other” location===
1. Porto
#Porto
2. Amsterdam/Den Haag
#Amsterdam/Den Haag
3. Treviso/Venice
#Treviso/Venice


10 Next TCons
===Next TCons===
Date: 24.05.2011 (moved from 19.05.2011),
:Date: 24.05.2011 (moved from 19.05.2011),
Time: 12:00-13:30 Brussels time
:Time: 12:00-13:30 Brussels time


10.1 General decisions about TCons
===General decisions about TCons===
Duration will be extended from 1 h to 1,5 h
:Duration will be extended from 1 h to 1,5 h


==Miscellaneous==
=== Liaison with epSOS===
=== Liaison with epSOS===
Michiel Sprenger is involved in epSOS WP 2.2 “Strategy and Policy”, deals with roadmap views, etc.  
:Michiel Sprenger is involved in epSOS WP 2.2 “Strategy and Policy”, deals with roadmap views, etc.  
He could be the link from IHE Pharmacy to epSOS.
Decision: If this is an official liaison or informal will be checked by Robert Breas.
:He could be the link from IHE Pharmacy to epSOS.
:'''Decision''': If this is an official liaison or informal will be checked by Robert Breas.


=== Meeting requested by Nick Brown===
=== Meeting requested by Nick Brown===
Jacqueline Surugue received an Email of Nick Brown (IHE UK).  
 
He would like to meet Pharmacy group at CAT Pisa.  
:Jacqueline Surugue received an email of Nick Brown (IHE UK).  
Jürgen will do the meeting in Thursday.
:He would like to meet Pharmacy group at CAT Pisa.  
:Jürgen will do the meeting in Thursday.

Latest revision as of 11:03, 4 May 2011

Attendees

Tuesday, April 12.

  • Ana Estelrich, Phast
  • Arianna Cocchiglia, Arsenal.it
  • Jacqueline Surugue, EAHP
  • Jose Costa Teixeira, Agfa Healthcare
  • Jürgen Brandstätter, CodeWerk
  • Leonidas Tzimis, EAHP
  • Luca Zalunardo, Arsenal.it
  • Marc Robberecht, Agfa Healthcare
  • Marco Demarmels Lake Griffin LLC
  • Orlando Rodrigues, Glintt
  • Robert Breas, NICTIZ
  • Robert Horn, Agfa Healthcare
  • Simon Letellier, EAHP
  • Tom de Jong, HL7 Pharmacy
  • Viktor Hafner, Austrian Pharmacists Association

Wednesday, April 13.

  • Ana Estelrich, Phast
  • Arianna Cocchiglia, Arsenal.it
  • Geert Claeys, Agfa Healthcare
  • Jacqueline Surugue, EAHP
  • Jose Costa Teixeira, Agfa Healthcare
  • Jürgen Brandstätter, CodeWerk
  • Leonidas Tzimis, EAHP
  • Luca Zalunardo, Arsenal.it
  • Marc Robberecht, Agfa Healthcare
  • Marco Demarmels Lake Griffin LLC
  • Orlando Rodrigues, Glintt
  • Robert Breas, NICTIZ
  • Simon Letellier, EAHP
  • Viktor Hafner, Austrian Pharmacists Association

Greetings

This minutes are available in pdf format - 17 pages.

Presentation: XDW Profile

Presentation PDF format - 11 slides by Luca Zalunardo and Arianna Cocchiglia.

Report of vendors testing HMW profile

Representatives of vendors:

  • Solinfo (Italy)
  • Glintt (Portugal)
  • Dedalus (Italy)

Report their feedback to the Pharmacy profiles and the Connectathon.

Presentation: Status of ePrescription/eDispensation in epSOS

The presentation by Marcello Melgara was based on epSOS ePrescription : functional service requirements (pdf document).

Roadmap: Discussing of Work-packages for 2011

COMMON

  • Clinical trials
Linkage “Pharmacy” with current profiles dealing with clinical trial.
Discussion: Not most important, but in some hospitals a big time-consuming issue.
Decision: Start with a whitepaper what is needed for TC. Not this year.
  • Handling instructions

e.g. Cold chain, ...

Discussion: If it’s an attribute of the product, of the supply chain or of part of Handling and Administration instructions.
Question: Shall Instructions be in prescriptions only or also in other documents. IHE must clarify the Technical Framework that this has been addressed.
Decision: Low priority but small task - This period if possible
  • Linkage to “Vaccines/Immunizations”
Decision: Important, but not this year!

CMPD / HMW

  • Workflow
Incorporate XDW Profile for missing workflow and status management -> Dependency issue with XDW roadmap.
Discussion: Very important especially for CMPD but a lot of work. Shall a whitepaper be written for the use of XDW in PHARM.
Decision: Urgent joint work XDW/PHARM beginning with a Whitepaper for use-cases. Confirmed by both WGs.
  • Query current medication / Medication reconciliation
Discussion: It’s important how this is presented (text!). We can just deliver, what we “know” not what he actually “takes”. Be careful in phrasing this! Users have to be clear what they get and not get. HL7 introduced a “Medication statement”. Patient tells which medication he takes.
Decision: Most important use-case, should be in this period
  • Substitution Handling: Exact Definition
Exact task: Work out and exactly clarify what a “Substitution is”.
Create samples.
Decision: In this period
  • Use-case: Community - Hospital
Connection to Query current medication: At point of admission it shall be known the medication status
Several use-cases.
Is the current specification ready for covering these?
Decision: Creation of use-cases this period – then further decision

CMPD only

  • Exceptional cases

e.g.: Prescription is not validated by pharmacist, Medication cannot be dispensed, etc. Results in writing specific use-cases and check if the current specification can handle them.

Decision: Some use-cases shall be created – then further decision

CONTENT PROFILES

  • Substitution-Structure
There is still the open issue, that substitution handling could be stated different as current, using current HL7 MedicationOrder (PORX_RM010120UV) structures.
Open Issue
This element might change. Structure is still in discussion with PCC and HL7 Structured Document group.
Derived from "MedicationOrder" CMET (PORX_RM010120UV).
http://www.hl7.org/v3ballot/html/domains/uvrx/editable/PORX_RM010120UV.htm
Decision: Sidetrack, we have a solution. No pressure on it. Nice to have.
  • Non-medication products
Same discussion in HL7.
Discussion: There is currently no harmonization in non-medication products (braces, bandages etc.) medical devices on international level. Such products don’t have a number, etc.
Decision: JB will check the optionalities to check, if current specification could carry such items. Then further decision.
  • Preparations / Cytotoxics
Problem: Can be a mixture of everything (Products, Substances, other things). Problem is complex.
Decision: This period.
  • Cancelling of already dispensed items which don’t have a prescription
Decision: This period.
  • How to deal with dispenses on behalf of pre which are not here yet
Decision: This period.
Jose volunteers.

HMW only

  • Message to be sent to many actors?
Decision: Not this year.
  • HL7v2 question: Insufficient fields for Order, Order session, Prescription ...
Decision: Will be taken offline. Further discussed by Tom and Jose
  • Administration report to dispenser – Purpose?
Decision: High priority
  • Prescription protocols
Decision: Not much work, Jose volunteers
  • Cytotoxics
Discussion: Impact on optionality, needs documenting.
Decision: Should be this year.
  • Administration of perfusion
Decision: This year.
  • Multiple systems in same hospital
e.g. Chemotherapy and normal pharmacy system
Decision: Draft solution this year, to see if good for inclusion
  • Documents in hospital system?
Discussion: Too much work. This would result in a NEW profile.
Decision: Not this year. Currently no volunteers.
  • Update to HL7v3 messages
Discussion: Would probably result in a new profile.
Decision: Not this year.
  • Supply chain
Discussion: Big interest of vendors. It’s not about how to solve the supply chain, but how to “inform” the supply chain. A whitepaper should be written. Vendors should be involved. Is a cross-domain topic, possible liaison with ITI?
Decision: Whitepaper started this year.
  • Referentials / Formularies
Discussion: It’s an implicit prerequisite in IHE to have common codelists and catalogs. Out of scope? Profiles should not require specific codesets, should be up to national extensions/specifications.
Decision: This assumption is sufficient.
  • Exceptional cases
Discussion: e.g.: Prescription is not validated by pharmacist, Medication cannot be dispensed, etc.
Results in writing specific use-cases and check if the current specification can handle them.
Decision: Some use-cases shall be created – then further decision

Prioritizing

Changes in the work plan 2011-2012 (xls file)

Presentation: “FamaSafe”

Presentation in PDF format - 10 slides by Lapo Bertini (Dedalus, Italy) about their implementation of Pharmacy hospital profiles.

Planning next meetings

F2F meetings

  • Paris/Vienna
Date: 28.-29.06.2011
  • Vienna/Paris
Date: 04.-05.10.2011
Decision about Paris/Vienna switch triggered by Jacqueline depending on availability of guests.
Report of Jacqueline about this until next week -> then decision.

General compromise on future meeting places

  • 3 F2F meetings per year:
    • 1 at the CAT
    • 1 at Paris or Brussels
    • 1 at an “other” location

List of candidates for future F2F on “other” location

  1. Porto
  2. Amsterdam/Den Haag
  3. Treviso/Venice

Next TCons

Date: 24.05.2011 (moved from 19.05.2011),
Time: 12:00-13:30 Brussels time

General decisions about TCons

Duration will be extended from 1 h to 1,5 h

Miscellaneous

Liaison with epSOS

Michiel Sprenger is involved in epSOS WP 2.2 “Strategy and Policy”, deals with roadmap views, etc.
He could be the link from IHE Pharmacy to epSOS.
Decision: If this is an official liaison or informal will be checked by Robert Breas.

Meeting requested by Nick Brown

Jacqueline Surugue received an email of Nick Brown (IHE UK).
He would like to meet Pharmacy group at CAT Pisa.
Jürgen will do the meeting in Thursday.
Retrieved from "http://wiki.ihe.net/index.php?title=Pharm_Tech_Minutes_2011.04.12-13&oldid=50683"