Master Data Management Chris Belmont Ochsner Health System 1

 Discovered during Analytics Initiative  No single source for people/party information  People can be in multiple roles, hierarchies and functions  Information often changes frequently – (location, phone, title)  Challenges with relationships:  Matrix organization structures – Lawson supports one  Multiple hierarchies – management, project, affiliations  Maintenance across multiple platforms is inconsistent 2 Issue

Master Data Management Master Data Management 3 Many Sources of Party Data Lawson Kronos Retail ID Badges Physicians Patients Active Directory Access Volunteers Fitness Center Contractors Emergency Communications Social Netw. Agency Empl Pictures. Phonebook Asset Mgmt

Platinum Record 4 Construction of the Platinum Record Lawson ID Badges Fitness Ctr Emergency Empl Pictures. Empl ID Manager Cost Ctr Chris Belmont Member # Chris Belmont Badge # Chris Belmont Team A Active Directory Ernest Belmont Corp Pers. Phone # Pers. Location Empl ID Manager Cost Ctr Member # Team A Corp Pers. Phone # Pers. Location Chris Belmont Badge #

 Party – Employees, Physicians, Patients, any Entity  Multiple Hierarchies – management, project, locations  Sophisticated Matching – bulletproof identity  Integration via web services, APIs, SDK  Batch, manual and real-time synchronization 5 Vision

 Create a single source of truth  No system has it all – supplements Lawson LTM (NextGen)  Integration between sources of party information  MDM termination or addition triggers events elsewhere  Employee picture in phone directory, websites, s  Self Service  Employee/Party manages personal data, interests, skills, etc.  Managers manage employee information Ex: work location vs. dept. location  HR manages employee related information  Focused internal communication  True location information  Manage multiple hierarchies including non-employees  Control of contractors, vendors, agency parties  Philanthropy, employee health, 6 MDM Opportunities and Uses

Build relationships manually, derived, automated, self-service  Employees  Disaster Teams, projects, experience  Fitness Center  Patients and Employees  Consultants  Sponsor, Projects, Contracts, Security  Philanthropy  Households, CRM, social networking  Security  Employees, physical security, assets, access  Communication  Interest groups, subscriptions, personal/specific 7 It’s all about relationships….

 Collaboration over control - willingness to centralize, relinquish control and resist creation of new islands of data.  Cleanup of legacy data  Rules – which systems take priority  Common definition of terms and sources  Integration and services to integrate MDM with other applications  Security and privacy  Prioritize vital first uses: Employees, security, phone directory 8 MDM Challenges

 Lawson – Kronos – AD synchronization – done  Integration with help desk and asset management - done  Emergency Personnel List - done (2013 Hurricane Season)  Single phone book – June, 2013  MyWorld – Sharepoint based with social networking  Internal Communications  Enterprise Analytics  Meaningful Use – attestation, registration, etc. 9 Where did we start….

Master Data Management Questions? 10