Question…… what percentage of you at community hospitals have a couple of million dollars laying around for analytics?
To quote Ben Stein, “Anyone…., anyone…..”
Didn’t think so….
Another question….. What percentage of you would like to answer basic questions regarding re-admissions, quality metrics, population health, etc.?
So, how can we get these questions answered within the face of budget constraints?
I would wish to propose one method.
The basic problem….
Most of the questions that cross my way are fairly candid. The complexity arises largely because systems don’t ask one another. Imagine a world where each piece of knowledge was in ONE SYSTEM! How easy would analytics be then! the truth is that we are faced with many systems and sources of knowledge in healthcare and that we don’t have a simple way of accessing the info.
Enter the info Lake
One tool that we use to deal with data gathering may be a Data Lake. I'm often asked how a knowledge Lake and a knowledge Warehouse differ. a knowledge Lake is just a repository where data is stored in its native format. Data Warehouses are defined as data structures that model a business area or need. The higher, more complete the model, the higher the warehouse.
Data Warehouses are at their best once they have an objective. When the business area they affect is fairly well defined. That isn’t the case in modern healthcare. The questions come hot and heavy from all areas…. the info does like-wise.
Data Warehouses are “Pay Now” systems: You pay upfront to define and optimize the structure, normalize and cargo the info.
Data Lakes are “Pay Later”: It’s a relatively straightforward interest “Take what you're given” and put it somewhere.