Whitepaper · Healthcare Providers · Informatica Customer 360
Patient EMPI and provider masters that credentialing can trust.
Enterprise patient identity, physician and clinician masters for credentialing and directories, referral sources, payers and supply items.
01 · Executive summary
The short version
- PDI delivers 21 healthcare providers use cases on Informatica Customer 360 with its accelerators. The use cases are drawn from 7 anonymized account profiles.
- Each use case arrives pre-mapped: the 15 entities it can land on, the 9 source-system families it draws from, and the match and data-quality rules for those entities.
- Design decisions are captured in adaptive-card workshops: 132 cards across 10 data-model workshops, so every answer becomes a configuration input.
- The entry point is a $50,000 fixed-fee MDM implementation for any two source systems. Informatica licensing is procured separately.
02 · The master-data problem
Where the records disagree.
Health systems carry two identity problems at once. Patients arrive through many registration points and need one enterprise identity. Clinicians need one record across credentialing, payer enrollment, scheduling and the public directory.
Provider, referral-source and supply-item masters land on Customer 360 for Healthcare. Patient EMPI use cases are configured on the Person and Member model and sourced from EHR and FHIR interfaces.
03 · What is prepackaged for this industry
The accelerator, before day one.
Data model in play
- Member11 use cases
- HCO10 use cases
- HCP9 use cases
- Practitioner Role9 use cases
- Person8 use cases
- Payer5 use cases
- Contract5 use cases
- Location4 use cases
- Plan3 use cases
- Agreement2 use cases
- +5 moreCategory, Item, Product, Organization, Structure
Source-to-target mappings
- HL7 FHIR R4Element-level mappings, confirmed per implementation
- NPPES NPI RegistryColumn-level mappings with page-level evidence
- 7 enterprise system familiesEHR / EMR / PM, Credentialing platform / CAQH ProView, HCM / payroll, E-commerce / web accounts, CRM, Contract / bid / co-op pricing systems, ERP item / customer / vendor master. Mapped at attribute-family level; column names confirmed from the data dictionary.
Rules and workshops
- 37 match rulesIn the library for the entity types in play, ranked from exact keys to fuzzy name-and-address matching.
- 35 standardization rulesAcross 23 attribute families: names, addresses, phones, emails, identifiers and more.
- 132 adaptive cards10 data-model workshops, from party sub-types to stewardship.
04 · Use-case accelerator map
17 patterns, each with a landing.
Every pattern below is delivered on Informatica Customer 360 with PDI's accelerators. Patterns are anonymized from account profiles; a count such as 3× means the pattern recurs across profiles. Source systems are shown as system families.
| Use case pattern | Typical source systems | Lands on |
|---|---|---|
| Patient 3603× | HL7 FHIR R4, EHR / EMR / PM | Member, Person |
| Patient EMPI2× | HL7 FHIR R4, E-commerce / web accounts | Member, Person |
| Provider / Physician MDM2× | Credentialing platform / CAQH ProView, HL7 FHIR R4 | HCP, HCO, Practitioner Role |
| Caregiver & Clinician MDM | HCM / payroll, Credentialing platform / CAQH ProView | HCP, HCO, Practitioner Role, Location |
| Clinic / Location & Payer MDM | HL7 FHIR R4, Credentialing platform / CAQH ProView, Contract / bid / co-op pricing systems | Payer, Location, Member, Contract, Plan |
| Clinician / Provider MDM (credentialing, payer enrollment, directory) | Credentialing platform / CAQH ProView, HL7 FHIR R4, HCM / payroll | Payer, HCP, HCO, Practitioner Role, Member |
| Donor / Philanthropy 360 | Confirmed in discovery | Person, Organization |
| Location & Supply Item Master MDM | ERP item / customer / vendor master, HCM / payroll | Category, Item, Product, Location |
| Patient / Client EMPI (inpatient, community, schools) | HL7 FHIR R4, E-commerce / web accounts | Hierarchy relationships, Member, Person, Structure, Organization |
| Patient EMPI (inpatient, outpatient, research) | HL7 FHIR R4, E-commerce / web accounts | Member, Payer, Person, Contract, Plan |
| Payer & Referral Source MDM | EHR / EMR / PM, CRM | Payer, HCP, HCO, Practitioner Role, Member |
| Payer Contract MDM | Contract / bid / co-op pricing systems, EHR / EMR / PM | Payer, Member, Contract, Plan, Agreement |
| Program, Location & Provider MDM | Credentialing platform / CAQH ProView, HL7 FHIR R4, HCM / payroll | HCP, HCO, Practitioner Role, Location, Agreement |
| Provider & Researcher MDM | Credentialing platform / CAQH ProView | HCP, HCO, Practitioner Role |
| Referral Source MDM | CRM, HL7 FHIR R4, EHR / EMR / PM | HCP, HCO, Practitioner Role |
| Referring Provider MDM | CRM, EHR / EMR / PM, NPPES NPI Registry, HL7 FHIR R4 | HCP, HCO, Practitioner Role |
| Supply Item Master MDM | ERP item / customer / vendor master, Contract / bid / co-op pricing systems | Category, Item, Product |
05 · How it deploys
Five steps, each already built.
The accelerator replaces blank-page design with decisions, a drawn model and pre-built mappings.
- Decide
Adaptive-card workshops capture the design. 10 data-model workshops, 132 cards. Each card asks one decision with two to four mutually exclusive options, and each answer is logged as a configuration input.
- Model
The healthcare providers model is already drawn: 15 entities, with their relationships and hierarchies, selected for the use cases in this paper.
- Map
The two sources arrive pre-mapped. 364 column-level mappings cover NPPES, MedPro, GLEIF, SAP, Salesforce and GS1, and 60 source-system families are catalogued in all.
- Match
Match, merge and quality rules start from a library: 20 match models with 65 rules, and 35 standardization rules across 23 attribute families.
- Prove
Tenant checks and acceptance. 80 documentation discrepancies are confirmed on the tenant before configuration is generated, and the acceptance measures agreed in discovery are tested.
This Customer 360 industry entry offer is distinct from the separately scoped Informatica MDM MVP.
06 · The two-source entry point
How a $50K MVP lands here.
A fixed-fee MDM implementation for two source systems. The model, the mappings, the match and data-quality rules and the workshop cards exist before the engagement starts.
- Starting pattern
- Provider / physician master
- Source system 1
- Credentialing system (e.g., CAQH-fed)
- Source system 2
- EHR provider file or FHIR Practitioner resources
- Lands on
- HCP, HCO and Practitioner Role from Customer 360 for Healthcare
- What it proves
- One clinician record reused by credentialing, enrollment and the directory, with source lineage on every attribute.
The $50,000 covers PDI professional services only. Informatica licensing is procured separately through Informatica. Additional sources, domains or scope changes after configuration begins are estimated separately. The example sources are illustrative; any two source systems qualify, and the pair is confirmed in discovery.
07 · Confirmed in discovery
What each engagement settles first.
- The two source systems. 7 enterprise system families appear in this industry. Their column names are confirmed from the customer's data dictionary before mappings are finalized.
- The tenant. 80 documentation discrepancies across the model are confirmed on the customer's tenant before configuration is generated, including field-group internal IDs that are read from tenant metadata.
- Package order. Industry packages are imported before any customization, because importing an industry package overwrites existing Customer 360 customization.
- Acceptance. Acceptance measures are agreed in discovery, before the fee is committed.
08 · Method
How this paper was built.
The use-case map, data model, mappings and rules come from PDI's accelerator, built on Informatica's published Customer 360 and Industry 360 documentation (April and July 2026 releases) and extended for each industry. Use cases are anonymized from 124 account profiles; no account is named. Adaptive-card counts come from PDI's Customer 360 data-model workshop set. The paper states no project durations or outcome figures; those are set as acceptance measures in discovery.