The Michigan Upper Peninsula Critical Access Hospital HIT Network Implementation Project

1. The Michigan Upper Peninsula Critical Access Hospital HITNetwork Implementation Project Donald A. Wheeler, FACHEPrimary Investigator Moving Community Health To the 21st Century AHRQ 2006 Annual Patient Safety & Health Information Technology Conference June 5, 2006

2. Critical Access Hospital HITNetwork Implementation ProjectParticipants • 10 Critical Access Hospitals • Marquette General Health System (MGHS) • Upper Peninsula Health Care Network (UPHCN) • A 10-year+ history of working cooperatively • Developing shared services and information systems

3. The Michigan Upper Peninsula HIT Network

4. PARTNER HOSPITAL OPERATIONAL INFORMATION The Michigan Upper Peninsula HIT Network

5. The Upper Peninsula Health Care Network • Formed 1995 • Serves 319,000 residents of Michigan’s Upper Peninsula • 16 members: all hospitals (-1), tribal health center & mental health agency • Elections • Each Member has one vote • Full-time CEO and support staff • Major Committees include: • Business Office Manager • Chief Financial Officer • Dietary Manager • HIPAA • Information Systems Workgroup • Laboratory Manager • Materials Management • Regional Medical Control Network • Pharmacy Manager • Radiology Manager.

6. UPHCN Collaborative Efforts • U.P. Poison Crisis Network • Hospital Home Care Network • Joint purchasing (materials, rx, lab, rad, etc.) • Mobile MRI services • Education • U.P. Medical Library Consortium • Publication of the U.P. Physician Directory • Primary care & specialty physician outreach clinics • Cardiac services network • U.P. Teleradiology, Teleconferencing, Telemedicine Networks • Telepathology • Remote pharmacy • U.P. Regional Blood Center • Reference lab outreach network • Information technology.

7. Interface Engine (SeeBeyond/UPCare) HIS (HBOC) LIS (Cerner) MPI (SeeBeyond/UPCare) Claim verification Claim tracking (eBill) E-mail (Lotus Notes) Decision support (EPSi) Knowledge-bases (MicroMedex, etc.) Internet Web-site design/hosting ED Log Practice management information system (MiSys) Electronic microfiche (Redwood) Tele-Pathology Tel-EKG Tele-Echocardiograms Tele-EEG Remote Pharmacy Tele-Radiology (Siemens, eWeb) HIPAA coordination MSDS’s (Hazsoft) Michigan Childhood Immunization Registry (MCIR) Tele-Conferencing (IP) Tele-Medicine (IP) RIS (Cerner->Siemens) Reference Lab Outreach (KliniTek) Wireless patient/visitor access PACS (Siemens Cosmos) EMR (KliniTek UPCARE®eMR). UPHCNInformation Technology Services

8. The Michigan Upper Peninsula HIT Network Identified Needs • Caregivers lack accurate and timely patient information when caring for a patient • When a patient‘s care is transferred from one setting/provider to another, tests and exams are frequently duplicated • There exists a lack of primary care to specialist and specialist to primary care communications and information • Lack of accurate and timely patient information creates serious patient care problems and potential adverse reactions • Inpatient transfers between hospitals and specialty physicians are hindered and delayed due to the need to “track down,” copy and deliver patient records and test/exam results.

9. The Michigan Upper Peninsula HIT Network Purpose “To Improve patient safety and quality of care through the regional planning, development, and implementation of Health Information Technologies.”

10. The Michigan Upper Peninsula HIT Network Long-Term Goals Assess quality of patient care, patient safety, and outcomes through consolidated patient clinical and care measures data collected by the Network HIT applications Provide clinical data sharing among participating entities through high-speed connectivity and data compatibility across the Network Partners I.T. applications to support optimal care delivery.

11. The Michigan Upper Peninsula HIT Network Desired Outcomes • Provide caregivers with as much information as possible when caring for the patient • Eliminate/reduce number of duplicate tests and exams when a patient‘s care is transferred from one setting/provider to another • Enhance primary care->specialist and specialist->primary care communications and information • Improve care provided in Partner hospital emergency departments • Improve inpatient transfers between Partner hospitals, Marquette General Hospital, and specialty physicians • Enable the conduct of medication reconciliation when patients are transferred between facilities, emergency departments, and specialty and primary care physicians • Eliminate hard-copy reports, paperwork, courier deliveries, and most types of handwritten clinical data by the end of the decade!

12. The Michigan Upper Peninsula HIT Network Project Oversight

13. The Michigan Upper Peninsula HIT Network Structuring the Solution • UPHCN provides the organizational structure to solve technical issues relative to sharing patient information • Across disparate systems • Between independently owned/operated organizations • Hospitals use their own Health Information Technology (HIT) within their facility: • Registration • Scheduling • Results • Order management • Clinical documentation, etc • Hospitals use UPCARE®eMR at their facility to view clinical results on their patient from other participating facilities, including their own.

14. The Michigan Upper Peninsula HIT Network UPCARE eMR - Phased Timeline

15. UPHCN Information TechnologyIn the beginning…1995 • No connectivity between Members • MGHS • “Best of Breed” w/interface engine • Upgrading clinical and financial systems • Demand for expanding I.T. resulted in growing I.T. staff • Other Members • “Best of Breed” w/o interface engine • Integrated “IBM 36” type systems for financials – no clinical systems • Little or no I.T. staff • Demand for I.T., but lacked capital and I.T. talent • MGHS packaged their I.T. services and systems and offered to Members • Many early adopters • Installed everything from networks to clinical and billing systems • Developed much of the data connectivity in use today • Established long-term trust and working relations.

16. UPHCN Information TechnologyToday • Hi-speed, private, secure network • 70 physical sites (more than just UPHCN Members) • Connects U.P. hospitals, providers, payers, patients • Data needs • Video needs • 9100+ user accounts • Managed through MGHS-IT department • Created working model, cost effective mechanism to access and share a host of systems and services • Provide the foundation to build • Local Health Information Technology (HIT) • Regional Health Information Organization (RHIO).

17. Steps leading to full implementation of an electronic medical record, according to a model developed by HIMSS Analytics. Current: 9 ½ stars Note: Based on information from more than 4,000 hospitals in the HIMSS Analytics database. Some 17% of U.S. hospitals have not achieved Stage 1.

18. EMR Development & MGHS Conclusions • Big vendor systems costly: $10’s millions dollars • Installations are not complete, therefore total costs $$$ unknown • Technology platforms tend to be “closed” vs. “open” • Limited by what vendor decides to do with product, i.e., little to no control over how product is developed • Purchase 80% of what you don’t need or can’t use… • …and only 20% of what you can use.

19. EMR Development &MGHS Direction • Buy “Best-of-Suite”, Develop, and Integrate option • Purchase clinical ancillary systems • Build a Clinical Data Repository (CDR) • Interface ancillary systems to the CDR • Develop web-based user interface/application to access data in CDR • Develop web-based order management & other EMR functions • MGH aligned w/KliniTek to develop an EMR that would work across the U.P. • Live on first version of UPCARE®eMR 6/04 • Today MGH has signed-up • 65% physicians/allied health professionals • 80% nursing professionals • 1,219 UPCARE eMR users • 10 Critical Access Hospitals • 2 Pilots in-progress.

20. UPCARE®eMRFramework • Master Clinical Data Repository (CDR) • Contains the ‘regional’ data elements, logic, and security for the system • Built on industry standards: 100% HL7 compliant, LOINC, ICD9 • Master Person Index (MPI) • Maintains a unique, ‘regional’ identifier for every patient in the U.P. • Provides the matching logic to ensure data is associated with correct patient • Cross-reference database to track all patient identifiers • Interface Engine (SmartIE™) • Connects systems to UPCARE • Formats data and ensures it is accurately stored in the CDR • User Interface (UI) • Screens used by clinicians to access & enter data • 100% web-based, i.e. thin, portable, mobile, single UI • Security • Role-based, manages who has access to what information and when • HIPAA compliant • Inference/Rules Engine – Object Logic Engine™ • Clinical decision support • Intelligent alerts/reminders. Electronic Medical Record

21. UPCARE eMRFunctionality • Patient census • Results • Order management • General/nursing • CPOE • Common registration • Bridge IP & OP settings • Provide common account number for same visit to store results • Scheduling • Enterprise procedures • Office appointment • Account Maintenance • Ensuring results are associated with correct patient • 100% Web-based • Single UI • Ultra-thin client • Fast • Portable & mobile. Electronic Medical Record

22. App Layer Merge Move Census Scheduling Order Entry Common Registration Result Admin Charges Users Interact Here Business Layer Result Order Entry Scheduling CPOE Registration Frame Work HL7 MPI Interface Engine Business Process Decision Support Schedule Core Analyzer Security Message Dispatcher Logging Life Cycle Systems Connect Here Platform Object Logic™(proprietary rules engine) .NET 2.0 (Microsoft) OS (Microsoft Internet Explorer) UPCARE eMRSystem Architecture Electronic Medical Record

23. Consolidated Patient Clinical Data via UPCare UPCare

24. Steps leading to full implementation of an electronic medical record, according to a model developed by HIMSS Analytics. 2007: 15 stars Note: Based on information from more than 4,000 hospitals in the HIMSS Analytics database. Some 17% of U.S. hospitals have not achieved Stage 1.