Data Warehouse / EDW

Hadoop in Healthcare: Getting More from Analytics (White Paper)

Healthcare data is positioned for momentous growth as it approaches the parameters of big data. While more data can translate into more informed medical decisions, our ability to leverage this mounting knowledge is only as strong as our data strategy. Hadoop offers the capacity and versatility to meet growing data demands and turn information into actionable insight.

Specific use cases where Hadoop adds value data strategy include:

  1. Archiving
  2. Streaming
  3. Machine learning

Comparing the Three Major Approaches to Healthcare Data Warehousing: A Deep Dive Review (White Paper)

The task to improve healthcare presents a significant challenge to providers, health systems, and payers. But according to the Institute for Healthcare Improvement, if health systems focus on achieving the objectives of the Triple Aim, they will be able to meet the ongoing government mandates to improve care. A key component for meeting the Triple Aim will require the ability to overcome the current data warehouse challenges the healthcare industry faces. Because of constantly changing business rules and definitions, health systems need to choose a data warehouse that’s able to bind volatile and nonvolatile data at different stages rather than the early binding approach that’s inherent with traditional data warehouses. The best type of healthcare data warehouse should offer a late-binding approach, which will provide the following critical characteristics: data modeling flexibility, data flexibility, a record of changes saved, an iterative approach, and granular security.

Database vs. Data Warehouse: A Comparative Review

What are the differences between a database and a data warehouse? A database is any collection of data organized for storage, accessibility, and retrieval. A data warehouse is a type of database the integrates copies of transaction data from disparate source systems and provisions them for analytical use. The important distinction is that data warehouses are designed to handle analytics required for improving quality and costs in the new healthcare environment. A transactional database, like an EHR, doesn’t lend itself to analytics.

Getting the Best Business-Intelligence Solution for Healthcare (Executive Report)

In today’s reality, healthcare is more dependent than ever upon business intelligence to survive and ultimately thrive. Get a review of the available solutions, a summary of what each does as well as the pros and cons. Also discover how a Late-Binding™ data warehouse stacks up against other solutions in its ability to aggregate data and make it accessible and foster a truly data-driven culture.

Build vs. Buy a Healthcare Enterprise Data Warehouse: Which is Best for You? (Executive Report)

Chances are, if you are reading this blog, you have heard some flavor of the “build vs. buy” question in the context of data warehousing. For example, here are two conflicting ways that I’ve personally heard this question posed:

“Do we need to buy [a data warehouse], or can we build it?”
“Are there any vendors we can buy this from, or will we have to build this?”

As you can imagine, both approaches resonate differently with different people, cultures, and strategies, and the same basic questions sound very different depending on who is asking it.

The Late-Binding Data Warehouse Explained (white paper)

You have options when it comes to data warehouses – but which one is right for your healthcare organization? Discover the difference of the Late-Binding (TM) data warehouse architecture. And see why this unique system offers quick time-to-value and the agility necessary to meet the changing demands of the healthcare industry.

6 Reasons Why Healthcare Data Warehouses Fail (Executive Report)

It’s no secret that the failure rate of data warehouses across all industries is high – Gartner once estimated as many as 50 percent of data warehouse projects would have only limited acceptance or fail entirely. So what makes the difference between a healthcare data warehouse project that fails and one that succeeds? As a former co-founder of HDWA, Steve details six common reasons: 1) a solid business imperative is missing, 2) executive sponsorship and engagement is weak or non-existent., 3) frontline healthcare information users are not involved from start to finish, 4) boil-the-ocean syndrome takes over, 5) the ideal trumps reality, and 6) worrying about getting governance “perfect” immobilizes the project.