Download Case Study: Smart Pump EHR Integration

Survey
yes no Was this document useful for you?
   Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Document related concepts
no text concepts found
Transcript
Case Study:
Smart Pump EHR Integration
Presented By:
Jeff McGeath, Senior Vice President
Software Solutions
Iatric Systems, Inc.
Agenda
 Smart Pump EHR Integration definition
 IHE standards and why they matter
 The right team and # of FTEs
 Workflow analysis
 Testing
 The benefits
Interactive session – Q&A throughout
In which department do you work?
 Nursing / Clinical Informatics
 Information Technology
 Pharmacy
 Biomedical Engineering
Smart Pump EHR Integration
Definition: The electronic transfer of IV med
orders from the EHR to smart pumps, and the
electronic transfer of start times, stops times
and other transfusion details back to the EHR.
 Bi-Directional
 EHR  Pump: Smart Pump Programming
(a/k/a Auto-Programming)
 EHR  Pump:
Auto-Documentation
Smart Pump EHR Integration
AAMI Report (5-year period):
 How often human error occurs
 56,000+ adverse events associated with IV pumps
 710 *deaths* associated with IV pumps
 34% happened during manual pump programming
The Solution: Smart Pump Programming
Smart Pump EHR Integration
Smart Pump Programming:
IV med orders from EHR  smart pump
No more manual pump programming,
Saving nurses time and preventing adverse events.
Smart Pump EHR Integration
Documentation Issues:
 Too time-consuming; not always documented
 Improper documentation = lower reimbursements
The Solution: Auto-Documentation
Smart Pump EHR Integration
Auto-Documentation:
EHR  IV Start and Stop Times, etc.
No more manual data entry,
And can help increase reimbursements.
IHE Interoperability Standards
 Integrating the Healthcare Enterprise
 Standard of choice for smart pump vendors
 IHE home page: www.ihe.net
 “PCD” is Patient Care Devices
 IHE PCD standards include smart pumps
 IHE PCD page: http://ihe.net/Patient_Care_Devices/
 “PIV” is Point-of-care Infusion Verification
 “IPEC” is Infusion Pump Event Communication
IHE Interoperability Standards
 IHE Integration Statement confirming PIV and IPEC
 IMPORTANT: Confirm Patient ID is stored on pump
 For more information, 1-hour on-demand webinar
 Go to You Tube and search for “How IHE is Advancing
Medical Device Connectivity”
Questions?
The Right Team & FTEs
 KLAS Research® 2015 report:
• Smart Pump/EMR Integration: What Are My Best
Options?
• Only 21 organizations (38 hospitals)
 Implementation = 6-9+ months
 Significant resources required from:
• Pharmacy – 500+ hours
• Nursing – 350+ hours
• Information Technology – 200+ hours
• Biomedical Engineering – 200+ hours
Workflow Analysis
Need to determine:
 Order verification and approval process
 Process for starting/holding/stopping an IV solution
 How staff perform rate changes/titrations
 How subsequent IV solutions are administered
Workflow Analysis continued
Don’t forget:
 Secondary/IVPB administration
 Bolus dosing (pump vs. manual)
 Transfer of IV solutions/emergency admin/syringe admin
 How to handle overfill
 Weigh-based dosing
 Priming tubing
Testing
Overview:
 Smart Pump Programming
 Auto-Documentation
 Barcode and Wireless Network
Testing
Smart Pump Programming:
 Connectivity Testing
Testing
Smart Pump Programming:
 Connectivity Testing
Testing
Smart Pump Programming:
 Connectivity Testing
 Functional Testing
 Ensure that the interface has all the required
functionality specified in your agreements with
your smart pump and EHR vendor (or MDI
solution vendor) — for example, Patient ID
Testing
Smart Pump Programming:
 Connectivity Testing
 Functional Testing
 End-to-end IV Medication Order Flow & Workflow Testing
 Dose/Rate/UOM combinations, additive testing,
dosing-based scenarios
 Error/exception testing, including clinical workflow
actions
Testing
Auto-Documentation:
 Pump event messages – produced every 60 seconds
Testing
Auto-Documentation:
 Pump event messages – produced every 60 seconds
 Data should include start/stop time, drug, volume, etc.
Testing
Auto-Documentation:
 Pump event messages – produced every 60 seconds
 Data should include start/stop time, drug, volume, etc.
 Validate data criteria, workflow steps, and integration to
EHR’s nursing documentation system
Testing
Barcodes and
Wireless Network
The Benefits of Smart Pumps EHR Integration
 Prevent errors and adverse events
• Saving lives = priceless!
• Reduces hospital’s liability
 Save nurses time
 Improve documentation
 Increase revenues
 Enforcement of drug library
Start planning now
Questions?
Thank You | Contact Us
Contact Us
Jeff McGeath, Senior Vice President
Software Solutions
Iatric Systems, Inc.
(978) 674-7205
[email protected]
www.iatric.com