OSEHRA Summit &PHA Activities

Seong K. Mun, CEOMay 13, 2015

• 400 participants– GOV, Corporate, Academia, International– VA/VHA (40), Indian Health Service, HHS and States

• General Topics– Open Source EHR– Open Source Health IT – m-Health, PHR and others– popHealth® and Population Health Analytics

• Abstract Submissions – more than 75• Strategic Goals for 2015

– Expand Beyond VistA – OS EHR’s, HIT and Analytics– Orient the Community on the Best Practice of OS

• Software – Governance - Community

OSEHRA Summit Scope

• Day 1: OS Best Practice– Non-VistA Open Source Community Activities– Roundtables and VistA Related Activities– Workgroup Reports– Cooperate Member Annual Meeting– Submitted Papers including PHA Submissions (4)

• Day 2: Big Pictures– Three Plenary Sessions

• Innovations, VA and Population Health Analytics

– Award Session– Submitted Papers– Summit Reception and Posters

• Day 3 – Community in Action – Town Hall(s)– VistA Town Hall Meeting Track– OS and Health IT submitted Papers- Two Tracks– popHealth® and Population Health Analytics Track

Three Day Agenda

• Goal– Build a high performance community in population health

analytics

• Objective– Introduction to OSEHRA Community and vise versa – Develop a community-based roadmap

• Task– Orientation on how OS Community operates– OSEHRA governance in action– Organize the first face-to-face PHA community meeting– Emergence of an open source community on Analytics

Planning Strategy for PHA Community

• Three Sessions on Friday• 8:30 am – 10:15 am• 10:30 am – 12:00 noon• 1:15 pm – 3:00 pm

• Question:• How do you want to use the time block?

Addional Planning

Fred PriorMay 13, 2015

OSEHRAPopulation Health Analytics

Roadmap

A type of strategic plan that outlines activities an organisation can undertake over specified time frames to achieve stated goals and outcomes.

Roadmap

7

Roadmap Development

Key Elements of a Successful Roadmap

Goals

Milestones

Gaps & Barriers

Action Items

Priorities & Timelines

8

• Convened stakeholders– Analytics User Group Meetings / popHealth

Steering Committee

• Gathered visions/use cases– From 5 state organizations

Where are we in the process?

9

Functionality in Common

10

Goals Functionality Subfunction

Allow provider-level analysis of Clinical Quality Measures Provide a tool for user managed provider hierarchies: Organize providers into teams or groups

Organize multiple teamsReporting at every level of the hierarchy

Provide quality performance monitoring; Comparison to Peer Group Aggregate data

Allow comparison of multiple providers; Ability to compare a provider to the aggregate/cohortAllow comparison across groups of providers; Comparison to Peer Group Aggregate dataProvide the ability to identify ‘best’ performers and ‘under’ performers

Actionable reporting with drill down ability to provider and patient-level data; produce actionable reporting with drill down to patient and providers

Centralized popHealth implementation for FQHCsCentralized repository of clinical data that can be used for multiple purposesAbility to integrate additional measures develop once and use for all FQHCs; popHealth measure creation tool in support of other federal initiatives (PCMH, UDS)Prepare FQHCs for interoperability by using CCDA standardTrack trends in quality and health over time

Provide clinical analytics tools to support low resource clinics efforts to improve quality of care and meet Meaningful UseProvide data / reports to support the use of data at the clinic levelFacilitate the use of data for community/clinical linkages in support of population health improvement

Functionality in Common

11

Goals Functionality Subfunction

Expand use of popHealth to other areaspopHealth as a service to support CQM reporting; Business Services offering to Stakeholders/Healthcare partners.Creation of QRDA cat 3 as part of analytic toolsContinued CQM reporting at clinic, provider, and patient level with customizable reporting periods

More control of MU Stage II Attestation Measure Submissions.Refine and Improve the EP attestation workflow. (Ease of Use) (This is a non-functional requirement)Utilize popHealth to aggregate statewide clinical quality data Onboarding/testing of EHRs for submission of QRDAsMake PopHealth more useful for provider practices.

Get the data out of PopHealth, with push to our Texas HIEs the priority.

Modify SLR and PopHealth to be able to exchange CQMsEnterprise Level Analytics.Targeted CQM point-to-point EHR Data Collection.Fast Interoperable Healthcare Resource ("FIHR") and Public Application program Interfaces (API) Possibilities.Open Source Application Alternatives.

• Review the goals and use cases• Identify critical milestones

– Needs of the community– Drivers from emerging regulations and

dependencies

• Conduct gap analysis– What functionality needs to be added

• Develop priorities with timeline

What’s Next?

12

How will Tacoma Impact Our Roadmap?

• Cypress version 2.6, a testing and certification tool for electronic clinical quality measures, was released on January 22, 2015.– Cypress V2.6 Measure Bundle includes updated patients.

Measure Bundle v2.6 will be the only option available to the Cypress user for testing.

– Cypress V2.7 is targeted for Summer 2015

• Quality Data Model specification, version 4.1.2 was released on January 14, 2015. Support for the 4.1.2 changes were made in the Measure Authoring Tool (MAT) v4.1.0.

Known Dependencies

14

• A timeline of planned releases• Each release will have a package of

required functionality• Key actions and staffing identified for

at least the first release

What will the Roadmap Look Like?

15

Release 1Feature 1

...Feature m

Release 2Release N