Professional Documents
Culture Documents
Webinar
Jrgen Brandsttter, MSc
Co-chair Pharmacy Planning committee
Co-chair Global Deployment Coordination Committee (GDC)
IHE International Board
CodeWerk Software GmbH, Austria
Learning objectives
Learning objectives
What is IHE?
eHealth Projects
Standards
IETF
Use cases typically require
combinations of standards
- but how to compose?
IHTSDO
What is IHE?
Standards
IETF
IHTSDO
eHealth Projects
IHE methodology
Projects
Products
Identify
available
standards
Products
declare
IHE
Use Case
RFPs
with IHE
reqs
IHE
Uses existing standards to profile Interoperability use-cases
IHE is a non-profit association dedicated to interoperability in health
information technology.
Pharmacy
since 2008
IHE Dental
Radiology
since 1998
Cardiology
since 2003
IHE Endoscopy
Pathology
since 2006
Eye Care
since 2006
Laboratory
since 2003
(Healthcare)
IT Infrastructure
since 2003
Quality
Research & Public Health
since 2007
since 2008
Patient Care Devices
since 2005
Radiation Oncology
since 2004
Strategic goals
1) http://eur-lex.europa.eu/legal-content/EN/TXT/?uri=OJ:JOL_2015_199_R_0011
Learning objectives
Liaisons
IHE Pharmacy
Profiling Layer
Friendly
collaboration
HL7 Pharmacy
Base Standards
Liaisons
ISO Standards
Global recognition
IHE Pharmacy
Profiling Layer
Contributions
HL7 Pharmacy
Base Standards
Base and
legal binding
standards
Liaisons
High-level
Projects
ISO Standards
IHE Pharmacy
Profiling Layer
Technical
Profiles
(Use Cases)
HL7 Pharmacy
Base Standards
Learning objectives
Our approach
Create and maintain a common data model
1)
Final version
Released in early 2010
78 pages
Community Pharmacy use cases
Hospital Pharmacy use cases
Harmonization of actors definitions
Current version:
ftp://ftp.ihe.net/Pharmacy/White%20Paper/IHE_Eur_Pharmacy_White_Paper_Final_Text_1.3.3.pdf
Prescription
Prescribed
Specialist, GP
Rejected
Pharmaceutical
advice
Pharmacist
Approved
Dispense
Pharmacist
Repeat
dispense
Administration
Patient, Nurse, Family member
Dispensed
Medication
Dispenser
(supply and distribution are
covered, but not profiled yet)
Dispense (DIS)
In sync with upcoming ISO DTS 19293
Requirements for the record of Dispense
Medicinal Products
Create Prescriptions/Dispenses
Create
Prescription
Create Dispense
Create Prescriptions/Dispenses
Create
Prescription
Create Dispense
Manage Prescriptions/Dispenses
Manage Prescriptions/Dispensations
Manage Prescriptions/Dispenses
Manage Prescriptions/Dispensations
Query/Retrieve Medication
Documents
PRE
PI 1
Physician prescribes
a prescription with 5
prescription items
PI 2
PI 3
PI 4
PI 5
Physician cancels PI 3
Physician changes PI 1
PRE
PI 1
PADV
PADV 1
PADV
PI 2
PI 3
PI 4
PI 5
PADV 3
Pharmacist dispenses
all PIs
PRE
PI 1
PADV
PADV 1
DIS
DIS 1
DIS 2
PI 2
PI 3
PI 4
PI 5
DIS
DIS
DIS 4
DIS
DIS 5
PRE
PI 1
PADV
PADV 1
DIS
DIS 1
DIS 2
PI 2
PI 3
PI 4
PI 5
DIS
PADV
PADV 2
DIS
DIS 4
DIS
DIS 5
PADV
PADV 5
Planning / Actual
Physician
starts
medication
treatment
Physician
changes
dosage
PADV
PADV
Change
MTP
PRE
Physician
changes
dosage
again
Patient
runs out of
medication
s
DIS
DIS
PADV
Change
Change
PRE
DIS
Action
Plan
Actual
Time
Logical flow
Leads to
Reference to MTP
Reference to PRE
Reference to DIS
Synced
Increasing patient safety by providing a Medication List of a patient for physicians and
pharmacists to support prescribing and medication interaction checking
Nation-wide rollout (8 mio people): All physicians and pharmacists will be connected
Rollout and startup on volunteer basis 2016, mandatory use for physicians and pharmacies
starting 2017
prescriptions and dispenses have to be captured electronically to act as data-source for the
medication list (e-prescription/dispense system)
does not replace paper prescription yet (just for capturing data)!
Covered use-cases
Covered use-cases
Increasing patient safety by sharing the Medication Treatment Plan of a patient between all
stakeholders (hospitals, private physicians, pharmacists, home care, )
Defining a national profile for sharing patients medication related information in relation with
the forthcoming federal law on the electronic patient record (2017)
Cantonal roll-out hospital, physicians, pharmacists and home care will be connected to the
shared treatment plan module of the regional Health Information Exchange
Rollout and startup first quarter 2016 on a voluntary basis
Covered use-cases
Learning objectives
Distributor
Dispensing
Systems
Hospital
Point of care
Catalog maintenance
Selection of vendors | Pricing & Contracts | Update product data
Internal data (Clinical data, internal prices, usage rules, usage
instructions)
Consult product data
Inventory management
Availability and recall
Permissions, availability, recall
Billing
Patient charges / intra-hospital charges
Hospital billing
Common Panorama
Medication
Catalog
Medication
Statements
Medication
Lists
Planning
Prescribing
Review /
Advice
Dispensing
Administration
ADE
reporting
Supply
For Communities
For Hospitals
FHIR-based (common)
Other activities
Medication Catalog / Formulary
How do we identify medication across different systems? Are
names sufficient? Are codes necessary? How do we
distribute the medication attributes across several systems?
Medication Data capture / Medication Documentation
How to retrieve data from prescriptions, dispenses, etc. In
order to create a medication list
Medication Administration (in Community domain)
More and more eligible to document electronically also in
Community domain
Learning objectives
Learning objectives
Sep
Dec
Jun
Jul
Dec:
Jun:
Jul:
Aug:
Links
White Paper
ftp://ftp.ihe.net/Pharmacy/White%20Paper/
Technical Frameworks
http://www.ihe.net/Technical_Framework/index.cfm#pharmacy
Pharmacy Wiki
http://wiki.ihe.net/index.php?title=Pharmacy
Strategic planning page
http://wiki.ihe.net/index.php?title=PHARM_Strategic_Planning
Roadmap
http://wiki.ihe.net/index.php?title=PHARM_Roadmap
Committees
http://wiki.ihe.net/index.php?title=Pharmacy_Planning_Committee
http://wiki.ihe.net/index.php?title=Pharmacy_Technical_Committee
Google group
http://groups.google.com/group/ihe-pharmacy