CE LHIN: Hospital Information Technology Shared Services (HITSS) Project – Phase 1High Level overvieweHealth Steering Committee – April 7th, 2011

2

Agenda

•Project Overview / Mandate

•Project Objectives & Meeting Purpose

•Current State

•Next Steps

Project Background and Overview

The Central East Executive Committee believes it has identified that the establishment of a Hospital IT Shared Services among the partners in the Central East LHIN has the opportunity to:

Provide a higher level of service (capacity and capability) to each hospital;

Align IT investments and implement the infrastructure and interoperable solutions that will enable universally accessible electronic health records among CE LHIN community hospitals and the exchange of patient information with community providers and patients;

Leverage economies and efficiencies with IT services and IT users;

Enhance the capacity of the organizations to implement and optimize eHealth initiatives;

Accelerate the assessment, planning and adoption of emerging best practices / applications in IT that support quality and safety of patient care across participants; and

Create a platform for other joint projects that the members may wish to develop.

3

Review of current state & Identify gaps

Enable sharing of clinical data

Characterize the necessary success factors Analysis of eHealth adoption status Benchmarking similar shared services

Comparisons with other regional SS

Outline the pros and cons Shared initiatives in the CE LHIN LHIN expectations for integration Provincial eHealth initaitives

Project Scope

4

5

Standardized EMR

Shared Regional HIS System

Common Data Centre

Effectiveness and Efficiency

Common Business and Workflow Processes

Integrated Clinical

View

Hospital Efficiencies

HospitalIT SharedServices

IT Services in the CE LHIN

6

Receives the Service from Internal ProvidersReceives the Service from External Providers

Provides the service internallyProvides to others in the LHIN

7

8

9

eHealth Ontario Near Term PlansHigh-Level

PlansDetailed PlansLegen

d:Planning

Build; Limited Production Release (LPR); Provincial roll out

2011/12 2012/13 2013/14 2014/15

Diabetes Registry DR LPR; LPR adoption activities

Medication ManagementMedication

Management SystemDrug Profile ViewerSystemic Treatment Information Program

Identity, Access & Privacy

Client Registry

Provider Registry

User Registry

Consent Directives

Privacy AuditIntegration Services

Regional Integration: cGTA

Common Services Integration

Regional Integration: 9 LHINs

Portal Services

Diabetes Registry provincial roll out Roll out to other chronic diseases

System procurement; Build; Phase 1 roll out

Planning TPA(s) executed; Partner HIAL procurement(s); Build; Roll out

Portlet/gadget development; Establish distribution partnersPhysician eHealth (not subject to MB20 approval)

Ontario Lab Information System

Data Collection

Data Warehousing

Go To Market

Expansion to 20 CHCs

OPIS expansion to 15 additional sites

Support DR LPR Post-DMS LPR deployment

Support DR LPR Post-DMS LPR deployment

Support DR LPR Post-DMS LPR deployment

Solution procurement; Build; Integration; Roll out

DR LPR Connect remaining hospitals/labs

Lab results for DR, EMR, TOH

Enabled for use by DR provincial roll out and secondary sourcesDiagnostic Imaging/PACS

Hospital Repositories

DI Common Service

IHF Repository

Complete 4 of 4 hospital diagnostic imaging repository integrations

System procurement; Build; Provincial roll out

TPA executed; IHF DI-r procurement; Build; Provincial roll out

Consumer Proposition

Current EMR funding program

System procurement; Build; Provincial roll out

Phase 2 roll out

Support DR

Roll out

Planning and policy resolution

Planning

System procurement

Continued roll out

Continued roll out

Continued roll out

Planning

Procurement; Build; Integration

New distribution partners

Planning

Over time, roll out patient self-management; better access to healthcare system; personal health records

Planning and policy resolution

Planning, procurement and execution of OLIS upgrade

The “Why” – Current State Opportunities

10

All nine Hospitals utilize Meditech to some degreeSome sharing of systems between hospitalsFlow of patients between hospitalsMix of several large and small hospitalsFirst Meditech 6.0 implementation in CanadaLow investment in IS/ITComponents of the EMR implemented across the nine hospitals include: 50% fully implemented 9% partially implemented 41% have yet to be implemented Low adoption compared to peers

The “Why” HITSS– Potential Benefits

“Better bang for the buck”

Economies of scale, including access to technologies could not do alone

Leverage experience and “best practices”

Platform for standardization of business and clinical processes Supports “circle of care” – sharing of clinical data

Ability to input and view patient information from anywhere and anytime across CE LHIN hospitals

Integrated view that provides comparison and trending of information across organizations

Critical mass

Integration

Strategically positioned for provincial projects Allows Organizations to focus on core clinical business vs. technology Human resource sustainability

Ability to attract, retain, and recruit strong, knowledgeable IT resources

Increases the depth and expertise

11

Critical Success Factors

Leadership / champions: a passion for step change Compelling case / sense of urgency Scalable, standardized and sustainable solution(s) Strategic map between organizational objectives and future

business strategy Objectives need to transcend cost savings Solid performance and improvement targets People management Experience delivering shared services Capacity to support and sustain adoption / transformation Robust stakeholder engagement process Clinically driven PMO functions Transition funding

12

Finalize report on current assessments

Agree to the gaps

Bring report back to CEEC to define Vision prior to continuing the analysis to determine benefits to the organizations

Next Steps

13