A Recipe for Analytics, Key Ingredient #2 – Infrastructure
This 4-part blog series focuses on building a successful analytics strategy with each of these 4 ingredients.
- Very liberal amount of Data Content
- Proportional dose of Infrastructure
- Quart of Data Governance
- Several stalks of Analytics Competency
Every good pie has a great filling with just the right texture, but supporting that pie from all sides, providing a solid foundation, is the crust. Think of your organization’s analytics infrastructure as the pie crust that provides packaging for analytics to be consumed and enjoyed.
Key Ingredient #2: Infrastructure
Technology is needed to support analytics. Infrastructure is a place to store big data, exchange insights, and integrate analytical solutions into business, clinical, financial and operational processes.
The good news is you don’t have to have sophisticated, expensive infrastructure to do great analytics. Any healthcare organization can start their analytics journey with simple tools and focus on collecting data into a centralized point where it can be shared and leveraged to improve patient care. A simple spreadsheet with pivot tables can be extremely powerful. Analytics maturity is not about more technology, it is about using data effectively to cook up data driven insights and serve up those “aha!” moments that improve patient care.
The HIMSS Analytics Adoption Model for Analytics Maturity (AMAM) provides a roadmap to help healthcare organizations advance their analytics journey. One of the model’s focus areas is infrastructure. AMAM helps organizations focus their infrastructure decisions strategically and with purpose to maximize intelligence learned from data.
The lower AMAM Stage “infrastructure ingredients” are the foundation for collecting data into a centralized shared repository. This allows all types of “cooks” (analysts) across the organization to effectively gain access to, build an understanding of, and leverage data.
Higher level AMAM Stage infrastructure requirements are designed to turn up the heat on data availability and analytics cooking times. By requiring clear identification of “systems of record” (the systems that data originates from) and tighter timeliness of delivery, organizations can cook up more and better flavors of embedded analytics solutions. Stage by Stage improvements of infrastructure are represented by these key ingredients:
Stage 0: Fragmented point solutions
Stage 1: Historical data, metadata, centralized operational data store
Stage 2: Centralized formal repository, enterprise-wide ad-hoc & reporting
Stage 3: Broadly accessed reporting solution, database schema in place
Stage 4: Widely accessible analytics driven dashboards track KPI’s
Stage 5: Updates from system of record in < 2 weeks
Stage 6: Updates from system of record in < 1 week
Stage 7: Updates from system of record in < 24 hours
The AMAM data requirements for each Stage are designed as a roadmap to help healthcare providers assimilate a solid infrastructure foundation that enables a wide variety of clinical, operational, and financial analytics insights (recipes).
Other key ingredients in the analytic recipe are fresh data, advanced analytical skills, and aligned data governance. We will provide an overview of those in the remaining parts of this 4-part blog series.
This post is part of a multipart series on healthcare analytics. Read Part 1 here and continue to follow HIMSS Analytics for more on this topic.
If you have questions about AMAM or healthcare analytics please reach out to our client relations team and read more here.