MDM in the Context of Data

Governance for Healthcare

Management

Speaker bio: Tina McCoppin

Partner at Ajilitee
Former Engagement & Project Manager for Fortune 1000
companies: HP, Knightsbridge, Forte, Seer, Pansophic, Accenture
Focus on: BI, data integration, data governance, BI/DW, MDM
Data governance strategist

Content
Case Study: A clients data challenge
Business drivers of DG and MDM initiative
Approach and timeline
Data governance
Tool selection: MDM, Metadata, 3rd Party DQ & Enrichment Vendor (by
data domain)
MDM pilot
MDM implementation (in progress)
Outcomes and looking forward

Wheres the cat?

Sure we are collecting our data. But finding the right data when you need it can
be challenging.
4

The Need for Data Governance and MDM

That isto bring control and order to our data

The Information Challenge we faced

Marketing

Sales

Compliance

Customer
Service

Incorrect
Contact Info
Hospitals

Physicians

Jbraverman@email
.com

Medicaid

Medicare

Provider Data
Management

No View of
Consumer

Kate Smith
Medicare B

PPO/HMO

Joseph Braverman,
M.D.

Portals

Pended
Claims

Katlyn Smith
452 2nd St
Newark, NJ-07105
PPO 20/150/40

Consumerism &
Health Exchanges

Data
Governance

Dental
Ancillaries

Kate Smith
450 Second Street
HMO

Medical
Claims

Dr. Joe Braverman

Medicare
Advantage

Dental

Medicaid

We need to be able to synthesize & govern data across silos & sources
7

Data Governance
Data Governance is a management function with direct accountability which
establishes and enforces a set of processes to help manage data as an asset

Revolves around People, Processes and Technology for governance of data

Key discipline areas for Data Governance include:
Steering Committee
Defines and champions the strategy. Sets direction and high-level priorities.
Conveys the EIM strategy to the community
Data Governance Council
Establishes the roadmap, prioritization and schedule. Communicates standards
for Stewardship and hold stewards accountable
Data Stewards
Provides data ownership, defines how data is used and defines enterprise
metrics
Successful DG programs have responsibility and trusteeship
vested in the lines of business

Master Data Management (MDM)

Master Data Management (MDM) is the practice of cleansing, rationalizing
and integrating data into an enterprise-wide system of record for core
business activities
Business information problems MDM tries to solve include:

Data duplication
Lack of standardization
Process disharmony
Difficulty in integrating similar data
from disparate sources
load
govern

Source A
Data
Stewards govern

publish

govern

publish

load

Source B

Data
Warehouse

Master Data
Registry Hub

Global
Financials

Master Data in Context: Medical Claim Form

Transactions pull together
the different types of data:
Master
Control/Reference
Transactional (values)

Patient name,
address, phone

Relationship

Insured name,
address, phone
State
Birthdate

Gender

CONTROL / REFERENCE DATA

Generally controlled through
Approved Lists of Values (LOVs)
TRANSACTIONAL DATA
(How many, how fast,
how much)

DX

INFERRED through the Master Data

Provider Type
Provider Specialty

Where

MASTER DATA
(Who, what, where)

CPT

ChargesUnits

TIN

Billing
provider
10
10

DG & MDM Developing a Common Language

Understanding syntax, processes, and purpose across all business functions
provides a framework for establishing a common language
Marketing

Customer
Service

Operations &
Service

What is a
Product?

Syntax

What is a
member?

What are the

key business
processes?
What data are
collected to
support the
business
processes?

Process

Purpose

What purpose
does the data
serve?

How are they

used?

Semantic modeling defines the business context of the data across all business
areas, functions, & processes
11

Content
Case Study: A clients data challenge
Business drivers of DG and MDM initiative
Approach and timeline
Data governance
Tool selection: MDM, Metadata, 3rd Party DQ & Enrichment Vendor (by
data domain)
MDM pilot
MDM implementation (in progress)
Outcomes and looking forward

12

DG and MDM: No Respect?

On a team comprised of Business stewards , subject matter experts, IT Data

Governance and MDM architects, designers and developers --

establishing a program which

is influential and impactful is a
challenge
How does a program become
successful?
13

Scenario
Healthcare Organization which started DG and MDM from scratch
Terminology:
Payer the ones who process the claim and reimburse (and charge) you,
reimburse the doctor, the State
Provider more then doctor. Can be an individual physician or dentist, a
group of physicians, a hospital, a lab, a clinic, etc.
Member subscriber (the one who is primary for coverage), dependents
(spouses, children) and all the accompanying rigmarole such as
Enrollment, Group Plans, Products offered, Benefits covered, etc.

14

Provider and Member DG/MDM Value Proposition

Unified view of Provider and Member Data across enterprise applications and lines of
business, improving collaboration and quality of care and reducing costs
Provider Types
Physicians
Groups
Hospitals
Diagnostics & Labs
Durable Medical
Dental & Vision
Retail Health Clinics
Delegates

Contracting

Demographics
Subscribers

Networks
Capitation

Preferences

Patients

Contacts

Provider Profile

Segmentation

Member Profile

Member & Provider

Collaboration
Claims
Reimbursements
Authorizations
Referrals
Customer service
Network management
Case Management
Care Management
Pricing
Portals
Marketing
Segmentation
CRM Strategy
Service & Billing
ACO

Enabling a unified, consistent, accurate, and timely view of Master Data

15

The MDM Value Proposition

Data Fragmentation

Data Duplication

Problem: As with all data, Master data quality deteriorates over time
MDM: Pre-cleanse and standardize data (e.g., gender)

Single Source of Truth

Problem: Same Master data attributes exist in multiple systems, leading to data
divergence (DOB: System A = 6/1/80, System B = 1/6/80)
MDM: Pick best value, based on trust scores

Data Quality

Problem: Master data is fragmented across multiple systems vertically & horizontally
MDM: Bring together data from multiple systems and build whole records and data
sets using match & merge

Problem: Multiple systems have slices of truth with inconsistent data quality and
standardization
MDM: Bring together and present single source of truth for consumption by users
and systems

Bridging the Gap

Problem: Vertical systems dont bridge well across Members, Providers, Products,
Customers, Employees, etc.
MDM: Provide visibility across multiple data domains (e.g., providers that are also
16
members)

Additional Benefits

Standardize data services

Retire obsolete components from infrastructure

Reduce the cost of maintenance

Reduce data inconsistencies across systems and improve business and IT
operational efficiencies
Increase agility with faster time to implement new business functionality

Enable portals and self-service administration

Deliver consistent information to members and providers across channels

Decouple and insulate downstream systems from changes to upstream
systems

Implement necessary workflows to authorize changes

Improve operational efficiency, customer satisfaction and regulatory
compliance

Enable reporting and analytics

Unified view of providers and members across all plans, lines of business and
market segments
17

Content
Case Study: A clients data challenge
Business drivers of DG and MDM initiative
Approach and timeline
Data governance
Tool selection: MDM, Metadata, 3rd Party DQ & Enrichment Vendor (by
data domain)
MDM pilot
Outcomes and looking forward

18

How We Phased the Implementation

One subject area at a time for Data Governance and Stewardship

Definitions, identifiers, valid reference values
Provider: Individuals, groups and organizations, provider types
Member: Subscribers, dependents and patients

MDM Tools Selection

Determine needs and MDM style (Integration, Registry, Hub)
Single-domain versus multi-domain

MDM Pilot
Focus on how the Business uses provider data
Engage Data Stewards to prototype match/merge and trust rules

MDM Lab
Focus on new functionality and product upgrades to be tested
Simulate Production-like environment before starting development (Adopt
Lessons Learned mentality)

Initial Rollout Provider Directories, Member and Provider portals and

communications
Individuals, groups, organizations
Service and billing locations
Provider and Member email and contacts
19

Data Governance Approach for a Subject Area

Communicate With Stakeholders
Preparation

Discovery

Analysis

Synthesis

Recommendations

Collaborative Effort Between Business and IT

Preparation preliminary steps to identify key participants, key data elements &
sources, and individuals to be interviewed; intent is to socialize operating
model with key stakeholders; define scope and approach
Discovery gain understanding of the data and processes in the current
environment, introduce Data Governance concepts, best practices and rollout of Data Governance program
Analysis pinpoint and clarify key data touch points, data handling processes, issues
and work-arounds; bridge from discovery to synthesis , with focus on clearly
defining the current environment
Synthesis/Recommendation generate informed recommendations based on
discovery and analysis. Tailor and define the near & future state policies and
procedures, including gaps and potential remediations
20

How Did We Triage Data Policies and Issues? The Data Governance Process
Populate:
Enterprise Metadata Manager
Root Cause Analysis
Enterprise Data Issue Log

Review and update:

If needed:
Create

Impact Analysis
Impact Assessment

Enterprise Data Issue Log

Decision Matrix
Root Cause Analysis

3
DG Governor

5
Review

Data Stewards
Stakeholders
Solution Architects

Request
Requestor
(Stakeholder, PM)

Data Steward

1. Steward or Stakeholder(s) discovers

and logs an issue.
2. Steward completes (or delegates) root
cause analysis.
3. Steward sends prioritized issue log
and root cause analysis to DG Core
Team.
4. Stakeholders review data quality
issue, gauge potential system impact
(if any) and advise Steward of same.
5. DG Core Team acts as escalation point.
6. DG Core Team sends recommended
action list to Steward.
7. DG Core Team posts decisions to
Sharepoint.
8. Steward communicates
recommendations to Stakeholders for
implementation.

6
Provide Input
DG Core Team
Data Profiling
Requirements
Logs
Data Stewards
Subject Matter Experts
IT Custodians
Stakeholders
Project Teams
Solution Architects

Escalate

DG Council
Review and update:

21

Post to
Sharepoint

Approve

Approve

Notify

Enterprise Data Issue Log

Decision Matrix
Impact Assessment

Stakeholders

Enterprise Data Model: Single-Domain versus

Multi-Domain
Multi-domain solutions versus Single-domain

We chose to leverage and reuse a single tool to master Provider, Member, and reference
data
Eliminates cost of buying multiple tools and creating competencies around multiple,
domain-specific tools /apps

Multiple MDM instances versus Single MDM instance

We chose to integrate provider and member master using a party
model that aligns with the enterprise data model we are designing

Key value of having a single instance is the ability to identify

and manage relationships
Physicians <-> Patients <-> Members <-> Employer Groups

22

MDM Implementation Time Lines

Activity

Q3 FY11

Q1 FY12 Q2 FY12

Oct 11 Nov 11 Dec 11 Jan 12 Feb 12 Mar 12 Apr 12 May 12 Jun 12

Data Analysis
Requirements
Design
Development
SIT Testing
UAT Testing
Production
Completed

In progress

Scheduled

Validate the capabilities of MDM solution for 2 domains, 6 data sources and systems
Data Integration: Integrate Provider and Member data from multiple sources
Data Quality Improvement: Enrichment Data using Third Party data providers
Data Governance: Generated workflows to support data stewardship
Consolidated outputs: Produce data extracts to demonstrate full lifecycle MDM
value
23

MDM Tool Selection Evaluation Criteria

MDM Evaluation Activities
Written questions
Demonstrations
Technical deep-dive sessions
Use case run-throughs

Total cost of ownership

MDM Business Value Categories

MDM Technical Value Categories

Third party data service integration

Extensible data models

Data Stewardship support

Integration with enterprise applications

Workflow and rules

Change and release management support

Multi-domain and Payer data models

Pre-canned web services

Match/merge technology

Supports common MDM styles

Training and professional services

Integration with infrastructure services

Total cost of ownership

Integration with BPM tools

Health plans customer success

24

MDM Data Architecture

-Common Record
Format
-Ready to load data

Balance & Control

-Temporary
MDM land area

-Temporary
MDM stage area

Error Handling
25

-Apply
Distribution Rules

Interface Hub

-Straight Move

Base

-Apply Trust Rules

-Business
Standardization
-Match
-Merge / Unmerge

-Address Cleanse

Staging

Extract
-RAW Data
-ASCII Delta

Master Data
Services

MDM Processing

Landing

-Structural Transform
-Cleanse
External Lookup
-Address Validation
-Technical Standardization

Data Sources

-Extract Validation
-Change Capture
-Convert to ASCII

MDM Preprocessing

Pre-landing

Source

-Mastered Data

-Ready to publish
data in consumer
format

Audit & Logging

MDM Data Architecture Extract Layer

Purpose:
Extract layer is expected to perform data extraction, delta detection and
conversion to ASCII format if needed
Also provide ability to meet:
Audit & Traceability
Recoverability and Reload
Decision Points
Extract Format (Files v Relational, etc.)
Extraction / Delta detection Method
Assumptions
All data to be sourced in file format. File could be a full snapshot or
incremental. File format could be flat, XML, Mainframe
Batch-only mode for all sources with lowest refresh rate of once per day
Delta detection can be performed at source or in MDM pre-processing
region depending on the source

26

Third Party Data Selection Criteria: for DQ and Enrichment

Criteria

Evaluation Questions

Cost

What is the pricing model (Geography, Type, Frequency, etc)? What are the contract lengths and terms?
What are the costs for the offered menu of data and/or services?

Data Coverage

What is the provider or member match rate? What data elements are offered?

Data Model Fit

How well does the vendors data model map to the use cases and Data Model?

Data Quality Lift

What quality improvements and enhancements have been measured?

Data Sourcing

Which data elements are sourced a) by the vendor b) from public sources c) from third parties?

Metadata & trust

rules

What metadata is provided for defining trust and usage rules?

Reporting/analytics

What analysis does the vendor provides around the data?

Data Security

The vendor must completed a Vendor Information Security Risk Assessment Survey. IT Security and Legal
approval are required before sample data can be sent to the vendor.

Batch Data
Publishing

Details around a unidirectional vendor to companys data feed for specific states.

Batch Data Matching

Details around providing a bidirectional data feed with a data service to match and append upplied data.

Online Lookup

Details around vendor offered portal, web site or application so that company staff can perform ad-hoc
lookups.

Real-time Web
Service

Details around vendor offered real-time web services that can be integrated with companys MDM solution.

27

MDM Pilot Results

Data profiling analysis of Provider and Member data sources

Preliminary match/merge and trust rules
Performance metrics
Master Data metrics (Totals, # Golden Records, # Overlaps)
Counting noses and belly-buttons
Individual Providers and Members
Individual intersections
Members who are also Providers
Dependents who are also Subscribers
Postal and email addresses
Refined trust rules based on analysis of results
Cases requiring data steward decisions

28

Content
Case Study: A clients data challenge
Business drivers of DG and MDM initiative
Approach and timeline
Data governance
Tool selection: MDM, Metadata, 3rd Party DQ & Enrichment Vendor (by
data domain)
MDM pilot
MDM implementation (in progress)
Outcomes and looking forward

29

Multi-Domain MDM Hub as a Solution

Compliance

Marketing

Sales

Customer
Service

Consumerism &
Health Exchanges

Enterprise Master Data Hub

Internal
Sources
Provider

Third
Party Data

Customer

Employee

Member

Joseph Braverman, M.D.

[email protected]

Portals

Provider Data
Management

Medical Claims

Broker

Kate Smith
452 Second
Street,
Newark, NJ-07105

Medicare
Advantage

Product

Pri: Medicare B
Sec: PPO 20/150/40

Dental

Disparate data reliably resolved

30

ICD-10

Medicaid

Data
Governance

Future State MDM Solution

Stewardship Process

Distribution Request
New/changed Master Data Request
Quality Improvement Initiative
Operations&Quality Monitoring

Workflow Services

Metadata

Review and Correction

Approval and Publishing
Exception escalation

Metadata shopping
Impact analysis
Operations Monitoring
Quality Investigations
Master Data Management

AIM Governance &Stewardship

Acquisition & Authoring

Real-time/Near
Batch
Change Capture

Workflow Services

Suppliers

Suppliers

Authoritative Sources
End-user Authoring

Metadata Services
Master Data
Management
Services
Data Quality Services
Administration
Services

Data Quality

Validation
Audit, balance & control
Quality Tracking

Distribution Services

Acquisition & Authoring Services

Maintenance
Services

Administration and Maintenance

Change management
Security management
Operational support
Process monitoring
Performance management

31

Historical Data Management

Storage services
Schema services
Mapping/alignment Services
Hierarchy Management

Consumers

Distribution

Self-service (pull) interface

Publishing (push) interface
Messaging-oriented interface

Enabling the Consumer 360 Using MDM

Integrating customer related data from internal and external sources is a key enabler with MDM
Consumer 3600 View - Data Elements
Member Information

Products & Benefits

Data

Data

Basic
Preferences
Extended
Prospect/Lead
Broker
Health Risk
PHR
Provider, PCP
Alternate Programs (e.g., ACO, etc.)
COB & other Ins.

Product
Benefit
Renewal
Ancillary Product
Wellness & Disease
HSA/FSA/HRA

Interactions

Transactions

Interaction Data

Interaction Data

Service Requests
Messages
Care Messages
Correspondence
Payment
Member Provider Interactions

32

Claims
Pre-Cert & Pre Authorizations
Care Management
Appeals & Grievances
Billing
Delegate Partner Data
EOB

Lastly: Big expectations for Data Stewards

DATA
QUALITY

DW, BI AND
DATA INTEGRATION

BUSINESS
KNOWLEDGE &
EXPERIENCE

OPERATIONAL SYSTEM
RESPONSIBILITIES

PERSONAL
TRAITS

Persuasion / Negotiation
Reputation / acknowledgement
Facilitation 33

One DG/MDM Program does not fit all!

Assess your own organization: key is deciding which governance
functions will be included

Different mix for each institution

Mix will define protect and manage data as a corporate asset
Do not over commingle responsibilities
Prioritize the implementation of the functions
Determine implementation sequence

Important functions to make sure are covered:

Data quality / certification

Data ownership / stewardship
Meta, reference and master data

Important stewardship growth must include:

Subject matter expertise in data domain(s)

Subject matter expertise in data management best practices
Tools & technologies competencies
Leadership competency
34

Final Lesson! -- DG + MDM

A cohesive team to accomplish great things!

35

Suggested Reading and Connecting

DAMA
TDWI
Data Governance & Information Quality (DGIQ) conference debtechint.com. Has
a DG conference twice a year in San Diego (June) and Ft. Lauderdale (Dec)
Datagovernance.com
Dataversity offer DG-related webinars
Join some LinkedIn DG Groups (search on data governance and/or MDM)
Look at the websites of vendors who have tools in ETL, DB, metadata, data
modeling, etc. (p.s. Ajilitee.com has some white papers and presentations
available too)

Lots of good white papers

Look for articles, papers, etc. from key DG and DQ speakers: David Loshin, Danette
McGilvray, John Ladley, David Plotkin, Aaron Zornes, Daragh OBrien (great stuff on
IQM), et al

36

Questions ?

37

Thank you
TINA MCCOPPIN
PARTNER AND FOUNDER, Ajilitee
[email protected]
847.840.0858
www.linkedin.com/company/ajilitee
www.facebook.com/ajilitee
www.ajilitee.com

38