The New Approach to Healthcare Enterprise Information Management

Introduction –

The lack of a healthcare specific, compliant, cost-effective approach to Enterprise Information Management (aka EIM) is the #1 reason integration, data quality, reporting and performance management initiatives fail in healthcare organizations. How can you build a house without plumbing? Conversely, the organizations that successfully deploy the same initiatives point to full Healthcare centric EIM as the Top reason they were successful (February, 2009 – AHA). The cost of EIM can be staggering – preventing many healthcare organizations from leveraging enterprise information when strategically planning for the entire system. If this is prohibitive for large and medium organizations, how are smaller organizations going to be able to leverage technology that can access vital information inside of their own company if cost prevents consideration?

The Basics –

What is Enterprise Information Management?

Enterprise Information Management means the organization has access to 100% of its data, the data can be exchanged between groups/applications/databases, information is verified and cleansed, and a master data management method is applied. Outliers to EIM are data warehouses, such as an EHR data warehouse, Business Intelligence and Performance Management. Here is a roadmap, in layman terminology, that healthcare organizations follow to determine their EIM requirements.

Fact #1: Every healthcare entity, agency, campus or non-profit knows what software it utilizes for its business operations. The applications may be in silos, not accessible by other groups or departments, sometimes within the team that is responsible for it. If information were needed from groups across the enterprise, it has to be requested, in business terminology, of the host group, who would then go to the source of information (the aforementioned software and/or database), retrieve what is needed and submit it to the requestor – hopefully, in a format the requestor can work with (i.e., excel for further analysis as opposed to a document or PDF).

Fact #2: Because business terminology can be different WITHIN an organization, there will be further “translating” required when incorporating information that is gathered from the different software packages. This can be a nightmare. The gathering of information, converting it into a different format, translating it into common business terminology and then preparing it for consumption is a lengthy, expensive process – which takes us to Fact #3.

Fact #3: Consumers of the gathered information (management, analysts, etc) have to change the type of information required – one-off report requests that are continuously revised so they can change their dimensional view (like rotating the rows of a Rubik’s cube to only get one color grouped, then deciding instead of lining up red, they would really like green to be grouped first). In many cases, this will start the gathering process all over again because the original set of information is missing needed data. It also requires the attention of those that understand this information – typically a highly valued Subject Matter Expert from each silo – time-consuming and costly distractions that impact the requestor as well as the information owner’s group.