Whitepaper · Life Sciences & Diagnostics · Informatica Customer 360
HCP, HCO, product and install base on a regulated footing.
HCP and KOL masters, hospital and IDN hierarchies, ordering providers and payers, regulated product and material masters, and instrument install base.
01 · Executive summary
The short version
- PDI delivers 42 life sciences & diagnostics use cases on Informatica Customer 360 with its accelerators. The use cases are drawn from 14 anonymized account profiles.
- Each use case arrives pre-mapped: the 26 entities it can land on, the 16 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.
Life-sciences and diagnostics companies sell to professionals, ship regulated products and service installed instruments. Each has a compliance dimension: spend transparency for HCP interactions, serialization and registration for products, and unique device identification for instruments.
The accelerator lands HCP and HCO on Customer 360 for Life Sciences, Packaged Medicinal Product and related entities on Product 360 for Life Sciences, and Payer on Customer 360 for Healthcare. Medical devices with UDI, clinical studies and instrument install base are modeled as well, with FDA GUDID catalogued as a public source.
03 · What is prepackaged for this industry
The accelerator, before day one.
Data model in play
- Person17 use cases
- Organization14 use cases
- HCO12 use cases
- HCP9 use cases
- Practitioner Role9 use cases
- Member9 use cases
- Category7 use cases
- Item7 use cases
- Product7 use cases
- Location7 use cases
- +16 moreMaterial, Supplier, Payer, Contract, Plan, Creative Work, Bond, Equity, Agreement, Asset, Legal Entity, Research Study, Medicinal Product, Packaged Medicinal Product, Pharmaceutical Product, Medical Device
Source-to-target mappings
- Salesforce Sales and Service CloudColumn-level mappings with page-level evidence
- HL7 FHIR R4Element-level mappings, confirmed per implementation
- NPPES NPI RegistryColumn-level mappings with page-level evidence
- SAP ECC / S/4HANAColumn-level mappings with page-level evidence
- FDA GUDIDElement-level mappings, confirmed per implementation
- 11 enterprise system familiesERP item / customer / vendor master, Regulatory / registry feeds, Contract / bid / co-op pricing systems, CRM, LIMS / lab order portal, Licensing / provisioning / billing, E-commerce / web accounts, PLM / CAD-PDM…. Mapped at attribute-family level; column names confirmed from the data dictionary.
Rules and workshops
- 51 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
37 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 |
|---|---|---|
| Supplier MDM4× | ERP item / customer / vendor master | Supplier, Organization, Person |
| Payer MDM3× | Licensing / provisioning / billing, EHR / EMR / PM, Contract / bid / co-op pricing systems | Payer, Member, Contract, Plan |
| Clinical Trial Site & Investigator MDM | Regulatory / registry feeds | Location, HCO, Research Study |
| Customer / Lab Account 360 (post-acquisition integration) | Salesforce Sales and Service Cloud, ERP item / customer / vendor master, E-commerce / web accounts | Organization, Person |
| Customer 360 (biopharma & CDMO sites) | Salesforce Sales and Service Cloud, ERP item / customer / vendor master, E-commerce / web accounts | Person, Organization |
| Customer 360 (integrators, distributors, veterinarians) | Salesforce Sales and Service Cloud, ERP item / customer / vendor master | Person, Organization |
| Customer 360 (labs, biopharma, hospitals) | Salesforce Sales and Service Cloud, ERP item / customer / vendor master, E-commerce / web accounts | Person, Organization, HCO, Location |
| Customer Hierarchy MDM (IDN, GPO, wholesaler chargebacks) | Contract / bid / co-op pricing systems, CRM | Hierarchy relationships, Person, Organization, Legal Entity |
| Device / Install Base MDM | ERP item / customer / vendor master | Asset |
| HCP / HCO Customer MDM (commercial launch, Sunshine Act) | Salesforce Sales and Service Cloud | HCP, HCO, Practitioner Role |
| HCP / KOL MDM | Regulatory / registry feeds, CRM, Rights management / MAM | HCP, HCO, Practitioner Role |
| Health System & Clinician User MDM | Salesforce Sales and Service Cloud | HCP, HCO, Practitioner Role, Location |
| Hospital / Imaging Center & Ordering Physician MDM | Salesforce Sales and Service Cloud, NPPES NPI Registry, HL7 FHIR R4 | HCP, HCO, Practitioner Role, Location |
| Hospital, IDN & GPO Hierarchy MDM | Contract / bid / co-op pricing systems, Salesforce Sales and Service Cloud | Hierarchy relationships, Legal Entity, HCO, Location |
| Ordering Provider & Account MDM | Salesforce Sales and Service Cloud, NPPES NPI Registry | Organization, Person, HCP, HCO, Practitioner Role |
| Ordering Provider & Clinic MDM | Salesforce Sales and Service Cloud, NPPES NPI Registry | HCP, HCO, Practitioner Role, Location |
| Ordering Provider & Institution MDM | Salesforce Sales and Service Cloud, NPPES NPI Registry, HL7 FHIR R4 | Hierarchy relationships, HCP, HCO, Practitioner Role, Organization |
| Patient & Order MDM | LIMS / lab order portal, HL7 FHIR R4 | Member, Person |
| Patient / Case MDM | Confirmed in discovery | Member, Person |
| Patient 360 across testing lines | LIMS / lab order portal, HL7 FHIR R4 | Member, Person |
| Patient MDM (de-identified tokenization across sources) | HL7 FHIR R4, LIMS / lab order portal | Member, Person |
| Patient MDM (longitudinal transplant surveillance) | LIMS / lab order portal, HL7 FHIR R4 | Member, Person |
| Payer Coverage MDM | Licensing / provisioning / billing | Payer, Member, Contract, Plan |
| Pharma Client & Brand Account MDM | CRM, ERP item / customer / vendor master | Organization, Person |
| Pharma Partner & Dataset Licensing MDM | CRM, Contract / bid / co-op pricing systems | Organization, Agreement, Creative Work |
| Product & Instrument Install Base MDM | ERP item / customer / vendor master, Salesforce Sales and Service Cloud | Bond, Equity, Category, Item, Product |
| Product & Material MDM | SAP ECC / S/4HANA, Regulatory / registry feeds | Category, Item, Product, Material |
| Product & Material MDM (many acquired lines) | PLM / CAD-PDM | Category, Item, Product, Material |
| Product & Material MDM with regulatory registrations | SAP ECC / S/4HANA, ERP item / customer / vendor master, Regulatory / registry feeds | Category, Item, Product, Material |
| Product / Material & UDI MDM | FDA GUDID, PLM / CAD-PDM | Medical Device, Category, Item, Product, Material |
| Product / NDC & Material MDM (DSCSA serialization) | ERP item / customer / vendor master | Medicinal Product, Packaged Medicinal Product, Pharmaceutical Product, Category, Item |
| Product, Material & Instrument Install Base MDM | ERP item / customer / vendor master, Salesforce Sales and Service Cloud, Field service / dispatch, PLM / CAD-PDM | Bond, Equity, Category, Item, Product |
| Publication & Content MDM | Rights management / MAM, Regulatory / registry feeds | Creative Work |
| Research Collaborator & KOL MDM | CRM, Rights management / MAM, Regulatory / registry feeds, LIMS / lab order portal | HCP, HCO, Practitioner Role |
| Subscription & Entitlement MDM | ERP item / customer / vendor master, Licensing / provisioning / billing | Agreement, Creative Work |
| Supplier / CMO MDM | ERP item / customer / vendor master | Supplier, Organization, Person |
| Transplant Center & Provider MDM | Salesforce Sales and Service Cloud, NPPES NPI Registry | HCP, HCO, Practitioner Role, Location |
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 life sciences & diagnostics model is already drawn: 26 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
- HCP / HCO customer master
- Source system 1
- Salesforce (Sales/Service Cloud)
- Source system 2
- ERP customer and ship-to file
- Lands on
- HCP and HCO from Customer 360 for Life Sciences, using the accelerator's Salesforce column mappings
- What it proves
- One professional and one institution record behind commercial, ordering and transparency reporting.
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. 11 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.