MDM Architecture

• Assess the current Informatica MDM data models, business rules, match/merge configuration, survivorship, identifiers, relationships, workflows and downstream interfaces.
• Define the target enterprise MDM model for Person/Patient/Provider and reusable patterns for future domains.
• Own the enterprise identifier strategy (person_id / enterprise identifiers), source cross-references and preservation of historical identity relationships.
• Define matching, duplicate detection, confidence thresholds and merge/unmerge/split/rematch behaviour with manual override controls.
• Define survivorship (trust) rules and source precedence, including stewardship override and audit.
• Design relationship lifecycle (provider-location, provider-specialty, patient-PCP, department-PRS).
• Lead Informatica configuration, rationalisation and migration decisions and ensure manual stewardship decisions are preserved.
• Define MDM history, lineage, audit, rollback and downstream synchronisation.

Primary Deliverables

• MDM target model and identity strategy
• Match / merge / survivorship design
• Relationship lifecycle model
• Identifier and source-cross-reference strategy
• Informatica migration / refactoring assessment
• MDM migration and reconciliation specification

10+ years (5+ Informatica MDM), * 10+ years in MDM, with 5+ years hands-on Informatica MDM (Multidomain / MDM Hub).

• Deep identity resolution, match/merge and survivorship (trust) design experience.
• Strong on enterprise identifiers, cross-references and history preservation during migration.
• Provider/person/patient data experience and MDM migration track record.

Good to Have

• Healthcare provider mastering at scale.
• Informatica MDM SaaS / IDMC exposure.

Experience integrating MDM with a semantic layer and governance catalogue.