EPharmacy Workshop 9 June 2008-Minutes: Difference between revisions
Geert.claeys (talk | contribs) No edit summary |
Geert.claeys (talk | contribs) No edit summary |
||
| Line 22: | Line 22: | ||
*Zip archive: [ftp://ftp.ihe.net/International/Europe/Development/Pharmacy/Meetings/Meeting9June2008/_ePharmacy%20workshop%09062008%20Archive.zip here] | *Zip archive: [ftp://ftp.ihe.net/International/Europe/Development/Pharmacy/Meetings/Meeting9June2008/_ePharmacy%20workshop%09062008%20Archive.zip here] | ||
==Community pharmacy Use Cases== | |||
==Community | |||
-Document : xxx | |||
-Assumption : | |||
--Community pharmacy Use Cases and transactions will be aligned with IHE XDS Use Cases/ transactions : | |||
--Document centric actors : prescripton provider | |||
-Feedback : | |||
-- Terminology : use IHE terms where appropriate : e.g. prescription repository instead of prescription registry); name an actor by their role and not by their implementation (e.g. IT infrastructure provider instead of college of pharmacists; prescription producer instead of prescription modules, …) | |||
-- Security : add security mechanisms (authentications, auditing, encryption) in the sequence diagrams | |||
-- Domain model : | |||
--- Prescription attributes : Medication (dose, frequency, instruction), optional : symptions, diagnosis | |||
--- Dispensed medication attributes: dispensed medication, link to original prescription. | |||
-- Future work (>2009) | |||
--- Define the complete business process for e-pharmacy as a basis for identifying the critical use cases | |||
---Create Prescription (as part of CPOE) which contains transactions to drug database | |||
--Actions : | |||
--- All : send the minimal set of prescription/dispensed medication attributes that are required for a particular country to Juan Nunez | |||
==Hospital pharmacy Use Cases == | |||
-Document : xxx | |||
- Assumption : | |||
--Hospital pharmacy Use Cases and transactions will be aligned with IHE Use Cases/ transactions of other hospital departments | |||
--IHE/Scheduled Workflow centric actors : order filler = prescriber | |||
-Feedback : | |||
- Prioritize the Use Cases so that the realization fit in the 18 monts time interval of IHE. --- year1 priorities : basic prescription, simple substitution use case , exit medication (as consistency check between community and hospital pharmacy actors) | |||
-- year2+ priorities : complicated substitution use case, injectable follow-up use case,… | |||
-- Align terms with community pharmacy use cases : | |||
--- Rename “picking and dose preparation” actor into dispenser actor | |||
--- Rename Administration by “Medication administration manager” | |||
-- Add formulary = list of medication (+permission rules) in hospital; used for substitution | |||
-- Define the actor in terms of its responsibilities and need in terms of the actions that he performs. Include possible realizations for clarification | |||
==IHE Pharmacy domain== | |||
- The current IHE Europe – Pharmacy workgroup will evolve to a new global IHE Pharmacy domain that will take ownership for creating the technical specifications with the current Use Cases as input. | |||
- The creation of the IHE Pharmacy domain will consists of the following steps : | |||
--Identification of primarily users, vendors and sponsoring organizations (e.g. hospital pharmacy associations like xxx) | |||
-- Submission of application form that details scope, members/sponsors, roadmap ,, | |||
---Action : G. Claeys will circulate a 1st draft before mid July | |||
-- IHE International will review the application form and will make a go/no go decision : +- august | |||
- IHE follows a development heartbeat of 18 months - from initial use case to testing of implementations at connectathons | |||
- Timing : | |||
-- September 2008 : completion of Use Cases | |||
-- July 2009 : completion of Technical Framework | |||
-- Spring 2010 : test implementations at connectathons | |||
==Miscellaneous== | |||
- Intellectual Property: according to the IHE Governance document (http://www.ihe.net/governance/) is IHE the owner of all of produced documents. Contributors/editors have to sign the IHE membership agreement. | |||
- In order to remain neutral, IHE forbids the publication of organization logos in their publications. However, many IHE documents contains a list of supporting organizations in their introduction section. | |||
- Potential new members : UK , Germany [hospital pharmacist] | |||
==Next Steps == | |||
-Complete the Use Case descriptions, including actors and transactions. | |||
--Target date : End september 2009 | |||
--Action : | |||
---Editors : incorporate feedback | |||
---Documents will be completed during the 2 days workshop in September | |||
==Timing== | ==Timing== | ||
*June 2008 : Finalise main Use Case; submit to global IHE Development committee | *June 2008 : Finalise main Use Case; submit to global IHE Development committee | ||
*Mid 2008 – Mid 2009 : profile development (as global IHE Pharmacy committee) | *Mid 2008 – Mid 2009 : profile development (as global IHE Pharmacy committee) | ||
*2010 : Test IHE Pharmacy implementations at connectathons | *2010 : Test IHE Pharmacy implementations at connectathons | ||
Revision as of 03:05, 26 June 2008
Under Construction
Venue
- Brussels, 9 June 2008 from 10-17hr
Participants
- Belgium : V. Hayen (KLAV)
- France : J. Surugue (EAHP), F. Gener (Phast), S. Letellier (EAHP/Phast), J. Nies (Medasys), E. Serrot (Vidal), S. Juvin (GIP-DMP), C. Rica (GIP-DMP), K. Bourquard (Gmsih), J. Nies (Tedasys)
- Greece : L. Tzimis (EAHP)
- Netherlands : M. Sprenger(NICTIZ), R. Moss (EAHP)
- Spain : Juan Nunez(Indra)
- IHE Eur : G. Claeys (Agfa Healthcare)
All Documents
- Ftp site : ftp://ftp.ihe.net/International/Europe/Development/Pharmacy/Meetings/Meeting9June2008/
- Zip archive: here
Community pharmacy Use Cases
-Document : xxx -Assumption : --Community pharmacy Use Cases and transactions will be aligned with IHE XDS Use Cases/ transactions : --Document centric actors : prescripton provider -Feedback : -- Terminology : use IHE terms where appropriate : e.g. prescription repository instead of prescription registry); name an actor by their role and not by their implementation (e.g. IT infrastructure provider instead of college of pharmacists; prescription producer instead of prescription modules, …) -- Security : add security mechanisms (authentications, auditing, encryption) in the sequence diagrams -- Domain model : --- Prescription attributes : Medication (dose, frequency, instruction), optional : symptions, diagnosis --- Dispensed medication attributes: dispensed medication, link to original prescription. -- Future work (>2009) --- Define the complete business process for e-pharmacy as a basis for identifying the critical use cases ---Create Prescription (as part of CPOE) which contains transactions to drug database --Actions : --- All : send the minimal set of prescription/dispensed medication attributes that are required for a particular country to Juan Nunez
Hospital pharmacy Use Cases
-Document : xxx - Assumption : --Hospital pharmacy Use Cases and transactions will be aligned with IHE Use Cases/ transactions of other hospital departments --IHE/Scheduled Workflow centric actors : order filler = prescriber -Feedback : - Prioritize the Use Cases so that the realization fit in the 18 monts time interval of IHE. --- year1 priorities : basic prescription, simple substitution use case , exit medication (as consistency check between community and hospital pharmacy actors) -- year2+ priorities : complicated substitution use case, injectable follow-up use case,… -- Align terms with community pharmacy use cases : --- Rename “picking and dose preparation” actor into dispenser actor --- Rename Administration by “Medication administration manager” -- Add formulary = list of medication (+permission rules) in hospital; used for substitution -- Define the actor in terms of its responsibilities and need in terms of the actions that he performs. Include possible realizations for clarification
IHE Pharmacy domain
- The current IHE Europe – Pharmacy workgroup will evolve to a new global IHE Pharmacy domain that will take ownership for creating the technical specifications with the current Use Cases as input. - The creation of the IHE Pharmacy domain will consists of the following steps : --Identification of primarily users, vendors and sponsoring organizations (e.g. hospital pharmacy associations like xxx) -- Submission of application form that details scope, members/sponsors, roadmap ,, ---Action : G. Claeys will circulate a 1st draft before mid July -- IHE International will review the application form and will make a go/no go decision : +- august - IHE follows a development heartbeat of 18 months - from initial use case to testing of implementations at connectathons - Timing : -- September 2008 : completion of Use Cases -- July 2009 : completion of Technical Framework -- Spring 2010 : test implementations at connectathons
Miscellaneous
- Intellectual Property: according to the IHE Governance document (http://www.ihe.net/governance/) is IHE the owner of all of produced documents. Contributors/editors have to sign the IHE membership agreement. - In order to remain neutral, IHE forbids the publication of organization logos in their publications. However, many IHE documents contains a list of supporting organizations in their introduction section. - Potential new members : UK , Germany [hospital pharmacist]
Next Steps
-Complete the Use Case descriptions, including actors and transactions. --Target date : End september 2009 --Action : ---Editors : incorporate feedback ---Documents will be completed during the 2 days workshop in September
Timing
- June 2008 : Finalise main Use Case; submit to global IHE Development committee
- Mid 2008 – Mid 2009 : profile development (as global IHE Pharmacy committee)
- 2010 : Test IHE Pharmacy implementations at connectathons