Difference between revisions of "Pharm Tech Minutes 2012.02.03"

From IHE Wiki
Jump to navigation Jump to search
 
(12 intermediate revisions by 2 users not shown)
Line 2: Line 2:
 
* Brandstätter, Jürgen (CodeWerk Software Services and Development GmbH, co-chair IHE)
 
* Brandstätter, Jürgen (CodeWerk Software Services and Development GmbH, co-chair IHE)
 
* Cocchiglia, Arianna (Arsenal.IT)
 
* Cocchiglia, Arianna (Arsenal.IT)
 +
* de Jong, Tom (Nova Pro)
 
* Demarmels, Marco (Lake Griffin, LLC)
 
* Demarmels, Marco (Lake Griffin, LLC)
 
* Géraud, Thierry (CareFusion)
 
* Géraud, Thierry (CareFusion)
 
* Letellier, Simon (EAHP)
 
* Letellier, Simon (EAHP)
 +
* Parisot, Charles (GE Healthcare)
 
* Robberecht, Marc (Agfa Healthcare)
 
* Robberecht, Marc (Agfa Healthcare)
 
* Surugue, Jacqueline (EAHP)
 
* Surugue, Jacqueline (EAHP)
 
* Zalunardo, Luca (Arsenal.IT)
 
* Zalunardo, Luca (Arsenal.IT)
* Parisot, Charles (GE Healthcare)
+
* Peytchev, Vassil (Epic)
* De Jong, Tom (Novapro)
 
  
 
== Greeting ==
 
== Greeting ==
 
*
 
  
 
==9:15-10:00 CMPD Exceptional cases ==
 
==9:15-10:00 CMPD Exceptional cases ==
  
*This work item will be combined with work item "Refinement CMPD workflow". New name: "CMPD exceptional cases and concept of "Therapeutic prescription" (the current prescription is ment to be a "logistic prescription")
+
*This work item will be combined with work item "Refinement CMPD workflow". New name: "CMPD exceptional cases and concept of Therapeutic prescription" (the current prescription is ment to be a "logistic prescription")
 
:*Exceptional cases shall be collected for scenario 1 + 2
 
:*Exceptional cases shall be collected for scenario 1 + 2
 
*Dedicated TCons to this topic. Schedule will be proposed by Jürgen
 
*Dedicated TCons to this topic. Schedule will be proposed by Jürgen
Line 33: Line 32:
  
  
*
+
*Problem 1: Maintaining XDW Document cross-domain
*
+
:*Publishing documents in foreign domains should be solved by ITI.
*
+
*Problem 2: Does proxying the managment of XDW make sense?
*
+
:*Evaluate the whole usage of XDW at client-side in both scenarios and weight the amount of work which could be proxied.
*
+
:*The extensions by work item "CMPD exceptional cases and concept of Therapeutic prescription" shall be considered
 +
*Decision
 +
:*First work item "CMPD exceptional cases and concept of Therapeutic prescription" will be worked out
 +
:*Then this work item will be taken up again
  
 +
==12:30-13:30 Use-case: Community – Hospital==
 +
* Link: ftp://ftp.ihe.net/Pharmacy/yr2_2010-2011/Technical%20Committee/WhitePapers/Hospital&CommunityWP/Use%20case%20for%20Hospital%20and%20Community%20Pharmacy%20v1.3.doc
 +
*Objective of the whitepaper should be to identify, if there is information missing or inconsistent in the Hospital or Community Pharmacy domain, which avoids smooth transition of information between them
 +
*The use-cases should be splitted into short and distict pieces
 +
:*Each of these should be evaluated if the border-system (attached to both domains) has enough information to perform the transition of information either way
 +
*The longer versions shall be preserved for the detailed prescription
 +
*Use-case "Hospital Dispense for inpatients and outpatients" combines too many things, seems inconsistent
 +
*Jacqueline will inform Orlando about this
  
  
 +
==13:00-13:15 Monitoring and Syncing with PCD: (Perfusion administration)==
  
* '''12:00-12:30 --- Lunch ---'''
+
*Work item is accepted as a IHE Pharmacy work item.
 +
*Main contact: Jürgen at first (change possible if it makes sense)
 +
*Interested people
 +
:*Vassil, Marc, Jacqueline, Thierry (+ others from CareFusion)
 +
:*Chris Courville (EPIC and part of PCD group)
  
==12:30-13:30 Use-case: Community – Hospital==
 
  
*
+
==13:15-13:30 Joint meeting with HL7 Pharmacy==
*
+
*HL7 Pharmacy schedule
*
+
:*Next out of cycle meeting: March 6.-7., Oslo
*
+
:*WG meeting in May 13.-18., Vancouver
 +
:*WG meeting in Sep 9.-14., Baltimore
 +
*Tom checks if IHE F2F at 2012.06.19-20 in Brussels/DenHaag is possible for HL7
 +
*Otherwise date it for autumn
 +
:*IHE schedule
 +
:*Good date: End of October (would be the a technical meeting at IHE)
 +
::*either Oct 23/24 or 30/31 2012
 +
*Vassil/Charles will send ITI/PCC/QRPH schedule when available
  
==13:30-14:45 Medication Documentation ==
+
==13:30-15:15 Medication Documentation ==
  
*
+
*News
*
+
:*Jose is not in the list of authors anymore
*
+
:*New lead authors: Marc, Julie
*
+
*Abstract
 +
:*Medication profile = Medical History + Clinical information
 +
:*Solving divided into two parts:
 +
::*Additional to "Bottom-Up" approach a Top-Down approach is added because of HL7 EHR WG, which deals with that topic by a "requirements"-driven approach, HL7 and IHE Pharmacy align to that
 +
:*Collecting guidelines of different countries
 +
::*Australia, Canada, Netherlands (shall be set up there)
 +
*Involved work groups:
 +
:*IHE Pharmacy
 +
:*HL7 Pharmacy
 +
:*HL7 EHR Functional group
 +
:*IHE PCC
  
 +
*Risks and questions
 +
:*Overlap between "Medication profile" and "Patient summary"
 +
::*Don't re-invent the wheel or invent it twice in parallel
 +
:*Size of a Medication profile
 +
:*What is different between the MP and the Med-Recon of PCC
 +
:*Word "profile" might cause confusion with "IHE profiles"
  
 +
*Discussion: "What is a Medication profile"
 +
:*The components of a "Medication record" have been discussed
 +
:*Shall be expressed in the "Top-down" chapter of the document
  
 +
*Next steps
 +
:*We need to ensure a togrough understanding of the requirements for information input and output into a Medication profile.
 +
:*For this the first step is to document requirements such as scope statement and goals in terms of clinical decision support and how an EHR functional profile and as a subset of it a Medication profile serves the clinical decision process
 +
::*The primary focus will be on the perspective of a Pharmacist giving a Pharmaceutical Advice
 +
:*The end goal is to assess which information we have and what we miss to ensure that medication related information is available and recorded as needed
 +
:*Dedicated TCons to this topic. Schedule will be proposed by Marc/Tom
  
 +
*Further schedule
 +
:*Whitepaper is unlikely to be finished this season
 +
:*Schedule will be relaxed according to availability of the contributors
  
  
*'''14:45-15:00 --- Break 15min ---'''
 
  
 
==15:00-16:00 Glossary work item ==
 
==15:00-16:00 Glossary work item ==
  
*
+
* Link: https://bit.ly/sdk2u7
*
+
 
*
+
* Current goal restricted to finding a common glossary between IHE Pharmacy and HL7 Pharmacy
*
+
:* Target audience of this glossary: Implementors, Software architects, Consultants, ... (domain experts know definitions anyway)
 +
:* Other sources (ISO TC215 WG6, CEN TC251, WHO, EMEA, ...) are considered to retrieve definitions, but no contribution to these other bodies yet
 +
::* Exception: Definitions in column "Nictiz-definitions" were the starting point of the work (currenlty still in the spreadsheet, will be merged in and removed in the end)
 +
:* Once completed, the result will be handed over too ISO TC215 WG6
 +
:* Note: Definitions of other sources sometimes do not serve the purposes our two groups (e.g. two precice, too complicated, ...)
 +
 
 +
*Review by Pharmacists intended
 +
:*Julie for HL7 Pharmacy
 +
:*Jacqueline for IHE Pharmacy
 +
 
 +
*Special topic "Definition of Prescription"
 +
:*Jacqueline will check the professional definitions
 +
 
 +
*General procedure
 +
:*Step 1: HL7 and IHE fill their columns with its definition
 +
:*Step 2: Agreement between HL7 and IHE per column by the working group
 +
:*Step 3: General agreement by the committees
 +
:*Step 4: If necessary, CPs to affected profiles to align glossaries
 +
:*Step 5: Hand over result to ISO 215
 +
 
 +
*Further schedule
 +
:* Intended to finish until end of season
 +
:* Reason: Time pressure because a common glossary is fundamental for all profile development and cross-domain work to avoid confusion. It should be harmonized and stable as soon as possible.
  
==16:00-16:45 Monitoring and Syncing with PCD: (Perfusion administration)==
 
  
*
 
*
 
*
 
  
 
== 16:45-17:00 Other business==
 
== 16:45-17:00 Other business==
Line 83: Line 149:
 
:* Maybe some involved vendors are thereby anchoraged to step into HMW
 
:* Maybe some involved vendors are thereby anchoraged to step into HMW
  
*
+
* Make CMPD better readable
*
+
:* Profile seem very complex at first sight, this might discourage people from using it
 +
:* Thoughts on better presentation
 +
::* Simplify actor diagram and remove parts which are just necessary in multi-domain
 +
::* Keepp first part of profile just single-domain, add multi-domain capabilities at the very end

Latest revision as of 10:29, 3 February 2012

Attendees

  • Brandstätter, Jürgen (CodeWerk Software Services and Development GmbH, co-chair IHE)
  • Cocchiglia, Arianna (Arsenal.IT)
  • de Jong, Tom (Nova Pro)
  • Demarmels, Marco (Lake Griffin, LLC)
  • Géraud, Thierry (CareFusion)
  • Letellier, Simon (EAHP)
  • Parisot, Charles (GE Healthcare)
  • Robberecht, Marc (Agfa Healthcare)
  • Surugue, Jacqueline (EAHP)
  • Zalunardo, Luca (Arsenal.IT)
  • Peytchev, Vassil (Epic)

Greeting

9:15-10:00 CMPD Exceptional cases

  • This work item will be combined with work item "Refinement CMPD workflow". New name: "CMPD exceptional cases and concept of Therapeutic prescription" (the current prescription is ment to be a "logistic prescription")
  • Exceptional cases shall be collected for scenario 1 + 2
  • Dedicated TCons to this topic. Schedule will be proposed by Jürgen
  • Volunteers:
  • Jürgen, Tom, Marco, Jacqueline, Charles, Marc, Viktor should be
  • HL7 Pharmacy works on the same topic, joint work intended by IHE and HL7
  • Objective: Know what to change in Community Pharmacy profiles at the end of the season
  • Do the changes in next season

10:00-11:00 Refinement CMPD workflows

  • Was combined with work item "CMPD Exceptional cases"

11:00-12:00 CMPD: XDW at CPM

  • Problem 1: Maintaining XDW Document cross-domain
  • Publishing documents in foreign domains should be solved by ITI.
  • Problem 2: Does proxying the managment of XDW make sense?
  • Evaluate the whole usage of XDW at client-side in both scenarios and weight the amount of work which could be proxied.
  • The extensions by work item "CMPD exceptional cases and concept of Therapeutic prescription" shall be considered
  • Decision
  • First work item "CMPD exceptional cases and concept of Therapeutic prescription" will be worked out
  • Then this work item will be taken up again

12:30-13:30 Use-case: Community – Hospital

  • Each of these should be evaluated if the border-system (attached to both domains) has enough information to perform the transition of information either way
  • The longer versions shall be preserved for the detailed prescription
  • Use-case "Hospital Dispense for inpatients and outpatients" combines too many things, seems inconsistent
  • Jacqueline will inform Orlando about this


13:00-13:15 Monitoring and Syncing with PCD: (Perfusion administration)

  • Work item is accepted as a IHE Pharmacy work item.
  • Main contact: Jürgen at first (change possible if it makes sense)
  • Interested people
  • Vassil, Marc, Jacqueline, Thierry (+ others from CareFusion)
  • Chris Courville (EPIC and part of PCD group)


13:15-13:30 Joint meeting with HL7 Pharmacy

  • HL7 Pharmacy schedule
  • Next out of cycle meeting: March 6.-7., Oslo
  • WG meeting in May 13.-18., Vancouver
  • WG meeting in Sep 9.-14., Baltimore
  • Tom checks if IHE F2F at 2012.06.19-20 in Brussels/DenHaag is possible for HL7
  • Otherwise date it for autumn
  • IHE schedule
  • Good date: End of October (would be the a technical meeting at IHE)
  • either Oct 23/24 or 30/31 2012
  • Vassil/Charles will send ITI/PCC/QRPH schedule when available

13:30-15:15 Medication Documentation

  • News
  • Jose is not in the list of authors anymore
  • New lead authors: Marc, Julie
  • Abstract
  • Medication profile = Medical History + Clinical information
  • Solving divided into two parts:
  • Additional to "Bottom-Up" approach a Top-Down approach is added because of HL7 EHR WG, which deals with that topic by a "requirements"-driven approach, HL7 and IHE Pharmacy align to that
  • Collecting guidelines of different countries
  • Australia, Canada, Netherlands (shall be set up there)
  • Involved work groups:
  • IHE Pharmacy
  • HL7 Pharmacy
  • HL7 EHR Functional group
  • IHE PCC
  • Risks and questions
  • Overlap between "Medication profile" and "Patient summary"
  • Don't re-invent the wheel or invent it twice in parallel
  • Size of a Medication profile
  • What is different between the MP and the Med-Recon of PCC
  • Word "profile" might cause confusion with "IHE profiles"
  • Discussion: "What is a Medication profile"
  • The components of a "Medication record" have been discussed
  • Shall be expressed in the "Top-down" chapter of the document
  • Next steps
  • We need to ensure a togrough understanding of the requirements for information input and output into a Medication profile.
  • For this the first step is to document requirements such as scope statement and goals in terms of clinical decision support and how an EHR functional profile and as a subset of it a Medication profile serves the clinical decision process
  • The primary focus will be on the perspective of a Pharmacist giving a Pharmaceutical Advice
  • The end goal is to assess which information we have and what we miss to ensure that medication related information is available and recorded as needed
  • Dedicated TCons to this topic. Schedule will be proposed by Marc/Tom
  • Further schedule
  • Whitepaper is unlikely to be finished this season
  • Schedule will be relaxed according to availability of the contributors


15:00-16:00 Glossary work item

  • Current goal restricted to finding a common glossary between IHE Pharmacy and HL7 Pharmacy
  • Target audience of this glossary: Implementors, Software architects, Consultants, ... (domain experts know definitions anyway)
  • Other sources (ISO TC215 WG6, CEN TC251, WHO, EMEA, ...) are considered to retrieve definitions, but no contribution to these other bodies yet
  • Exception: Definitions in column "Nictiz-definitions" were the starting point of the work (currenlty still in the spreadsheet, will be merged in and removed in the end)
  • Once completed, the result will be handed over too ISO TC215 WG6
  • Note: Definitions of other sources sometimes do not serve the purposes our two groups (e.g. two precice, too complicated, ...)
  • Review by Pharmacists intended
  • Julie for HL7 Pharmacy
  • Jacqueline for IHE Pharmacy
  • Special topic "Definition of Prescription"
  • Jacqueline will check the professional definitions
  • General procedure
  • Step 1: HL7 and IHE fill their columns with its definition
  • Step 2: Agreement between HL7 and IHE per column by the working group
  • Step 3: General agreement by the committees
  • Step 4: If necessary, CPs to affected profiles to align glossaries
  • Step 5: Hand over result to ISO 215
  • Further schedule
  • Intended to finish until end of season
  • Reason: Time pressure because a common glossary is fundamental for all profile development and cross-domain work to avoid confusion. It should be harmonized and stable as soon as possible.


16:45-17:00 Other business

  • Tom informs that in the Netherlands the local HL7 Pharmacy and IHE Pharmacy do e joint comparison of the HMW profile to the national HL7v2.4 guidelines to that topic. Goal is to shift to IHE Pharmacy profiles
  • Maybe some involved vendors are thereby anchoraged to step into HMW
  • Make CMPD better readable
  • Profile seem very complex at first sight, this might discourage people from using it
  • Thoughts on better presentation
  • Simplify actor diagram and remove parts which are just necessary in multi-domain
  • Keepp first part of profile just single-domain, add multi-domain capabilities at the very end