Integrating the Healthcare Enterprise and the Patient Care Devices Domain Ken Fuchs Draeger Medical...
78
Integrating the Healthcare Integrating the Healthcare Enterprise and the Enterprise and the Patient Care Devices Domain Patient Care Devices Domain Ken Fuchs Draeger Medical Systems, Inc. (Andover, MA) IHE Patient Care Devices Domain Co- Chair [email protected] NESCE October 9, 2008
-
Upload
samuel-evans -
Category
Documents
-
view
235 -
download
4
Transcript of Integrating the Healthcare Enterprise and the Patient Care Devices Domain Ken Fuchs Draeger Medical...
Integrating the Healthcare Enterprise Integrating the Healthcare Enterprise and the and the
Patient Care Devices DomainPatient Care Devices Domain
Ken FuchsDraeger Medical Systems, Inc. (Andover, MA)
IHE Patient Care Devices Domain [email protected]
NESCEOctober 9, 2008
© 2008 ACCE, HIMSS, IHE
2
This presentation can be found as follows:
Go to FTP Site:ftp://ftp.ihe.net/Patient_Care_Devices/Presentations/
Look for: NESCE Presentation 2008-10-09
3
Outline
• What is Interoperability?
• What is the IHE?
• What is the PCD?– What is the IHE PCD Process?– What are the IHE PCD Profiles?
• Why Should You Care about IHE?
• What Can You do?
• References and Contacts
4
What is Interoperability?
5
Current State of Affairs
• Proprietary protocols or variations on “Standard” protocols
• Hard to integrate with collaborating systems– difficult, expensive, and requiring continued
monitoring
• Hard to integrate with competing vendors systems
– difficult, expensive and requiring continuing negotiation for cooperation
• Hard to change from one vendor to another
• Requires careful selection, contracting, collaboration
6
Interoperability
The Goal - Interoperability:The Goal - Interoperability:
The ability of two or more systems or components to exchange and use the information exchanged– Accurately, securely, verifiably– When and where needed
Adapted from HL7, www.hl7.org
– With minimal or no effort, “Plug and Play”With minimal or no effort, “Plug and Play”
7
What is IHE?
8
Integrating the Healthcare Enterprise International
The IHEThe IHE• An international umbrella organization sponsored
by RSNA, HIMSS and others…• Voluntary, non-profit, operating in public view
– Largely manufacturers, users, regulators
• An initiative by healthcare professionals and industry to improve the way computer systems share information. Systems developed in accordance with IHE Profiles communicate with one another better, are easier to implement, and enable care providers to use information more effectively.
9
What is IHE?
What does IHE Do?What does IHE Do?
• In a nutshell:– IHE identifies Real-World Interoperability problems– Brings people together to design, test and demonstrate
solutions using existing standards.
10
IHE International
11
What is the IHE?
Value PropositionsValue Propositions
• The IHE supports– Patient safety and reduced medical errors– Effective patient care with information when,
where needed– Efficient organizations, less tedious and
redundant work– Reduced cost
• Development is facilitated now, more in the future• Complexity of interface deployment, management• Regulatory compliance
– Best of breed for the organization– National mandate for electronic medical
records
12
Standards: Necessary…Not Sufficient
• Generally Standards are:– Foundational - to interoperability and
communications– Broad - varying interpretations and
implementations– Narrow - may not consider relationships between
standards domains– Plentiful - often redundant or disjointed– Focused - standards implementation guides
typically focus on a single standard
IHE provides a defined process for IHE provides a defined process for implementingimplementing standards standards
13
IHE: Connecting Standards to Care
• Coordinate implementation of standards to meet clinical and administrative needs– Clinicians and HIT professionals identify the key
interoperability problems they face– Providers and industry work together to develop
and make available standards-based solutions– Implementers are able to follow common
guidelines in purchasing and integrating effective systems
• IHE is not an SDOSDO, but does provide feedback
IHE: A forum for defining needs, implementing IHE: A forum for defining needs, implementing standards and processes for making it happenstandards and processes for making it happen
14
International Adoption of IHE
FranceUSA
Germany
Italy
JapanUK
Canada
Korea
Taiwan
Norway
Holland
SpainChina
Yea
r 1
(199
9)
Yea
r 2
(200
0)
Yea
r 3
(200
1)
Yea
r 4
(200
2)
Yea
r 5
(200
3)
Yea
r 6
(200
4)
Yea
r 7
(200
5)
Yea
r 8
(200
6)
15
IHE Domains
Radiology (18)
IT Infrastructure for Healthcare (17)
Cardiology (7)
Laboratory (6)
Radiation Oncology (1)
Patient Care Coordination (5)
Patient Care Devices (1)
Quality
Eye Care (3)
VeterinaryEndoscopyPathologyPharmacy
Ye
ar
1
(19
99
)
Ye
ar
2
(20
00
)
Ye
ar
3
(20
01
)
Ye
ar
4
(20
02
)
Ye
ar
5
(20
03
)
Ye
ar
6
(20
04
)
Ye
ar
7
(20
05
)
Ye
ar
8
(20
06
)
Ye
ar
9
(20
07
)
• Over 100 vendors involved world-wideOver 100 vendors involved world-wide• 8 Technical Frameworks8 Technical Frameworks• 48 Integration Profiles48 Integration Profiles
•Testing at “Connectathons” world-wideTesting at “Connectathons” world-wide• Demonstrations at major conferences world-wideDemonstrations at major conferences world-wide
16
Two Foundational Domains
• IT Infrastructure Domain– Common foundational profiles
• ADT – including patient identity• CT – consistent time• Document transactions• Security
• Patient Care Coordination Domain– Coordination between specific domains
17
What are Profiles?
• A profile describes the application of a standard(s) to provide specific requirements to accomplish the communication requirements.– Provides an opportunity for users & vendors to
define requirements• Requirements for development • With Conformance Statements, for purchase
• Examples– HL7/DICOM – IHE Radiology– HL7/IEEE 11073 – Patient Care Devices
18
What is the Process?
• Define needs• Set priorities• Develop “profiles” with use cases• Recruit volunteers for each profile to be
developed• Develop the technical solutions• Demonstrate successful implementation
– Connectathons– Showcases
• Publish for public access, comment at various stages
19
IHE – One Year Cycle
Q2 Q3 Q4 Q1Survey & Propose Use Cases (Profiles)
Develop Use Cases
Prioritize Use Cases
Document Technical Profiles
Develop Product SW
Bench Test Software
Connectathon(s)
Public Demonstration(s)
20
What is PCD?
21
PCD Domain Overview
IHE PCD CharterIHE PCD Charter
The Patient Care Devices Domain is concerned with Use Cases in which at least one actor is a regulated regulated patient care devicepatient care device. The PCD coordinates with other IHE clinical specialty based domains such as medical imaging and laboratory.
22
PCD Domain Overview
• Established in 2005 when the “charter” was awarded to the ACCE
• Jointly sponsored by ACCE and HIMSS as of July 1, 2006
• Technical Framework 2006-7 developed to communicate patient data (asynchronous)
• Successful demonstration at the 2007 & 2008 Connectathons and HIMSS Interoperability Showcases
23
PCD Participation in IHE
24
PCD Domain Overview
IHE PCD MissionIHE PCD Mission
The IHE Patient Care Devices Domain will apply the proven, Use Case drivenUse Case driven IHE processes to:
– DeliverDeliver the technical frameworktechnical framework for the IHE-PCD domain profiles;
– ValidateValidate IHE-PCD profile implementations via ConnectathonsConnectathons; and
– Demonstrate Demonstrate marketable solutions at public trade public trade showsshows.
25
PCD Domain Overview
• Heterogeneity – Coexistence in a multi-manufacturer / multi-modality world, leveraging shared infrastructure
• Semantic Interoperability – … from the sensor to the EHR
• Real-time Availability – Facilitating more timely clinical decisions
PCD Profile Value Objectives:PCD Profile Value Objectives:
26
Emerging IHE-PCD Workflows
Key Objectives 2007/2008Key Objectives 2007/2008• Enterprise sharing of Patient Care Data• Patient Identity Binding to Device Data• Subscribe to Patient Data
Key Objectives 2008/2009Key Objectives 2008/2009• Rosetta Stone Terminology Project• PCD Alarm Communication Management• Infusion Pump Integration - Drug Administration
Key Objectives 2009 and beyondKey Objectives 2009 and beyond• Point of Care Plug and Play (multiyear effort)• Real-time data archiving and communication• Medical Device Management• Mobile, enterprise-wide, reliable vital signs monitoring• … many more!
Initial device classes…vital sign and patient monitors, infusion pumps, ventilators and anesthesia systems
27
Process
ProcessProcess
• Survey• Brief Profile Proposals• “Vetting” by Planning and Technical Committees• Setting priorities• Development of Technical Framework Supplements• Design of new profiles• Virtual testing• Face-to-Face testing at Connectathon• Demonstration at HIMSS
28
IHE-PCD Surveys 2005 and 2006
SurveysSurveys
• To set priorities, direction• Survey Managed by HIMSS Analytics• Open Solicitation to HIMSS, ACCE,
AdvaMed, Anesthesia Patient Safety Foundation, ECRI membership
• 171 Responses, (103 Users, 68 Vendors)• Please return and review at leisure
29
IHE Patient Care Devices (PCD)
HIMSS Survey IHE pre-2005 Annual Conference results:HIMSS Survey IHE pre-2005 Annual Conference results:
• Further, Further, 56%56% said they’d pay more for IHE-compliant said they’d pay more for IHE-compliant products!products!
• Survey of all IHE Users
• Over 50% of those surveyed said patient care devices should be the next area developed for IHE *
30
2006 Survey Question: How important is it for the following devices to become integrated under IHE?
= Users= Vendors
0 10 20 30 40 50 60 70 80
Dialysis (acute / chronic)
Intra-Aortic Balloon Pumps
Infusion Pumps
Anesthesia Systems
Ventilators
Physiological Waveform Monitors
Vital Signs Reporting Devices
Percent of respondents that consider it important
31
2006 - Survey Question: Which clinical applications should IHE target?
= Users= Vendors
0 10 20 30 40 50 60 70 80
Wellness Monitoring (Such as non-clinical fitness activities)
Home Health monitoring (Such as remote monitoring of key indicators, smarthealthcare appliances, etc.)
Remote Consultation
Image Guided Surgery
Asset Utilization Management (Such as asset tracking, self-diagnosis / reportingsystems)
Remote viewing of waveforms
Integration of live waveform information into Clinical Systems
Clinical Decision Support
Alarm Notification Management
Remote Viewing of patient information on PDA or Tablet devices
Drug Administration
Medication Management
Real-time medical error detection / mitigation
Communicating physiologic measures to the EHR
Percent of respondents that consider it important
32
Brief Profile Proposal
• Description of the Problem• Key Use Case(s) (example of how the
proposed solution will work)– Describe a short use case scenario from
the user perspective. The use case should demonstrate the integration/workflow problem.
• Standards and Systems Available
• Discussion
33
Development of Technical Document
• Brief Profile Proposal• Evaluation of Feasibility• Prioritization of Feasible Profiles• Detailed Profile Proposal• A Technical Committee Working
Group Develops Detail• Public Review and Modification• Publication as Trial Implementation
Version
34
Implementation and Testing
• Vendors Volunteer to Test the Trial Implementation Version and Prototype Systems at a Connectathon
• TI Versions May be Modified
• Vendors With Successful Systems– May demonstrate at a Showcase– Can claim conformance after two or three
tests
35
• IHE Connectathon 2008 – Hyatt ChicagoIHE Connectathon 2008 – Hyatt Chicago
36
PCD Profiles
37
PCD - Published Profiles
DEC ProfileDEC Profile
Device to Enterprise CommunicationDevice to Enterprise Communication
38
DEC Profiles
• PCD DEC profiles support the communication of patient clinical data from devices.
• This data can include:– Vital Signs (profile available)– Alarm information (2008/2009 profile)– Waveform information (future profile)– Etc.
39
DEC - Subscribe to Patient Data
40
DEC Profile Mapping Model
• ISO/IEEE 11073 Domain Information Model and Nomenclature mapped to HL7 (v2.5) Observation Report
• ISO/IEEE 11073 Data Types mapped to HL7 Data Types
• Mapping preserves measurement context for complex devices.
41
IEEE 11073 Domain Information Model Defines Device Context
10..n
Medical Device System (MDS)
Virtual Medical Device (VMD)
Channel (Chan)
Numeric
Enumeration
1
*
1
*
1
*
1
0..*
Metric
42
Mapping preserves measurement context
Medical Device System (MDS)
Virtual Medical Device (VMD)
Channel (Chan)
Numeric
Enumeration
1
*
1
*
1
*
1
0..*
Metric
43
Example PCD-01 Message
MSH|^~\&|INFO_SRC_PHILIPS^ACDE48234567ABCD^EUI-64||||20061215153500||ORU^R01^ORU_R01|PMS116621490051| P|2.5|||NE|AL||8859/1 PID|||AB60001^^^Philips Medical^PI||Brooks^Albert^^^^^L||19610101|M PV1||I|UNIT_1^^Bed1 OBR|1|PMS116621490051^INFO_SRC_PHILIPS^ACDE48234567ABCD^EUI-64| PMS116621490051^INFO_SRC_PHILIPS^ACDE48234567ABCD^EUI-64| 69837^MDC_DEV_METER_PHYSIO_MULTI_PARAM_MDS^MDC|||20061215153500 OBX|1|ST|184326^MDC_ECG_STAT_ECT^MDC|1.5130.1.184326|""||||||F OBX|2|ST|184327^MDC_ECG_STAT_RHY^MDC|1.5130.1.184327|Sinus Rhythm||||||F OBX|3|NM|150456^MDC_PULS_OXIM_SAT_O2^MDC|1.5238.1.150456|99|262688^MDC_DIM_PERCENT^MDC|||||F OBX|4|NM|147842^MDC_ECG_HEART_RATE^MDC|1.5130.1.147842|81|264864^MDC_DIM_BEAT_PER_MIN^MDC|||||F OBX|5|NM|150037^MDC_PRESS_BLD_ART_ABP_SYS^MDC|1.5190.1.150036|126|266016^MDC_DIM_MMHG^MDC|||||F OBX|6|NM|150038^MDC_PRESS_BLD_ART_ABP_DIA^MDC|1.5190.1.150036|76|266016^MDC_DIM_MMHG^MDC|||||F OBX|7|NM|150039^MDC_PRESS_BLD_ART_ABP_MEAN^MDC|1.5190.1.150036|92|266016^MDC_DIM_MMHG^MDC|||||F OBX|8|NM|148065^MDC_ECG_V_P_C_CNT^MDC|1.5130.1.148065|0|264864^MDC_DIM_BEAT_PER_MIN^MDC|||||F OBX|9|NM|150045^MDC_PRESS_BLD_ART_PULM_SYS^MDC|1.5190.1.150044|26|266016^MDC_DIM_MMHG^MDC|||||F OBX|10|NM|150046^MDC_PRESS_BLD_ART_PULM_DIA^MDC|1.5190.1.150044|9|266016^MDC_DIM_MMHG^MDC|||||F OBX|11|NM|150047^MDC_PRESS_BLD_ART_PULM_MEAN^MDC|1.5190.1.150044|14|266016^MDC_DIM_MMHG^MDC|||||F OBX|12|NM|149538^MDC_PLETH_PULS_RATE^MDC|1.5238.1.149538|55|264864^MDC_DIM_BEAT_PER_MIN^MDC|||||F OBX|13|NM|150067^MDC_PRESS_BLD_ATR_LEFT_MEAN^MDC|1.5190.1.150064|4|266016^MDC_DIM_MMHG^MDC|||||F OBX|14|NM|150087^MDC_PRESS_BLD_VEN_CENT_MEAN^MDC|1.5190.1.150084|12|266016^MDC_DIM_MMHG^MDC|||||F
44
PCD - Published Profiles
PIB ProfilePIB Profile
Patient Identity BindingPatient Identity Binding
45
Patient ID Binding
46
Patient ID Binding
• Automates identity association / authentication process using standard ITI profiles.
• Option for the DEC Profile• Async identity access using ITI-21 Patient
Demographics Query (PDQ)• Sync identity acquisition using ITI-30 Patient
Admin Management / Patient Identity Feed (PAM)
DEC-PIB profile…DEC-PIB profile…
47
PCD - New Profiles 08/09
RTM ProfileRTM Profile
Rosetta Terminology MappingRosetta Terminology Mapping
48
Rosetta for Semantic Interoperability
49
Rosetta for Semantic Interoperability
Migrating Toward True PCD Semantic Interoperability
Today HIMSS ’09!
ISO/IEEE 11073Semantic Standards
Vendor Semantics
IHE PCD TF Content
Vendor A
Vendor C
Vendor B
RosettaMappingTables(RTM)
11073PnP Comm
HL7 v3CDA/CCD
HL7 v2Messages
50
RTM Cardiovascular (multiple vendors)
Group REFERENCE_ID Vendor_Description
CODEVendor
A Vendor
BVendor
C
CVS_ECG_HR MDC_ECG_CARD_BEAT_RATE Heart Rate (DBR 326) 16770 HR HR HR
CVS_ECG_HR MDC_ECG_CARD_BEAT_RATE_BTB Beat-to-Beat Rate 16778 btbHR
CVS_ECG_HR MDC_ECG_HEART_RATE Heart Rate (DBR 2178) 16770 HR HR HR
CVS_ECG_HR MDC_ECG_PACED_BEAT_RATE %PACED 16554 %PACED
CVS_ECG_HR MDC_ECG_TIME_PD_RR_GL R to R Interval 16168 rr_time rr_time rr_time
CVS_ECG_QT MDC_ECG_TIME_PD_QT_GL QT interval 16160 QT
CVS_ECG_QT MDC_ECG_TIME_PD_QTc QT interval (corrected) 16164 QTc
CVS_ECG_RHY MDC_ECG_ARRHY Arrhythmia 4410 ARR
CVS_ECG_RHY MDC_ECG_V_P_C_CNT PVC rate. 16993 PVC/min PVC PVC
CVS_ECG_ST MDC_ECG_AMPL_ST ST generic label 768 ST ST
CVS_ECG_ST MDC_ECG_AMPL_ST_AVF ST lead aVF 832 STaVF ST-AVF ST-aVF
CVS_ECG_ST MDC_ECG_AMPL_ST_AVL ST lead aVL 831 STaVL ST-AVL ST-aVL
CVS_ECG_ST MDC_ECG_AMPL_ST_AVR ST lead aVR 830 STaVR ST-AVR ST-aVR
51
PCD - New Profiles 08/09
ACM ProfileACM Profile
Alarm Communication ManagementAlarm Communication Management
52
ACM Statement
Alarm Communication Management enables systems to deliver the right alarms, with the right priority, to the right individuals via devices with the right content, escalating to other individuals via devices (based on system configuration)
Alarm Communication Management enables systems to deliver the right alarms, with the right priority, to the right individuals via devices with the right content, escalating to other individuals via devices (based on system configuration)
53
AlarmSource
AlarmAggregator
AlarmReceiver
AlarmCoordinator
AlarmDisseminator
AlarmCommunication
AlarmEndpoint
AlarmCommunication
(AC)
AlarmCommunication
(AC)
AlarmManagement
(AM)
AlarmManagement
(AM)
AlarmReporter
(AR)
AlarmReporter
(AR)
AlarmReporter
AlarmCache
Alarm
Query
(AQAQ)
Alarm
Query
(AQAQ)
Communication detailed in ACM profileCommunication detailed in ACM profile
Communication not detailed in ACM profileCommunication not detailed in ACM profile
.
.
.
.
.
.......
PCD Inputs(PM, NC, Resp,
Pump, etc.)
PCD Inputs(PM, NC, Resp,
Pump, etc.)
Output Devices(Marquee Sign, Pager,
Wi-Fi Phone or Badge, etc.)
Output Devices(Marquee Sign, Pager,
Wi-Fi Phone or Badge, etc.)
HIS, EMRHIS, EMROptionalOptional
ACM Actors
54
PCD - New Profiles 08/09
PIV ProfilePIV Profile
Point-of-Care Infusion VerificationPoint-of-Care Infusion Verification
55
PIV Statement
Point-of-Care Infusion Verification supports the electronic transfer of infusion parameters from a Barcode Point of Care (BPOC) system, also known as a Bar Code Medication Administration (BCMA) system, to an infusion pump.
Point-of-Care Infusion Verification supports the electronic transfer of infusion parameters from a Barcode Point of Care (BPOC) system, also known as a Bar Code Medication Administration (BCMA) system, to an infusion pump.
56
PIV Benefits
PIV will reduce errorsreduce errors by eliminating keystroke errors and by increasing the use of automatic dosage checking facilitated by onboard drug libraries. In addition to the reduction of medication administration errors, this integration may also increase caregiver productivityincrease caregiver productivity and provide more contextual information regarding infusion data.
PIV will reduce errorsreduce errors by eliminating keystroke errors and by increasing the use of automatic dosage checking facilitated by onboard drug libraries. In addition to the reduction of medication administration errors, this integration may also increase caregiver productivityincrease caregiver productivity and provide more contextual information regarding infusion data.
57
PIV as part of overall workflow…
Nurse
Review
MAR Entry
Pharmacist reviews
order detail
(Pharmacy
System)
eMAR updated
Medication
DispensedNurse removes
Medication
from Dispensing
Unit or Med Room
Nurse Confirms 5
Rights:
Right Patient,
Medication,
Dose, Time, Route
AT THE BEDSIDE
Medication
Administered
Physician reviews
data and places
Orders
Nurse
Review
eMAR Entry
Pharmacist reviews
order detail
(Pharmacy
System)
eMAR updated
Medication
DispensedNurse removes
Medication
from Dispensing
Unit or Med Room
Nurse Confirms 5
Rights:
Right Patient,
Medication,
Dose, Time, Route
AT THE BEDSIDE
Medication
Administered
Physician reviews
data and places
Orders
58
PIV Actors
Infusion OrderFiller(IOF)
Device
PCD-03: Communicate Infusion Order
BPOC or BCMA
Infusion OrderPlacer (IOP)
59
PCD – “In the Works”
• For the coming year, PCD is currently in the process of evaluating a number of Brief Profile Proposals:– WCM – Waveform Comm. Management– DPI – Device Point-of-Care Integration– MEM – Medical Equipment Mgmnt– Extensions to
• DEC• ACM• PIV• etc.
60
PCD - Showcase
HIMSS ShowcaseHIMSS Showcase
Where we get to show off !!Where we get to show off !!
61
Block Diagram of IHE PCD HIMSS Showcase 2008
GEGE
AwareAwareGatewayGateway
Patient Monitor, Ventilator
Intensive Care
PhilipsPhilipsIntellivue ClinicalIntellivue Clinical
InformationInformationPortfolioPortfolio
DraegerDraegerInnovianInnovian®®
Solution SuiteSolution Suite
CapsuleCapsule
PhilipsPhilipsIntellivueIntellivue
InformationInformationCenterCenter
Patient Monitor
Emergency Care Perioperative Care
LiveDataLiveData
OR –OR –DashBoardDashBoardTMTM
GE GE CentricityCentricity®®
PeriopPeriopAnesthesiaAnesthesia
EpicEpic
InPatientInPatient
Enterprise
PDQ/PAMServer
TimeServer
SpacelabsSpacelabs
IntesysIntesysClinical SuiteClinical Suite
Patient Monitor
Welch AllynWelch AllynConnexConnexTMTM
Data MgmtData MgmtSystemSystem
Vital Signs Monitor
DOR
DOC
B. BraunB. BraunDoseTracDoseTracTMTM
InfusionInfusionMgmt SWMgmt SW
InfusionDevices
DraegerDraeger
InfinityInfinityGatewayGateway
Patient Monitor, Anesthesia Sys
62
PCD @ HIMSS Showcase ‘08
63
HIMSS Showcase ’08 – ER & OR
64
HIMSS Showcase ’08 – ICU
65
Why use IHE PCD profiles?
• Simplified standards-based integration of point-of-care device info & services
• Multi-vendor product integration testing @ Connectathons
• Visibility of products with care providers and peer technology organizations in Showcases
• Path to programs such as the U.S. National Health Information Network (NHIN)
PCD profiles will enable…PCD profiles will enable…
66
Year 3 Implementation
Companies registered for the 2009 Companies registered for the 2009 Connectathon and HIMSS ShowcaseConnectathon and HIMSS Showcase
– B Braun, Cardinal, Hospira IV pumps with DEC, PIV
– Draeger, GE, Philips, Capsule - monitors, ventilators, anesthesia systems, with DEC
– Capsule, Cardinal, LiveData, Philips, Draeger - with ACM, DEC
• Above as of Oct. 1
67
Why Should You Care?
68
Why Should You Care?
Significance for Users/PurchasersSignificance for Users/Purchasers
• You Job (CE and IT)– CE and IT must collaborate on
selection, specification, installation, maintenance and support of these systems
– New knowledge and skills are required
69
Why Should You Care?
Significance for Users/PurchasersSignificance for Users/Purchasers
• Clinical implications– Patient safety– Enterprise wide access to the patient’s data– Quality of care– Ability to implement “best of breed”– Workflow improvements
• Financial implications– Rapid changes in technology increase risk– Interoperability reduces risk– Interoperability improves efficiency
70
What Can You Do?
71
What Can You Do?
• Plan, Evaluate, Purchase Conforming Devices
• In continuing discussions with vendors – at all levels– Push IHE, Interoperability
• Refer to lower deployment, maintenance costs– Encourage vendors’ active IHE participation
• Lower development, installation, support costs– Refer to profiles
• Leverage public and objective commitments
• In RFPs– Refer to profiles, Conformance Statements– Use Conformance Statements to “nail down” vendor’s
representations– Adopt very specific language
Raise the Bar!!Raise the Bar!!
72
What Can You Do?
ParticipateParticipate
The Planning Committee (PC):• Set member based priorities• Conduct Surveys• Develop Use Cases• Manage Connectathon, Showcase
The Technical Committee (TC):• Determine technical feasibility• Research standards• Develop Technical Framework• Establish conformance tests
73
What Can You Do?
To Help Define the FutureTo Help Define the Future• Become a member of a Domain’s Planning or
Technical Committees– Help establish priorities – what the domain will work on– Help define profiles – clinical, IT requirements– Provide the “business case” to encourage developments
• Provide Public Comments on Technical Framework Supplements
• Attend Demonstrations, Educational Events and Workshops
To join or ask questions send me an email:[email protected]
74
References
• Parisot, Charles. What IHE Delivers for Vendors, Purchasers, Users and Patients. IHE Interoperability Workshop Sept. 2004. http://www.ihe.net/Participation/upload/2_What%20IHE%20Delivers_final.ppt#319,1,Integrating the Healthcare Enterprise
• Gauvin, Alain. How to Purchase IHE Functionality. IHE Canada Workshop 2006. http://www.ihe-canada.com/Events/2006/06SepGauvin2.pdf
• Haramati, Nogah and Goodhew, Beth. Purchasing IHE Functionality. IHE Canada Workshop 2006. http://www.ihe-canada.com/Events/2006/06SepHaramati-Goodhew.pdf
• Bak, Peter. Achieving Interoperability Across Canada. IHE Workshop, June 2006. http://www.ihe.net/Events/upload/IHE%20Workshop%20June%202006%20Bak%20Infoway%20v2.ppt#724,1,Slide 1
• Braithwaite, William. IT at the Core of Healthcare Transformation. Proceedings, HIMSS 2007.
75
References
PCD ResourcesPCD Resources
• http://www.ihe.net/
• http://www.ihe.net/pcd
• http://www.ihe.net/Technical_Framework/index.cfm#pcd
• http://wiki.ihe.net/index.php?search=PCD+Proposals+2009-2010
• ftp://ftp.ihe.net/Patient_Care_Devices/Presentations
• ftp://ftp.ihe.net/Patient_Care_Devices/
76
Resources
This presentation can be found as follows:
Go to FTP Site:ftp://ftp.ihe.net/Patient_Care_Devices/Presentations/
Look for: NESCE Presentation 2008-10-09
77
PCD Contacts
PCD CoChairs:– Todd Cooper [email protected] – Ken Fuchs [email protected] – Ray Zambuto
• PCD Technical Project Manager:– Manny Furst [email protected]
• IHE Strategic Development Committee Co-Chair:– Elliot Sloane [email protected]
78
Thank You for Your Attention !!
