About the presentation. Based on Chapter 3 of my book "Healthcare Analytics for Quality and Performance Improvement", this presentation describes the key components of a strategic analytics framework that can enable your healthcare organization to leverage data from source-systems to achieve its quality, safety, and performance improvement goals.
What is an analytics strategy? Analytics is currently a very “trendy” topic. The internet is scattered with many buzzwords, marketing angles, white papers, and opinions on the topic of healthcare analytics. With all this “noise”, it is easy to get distracted from what is actually required, from an analytics perspective, by your organization. An analytics strategy helps cut through the noise and keep focus on what is important for the organization. Regardless of what the latest “buzz” is, your analytics strategy will enable your organization to Invest now for what is required now, and invest later for what is required in the future.
An analytics strategy helps ensure that analytics development and capabilities are in alignment with enterprise quality and performance goals and helps avoids the “all dashboard, no improvement” syndrome. Furthermore, a well formed strategy document helps to achieve optimal use of analytics within a healthcare organization and can mean the difference between a “collection of reports” versus a high-value information resource.
An analytics strategy can rarely stand on its own. In general, the analytics strategy should use as input an organization’s Quality Improvement (QI) strategy and should be used to inform an organization’s Business Intelligence (BI) or Information Technology (IT) strategy. The analytics strategy is an important input to technical strategies because analytics, after all, can involve a sophisticated use of data and technology. Requirements for analytics may trigger a cascade of enhancements throughout other components of IT and BI (i.e., reporting, data storage, ETL, etc)
The document is intended to accompany Chapter 3, “Developing an Analytics Strategy to Drive Change”, so please refer to the chapter for further information about developing an analytics strategy.
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Developing a Strategic Analytics Framework that Drives Healthcare
Transformation
Developing a Strategic Analytics Framework that Drives Healthcare
Transformation
Trevor Strome, MSc, PMP
Blog: http://HealthcareAnalytics.info
Twitter: @tstrome
Presentation Content Based on Chapter 3 of:
Healthcare Analytics for Quality and Performance Improvement
Healthcare Analytics and the Information Value Chain
2
Performance Objectives
Quality Goals
Improvement Approach
Data
Business Processes
Analytics
What DID Happen
What IS Happening
What Will Happen
Decisions & Actions
Outcomes Evaluation
Healthcare analytics is the system of tools, techniques, and people required to consistently and reliably generate the accurate, validated, and trustworthy business and clinical insight needed to take appropriate actions and achieve measurable, desired outcomes.
• Healthcare organizations (HCOs) are facing increasing quality, financial, and regulatory pressures, and must transform to achieve sustainability.
• The three fundamental information needs of healthcare improvement are to identify: – What quality/performance/safety aspects need to improve?– What processes must change to result in improvement?– What change (if any) has occurred?
• Healthcare organizations require better insight into their operations and accountability for their performance.
• Healthcare organizations must allow for creative use of available data and analytic tools to foster decision making – in real time and near the point of care.
• To keep up with pace of change, analytics development needs to adopt an agile approach which values innovation and experimentation.
• A strategy that ensures analytics development and capabilities are in alignment with enterprise quality and performance goals– avoids the “all dashboard, no improvement” syndrome
• Helps to achieve optimal use of analytics– can mean the difference between a “collection of reports” versus
a high-value information resource
• Analytics Strategy should align with other relevant strategies including: – Business Intelligence (BI) strategy– Information Technology (IT) strategy– Quality Improvement (QI) strategy
• Understand requirements– Review strategy components with stakeholders– Identify how analytics are currently used– Determine what capabilities will be needed (short & long term)
• Identify gaps and mitigate risks– List known/potential gaps and their mitigation approaches– Prioritize gap mitigation based on impact, effort, & cost
• Execute plan– Assign task owners and target implementation deadlines– Monitor progress and apply mid-course corrections
Business Context: Enterprise Goals, Objectives, and Strategy
• Goals:– Are what the organization is aiming to achieve. – Define the performance and quality targets of the organization– Answer “why” the organization is (or should be) engaging in
certain activities
• Strategy– Outlines how the organization expects to achieve its goals
• Analytics must provide insight into past, current, and anticipated future progress towards meeting the enterprise goals.
Aligning Strategic and Tactical Quality Objectives
• Analytics is the “glue” which ties strategic objectives and tactical activities together.
• Objectives of unit- or department-based improvement initiatives should, where possible, align with the quality objectives of the organization as a whole.– Prevents misdirected/wasted activity– Enables the HCO to monitor progress and evaluate outcomes
Strategic Level Strategic Objectives
Analytics Metrics Indicators Targets
Tactical Level Tactical Objectives
A reminder that the customer (“the patient”) is the ultimate reason for the work we’re doing.
• Quality Strategy outlines the steps and approach the organization is going to be taking to achieve quality goals/objectives.
• Which QI approaches are utilized (i.e., Lean, Six Sigma) will impact what data is required, how it is analyzed, and how it is communicated.
• Analytics development teams and quality improvement teams must work closely together – to ensure that information requirements of users and the delivery
by via analytics are in sync.
• When executing the analytics strategy, always ask “are we taking appropriate and necessary steps towards achieving the organization’s quality and performance goals?”
• A stakeholder is a person (or group of persons) that are:– impacted by, users of, or otherwise have a concern (or interest
in) the development and deployment of analytical solutions throughout the healthcare organization.
• When developing an analytics strategy, it is important to understand what each of the likely analytics stakeholders will require, and develop approaches to ensure they are getting what they need.
Patient The person whose health an healthcare experience we’re trying to improve with the use of analytics
Sponsor The person who supports and provides financial resources for the development and implementation of the analytics infrastructure
Influencer A person who may not be directly involved in the development or use of analytics, but who holders considerable influence over support of analytics initiatives.
Customer / User A person in the HCO who accesses analytical tools, or uses the output of analytical tools, to support decision making and to drive action.
• A use case is a brief description of how analytics will be used by a stakeholder. Analytics use cases can help to:– identify any gaps in analytics capabilities, and – reduce the likelihood that critical analytics needs will be missed.
• Analytics use cases help identify:– what data elements are most important and what indicators will
be necessary to calculate, and – what types of usability and presentation factors (such as
dashboards, alerts, and mobile access) need to be considered.
• TIP: Develop high-level use cases when outlining the analytics strategy, and drill down in more detail as new analytical applications are designed and built.
• Modern computerized clinical systems (such as electronic medical records) contain dozens if not hundreds of individual data elements. – The potential exists for thousands of possible data items from
which to choose for analytics.
• An analytics strategy must consider:– how to determine which data is necessary for quality and
performance improvement– how the data is managed and its quality assured– how data links back to business processes for necessary
• Business processes provide essential context to the data.
• Most quality improvement methodologies monitor progress and evaluate performance and outcomes using indicators based on process data. – This requires a strong alignment between key business
processes and the data that measures those processes.
• As part of the analytics strategy, you should consider:– if and how current business processes are documented, and – how data items are mapped to these documented business
processes.
• TIP: stacks of Visio charts becomes unmanageable very quickly!
• Big data “describes large volumes of high velocity, complex, and variable data that require advanced techniques and technologies to enable the capture, storage, distribution, management, and analysis of the information.”1
• Big Data represents big opportunity– U.S. health care data alone reached 150 exabytes in 2011. – Big data for U.S. health care will soon reach zettabyte (1021
gigabytes) scale and even yottabytes (1024 gigabytes) not long
after.
24
1. Hartzband, D. D. (2011). Using Ultra-Large Data Sets in Health Care. 2011 Sessions (p. 3). e-healthpolicy.org.
• Web and social media data: Clickstream and interaction data from social media such as Facebook, Twitter, Linkedin, and blogs.
• Machine-to-machine data: Readings from sensors, meters, and other devices.
• Transaction data: Health care claims and other billing records.
• Biometric data: Fingerprints, genetics, handwriting, blood pressure, medical images, retinal scans, and similar types of data.
• Human-generated data: Unstructured and semi-structured data such as electronic medical records (EMRs), physicians’ notes, email, and paper documents.
25
SOURCE: Institute for Health Technology Transformation.
• Using appropriate indicators that align between tactical and strategic levels are necessary. – Tactical-level sub-indicators should align with strategic indicators– Some tactical-level-specific indicators might be necessary for
initiatives that are important at a program, department, or unit level, but don’t directly align with strategic goals.
• Analytical tools must meet the requirements of analysts building analytics solutions/applications, and the end-users who will rely on the resultant information and insight.
• Conduct an inventory of existing analytics tools to determine if:
– Capability is missing that will be required– Existing capability exists that may not be widely known
• Identify viable best-of-breed vendor solutions that meet requirements; custom-build from scratch if necessary or if participating in research.
• PEOPLE are a critical consideration when developing or expanding an analytics capability within a healthcare organization
• Although having the best tools are nice, having the best (and right) people is critical to achieving the goals and objectives of the HCO
• An analytics strategy must consider:– What kinds of people (and the skills they bring) are necessary– The optimal size and composition of the team– Roles and degree of specialization– What gaps in skills exist, and what training is required– How to attract the best analytical talent– How to retain the analytic talent within your HCO– Optimal organizational structure
• Different resource management models exist for analytics teams:– “centralized” analytics office– “distributed” analytics resources– “virtual” center of excellence / competency center (combines
best aspects of centralized and distributed models)
33
Virtual Business Intelligence / Analytics Competency Centre
• Analytics and reporting are the tip of the iceberg in the business intelligence stack.
• The current, near-term, and long-term analytics needs of the HCO must drive how analytics-related technological capabilities are acquired. The exact complement of tools will depend on the overall needs of the HCO.
• The analytics strategy is an important input to IT hardware and infrastructure strategies and planning as hardware and other system upgrades are considered.
• Identify important gaps between current and future state, what the corrective action(s) will be, who owns the actions, and what the due date for corrective actions is.