Healthcare Providers Evolving Their Use of MDM

Having spoken with a number of healthcare providers at recent events including the Gartner MDM Summit, Informatica’s own MDM workshops and a variety of other meetings, I’ve noticed their use of MDM is evolving as of late.  It’s clear that within the provider community, MDM is quickly maturing beyond a single virtual view of the patient using an Enterprise Master Patient Index (EMPI). 

To give you a bit of detail about what I mean, I’ve highlighted a few recent examples of changing MDM usage in the industry extending beyond traditional EMPI.  I’ve also included a few links to some related information, if you’re interested in learning more:

  • Domain Expansion:  MDM requirements to gain control of patient data, fueling initiatives like patient-centricity, haven’t subsided.  On the contrary, efforts are expanding to include the management and analysis of other related domains.  Providers are now commonly identifying provider, location, employee and service domains in addition to patient, as critical to attaining business objectives.   

With this information, healthcare execs are gaining new insight into the internal operations of individual facilities and entire health systems, exposing the best-practices of the most sought-after physicians to enhance quality, and uncovering the insight needed replicate the efficiencies of the most effective care teams to reduce cost.

Ochsner Health System is one such leader expanding the scope of MDM traditional healthcare domains.

  • Relationship Analytics:  Today’s industry pressures are forcing many healthcare organizations to pursue aggressive improvements in their ability to increase patient populations, enhance quality under cost constraint, and respond more quickly to upcoming regulatory requirements.  As healthcare executives attempt to understand and improve their businesses to that end, they are demanding trustworthy information and analysis, which relies on relationships between patients, geographic proximity to the practice locations they visit, their preferred specialists and a host of additional insight.

Not only does this use-case require a full spectrum of domains as described above, but even more importantly necessitates the management of complex relationships between these entities.  Once obtained within MDM, providers are leveraging authoritative master information to generate new relationship insight needed to achieve revenue, cost, quality and service goals.   

For more information on MDM in Relationship Analytics check out an upcoming webinar 

  • Reference Data:   Reference data, or that data used to categorize other information within and outside of the enterprise, has been surfacing lately within the healthcare industry as another popular use case for MDM.  Reference data can most readily be seen in areas such as pharmaceuticals – managing name brand drugs, generic substitutes and the mapping between them – but a variety of reference MDM examples are sprouting out of the industry. 

Managing test data, such as a tissue test and rules for subsequent required tests based on initial results, has appeared as another use of MDM.  Finally, recent regulatory pressures including the transition of diagnosis codes from ICD-9 to ICD-10, have highlighted yet another opportunity to introduce trustworthy reference data MDM to the healthcare enterprise. 

To understand more about the use of MDM and ICD-10, check out the Blue Cross Blue Shield of Michigan success story.

It’s exciting to see this evolution of MDM technology within industry.  It may signify stronger IT/Business partnerships, or may be a function of the tumultuous regulatory and market landscape.  Either way the new paradigm has certainly taken hold.  

If you have other examples of providers using MDM in innovative ways, please leave a comment or send me an email! 

This entry was posted in Healthcare, Master Data Management, Vertical and tagged , , . Bookmark the permalink.

3 Responses to Healthcare Providers Evolving Their Use of MDM

  1. Pingback: The Changing Use of MDM in Health Care | Data Daily | DATAVERSITY

  2. I am in my first year of a Doctoral programme DHA, I have a theory about implementations of EMR, and EHR. After 25 years of data constructs, integration in most businee verticals, hospitals data, in my reseach tells me that the healthcare industry is facing a $500 billion build out across every type practice. The silo data within each hospital is a tremendous burden , but with efficient gains the industry is waking up to, regardless of The Health Care act, data inside hospitals needs strong data leadership to clean up data that is scattered across different applications and platforms. If implementating a EMR, just hanging the application out there and going though integration, you still have bad data.
    Creating an initative , Data Management Initiative (DMI) well before the implementation of the EMR, is a change in direction for hospitals, hospitals today must operate like a business model, cash flow, operations, LIS (lab info systems) that retrieve monies from CMS that is normally lost for most lab work. Even the hospital I see, has an EPIC and EHR running, why? Might be because of lack of documentation or the data isn’t really that nice, and clean.

  3. Jeff Scheepers says:

    Thank you for the comment – you make an excellent point. EHRs/EMRs depend on trustworthy master data about patients, physicians, facilities and other important entities. These applications themselves don’t actually improve the quality of the data (nor do these applications maintain data consistency outside of the application). It would certainly be prudent for an organization pursing this implementation to take a broad snapshot of their data, and take measures to address inconsistency, before embarking on such an important initiative.


Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>