IT leaders contemplating Master Data Management (MDM) because of their health care organization already understand the significance of having a good MDM strategy. But that does not make the job any less intimidating.
Their concerns for people include”What’s the ideal MDM strategy for the business?” Or,”Can an enterprise data warehouse (EDW) resolve my MDM issues?”
MDM is, really, a subject of frequent discussion together using all our brand newest health programs and potential spouses. Based on these discussions, we have developed a primer on MDM, strategies for coming it, and once an EDW could be the best solution.
What’s Master Data Management?
Our first order of business would be to specify master information. Master information is crucial enterprise information shared amongst multiple methods. In health care, we split master data to two types:
- Identity information –such as individual, provider, and location identifiers
- Reference information –that comprises common linkable language such as ICD, DRG, SNOMED, LOINC, RxNorm, and sequence sets
Master data management is also, at its simplest, the procedure for connecting identity information and reference information over multiple IT systems into one single, constant point of view.
That only point of reference may be a patient, or it might be a process code. A more formal, eclectic definition we provide to MDM is the next:
MDM includes the procedures, government, policies, criteria, and resources that always define and deal with the essential information of a company to supply a single point of view.
Accurately linking both identity and reference information is very vital to get a strong health system IT surroundings. But for our purposes we’ll refer largely to identity information.
Handling identifiers is the base of MDM. If you can not do this well, you will not have the ability to be successful in the intricate job of handling reference information.
Why It Is Important
Three Chief drivers are creating MDM more significant than in the Health Care sector:
- Mergers and Acquisitions (M&A): Both the IT systems of associations included with M&A are seldom exactly the same, and every company has its own enterprise information. Thus, M&A often involves consolidating data from comparable systems (by way of instance, supplier identifiers from 2 separate EMR programs ) to ensure that the information may be used throughout the organization.
- Health data exchanges (HIEs): To successfully market data across organizations and locations, HIEs need to have the ability to recreate master information. By way of instance, an HIE sponsored by a health program will have to make certain its master individual identifiers could be paired with the individual IDs of its affiliated clinics.
- ACOs: To know and manage their individual populations, ACOs bring together health system info and payer info. Bringing these two quite different systems together demands complex MDM to make certain the payer-organization’s master information matches provider-organization grasp information.
In real-world scenarios, there may be a significant little overlap among these 3 classes. By way of instance, that an ACO is typically in an HIE too, along with the ACO’s escrow supplier may be moving through a merger. (It is this degree of sophistication that keeps tech wonks like us in our feet.)
Three Ways for Managing Master Data
The following question that any health care company (ACO or not) should address is the way to handle MDM. Presently, three Chief approaches can be found:
- IT system integration
- Upstream MDM execution
- Downstream master information balancing in an enterprise data warehouse (EDW)
We will go over the advantages and disadvantages of the initial two methods temporarily. Then we will spend some time speaking about if it’s acceptable to utilize an EDW to resolve MDM issues.