HCP Master Data for Life Sciences Cloud Go-Live: OneKey, Informatica MDM, and Data 360

HCP Master Data for Life Sciences Cloud Go-Live: OneKey, Informatica MDM, and Data 360 · Blueprints · Muley SolutionsLand a clean HCP and HCO master in Life Sciences Cloud for go-live — search OneKey before create, bulk and delta sync into Account and HealthcareProvider, keep an Informatica MDM golden record with a Veeva, OneKey, and LSC ID crosswalk, and resolve identity in Data 360 for analytics and agents.Tags: life-sciences, life-sciences-cloud, pharma, medtech, hcp-data, mdm, onekey, informatica, data-360, salesforce, mulesoft-direct, remix

Objective: Go live on Life Sciences Cloud with one answer to who each HCP and HCO is. OneKey supplies reference data, Informatica MDM arbitrates the golden record, LSC holds the working record in Account and HealthcareProvider, and Data 360 resolves identity for analytics and agents — tied together by a crosswalk that still knows every legacy Veeva ID.

What's Getting Built

OneKey bulk load and search (System API, from MuleSoft Direct) — the prebuilt Provider Bulk Sync integration brings OneKey HCPs and HCOs into the Life Sciences Cloud healthcare data model, and Provider Services adds real-time OneKey search, data change requests, and status tracking
OneKey (System API) — searches and retrieves OneKey HCP and HCO reference records by country · GET /onekey/search, GET /onekey/individuals/{id}
Search before create (Process API) — searches MDM then OneKey before any create in LSC, and links rather than duplicates · POST /hcp/match, POST /hcp
Informatica MDM (System API) — golden record, survivorship, and the Veeva, OneKey, and LSC ID crosswalk · POST /entities, GET /crosswalk/{id}
LSC provider sync (Process API) — bulk loads and delta-syncs golden records into Account and HealthcareProvider · POST /lsc/providers/bulk, PUBLISH hcp.changed
Data 360 identity (Process API) — feeds golden IDs and crosswalk into Data 360 identity resolution · POST /data360/ingest

Value chain phase

Phase 06 — Commercial & Patient Services. Marketing to healthcare providers (HCPs) and patient support program delivery.

Scope of this plan: HCP and HCO identity for a Life Sciences Cloud go-live, from reference data through golden record to LSC and Data 360.
Data in this phase: CRM (Veeva / Salesforce Life Sciences Cloud), prescription data, and logs.
Receives from: Phase 05 — Supply Chain & Logistics.
Hands off to: Nothing downstream — this phase closes the loop back to Research & Discovery with real-world evidence.

Prerequisites

Anypoint Platform org with API Manager, Runtime Manager, and a non-production deployment target.
Salesforce Life Sciences Cloud org with a connected app and an integration user scoped to the objects this plan writes.
Secrets Manager or secure properties configured for every system credential.
Named owner for each source system — integration stalls on access, not on code.
OneKey licence and API access for every country in scope — through MuleSoft or the IQVIA API, per your contract.
MuleSoft Direct for Life Sciences Cloud, to deploy Provider Bulk Sync and Provider Services from inside Salesforce.
Informatica MDM with an HCP and HCO model and stewards named.
Data 360 (Data Cloud) org with identity resolution rules agreed.
Legacy Veeva CRM and Network IDs available for the crosswalk.

Choose your path

OneKey direct, MDM later — Choose for a first go-live with OneKey and no MDM yet — deploy the MuleSoft Direct Provider Bulk Sync and Provider Services integrations, and keep the crosswalk so MDM can take over arbitration later.
OneKey-led — Choose where OneKey is licensed for the country — search it before create and subscribe to its changes.
MDM-led — Choose in countries without OneKey coverage — MDM matches against internal sources and stewards approve new records.

Architecture

1. Search before create

Search MDM, then OneKey, before any HCP create in LSC; on a hit, link to the existing record. Provider Services can serve the OneKey search and carry the data change request when a rep's edit needs OneKey to change.
Route a OneKey record not yet in MDM through MDM, not straight into LSC.

2. Load and sync LSC

Bulk-load the golden record into Account plus HealthcareProvider for go-live, then switch to delta events.
Carry specialty, licence, affiliations, and addresses as LSC related records, not flattened fields.

3. Keep the crosswalk

Hold Veeva, OneKey, MDM, and LSC IDs in one crosswalk in MDM.
Publish merges as retirement events so LSC and every consumer repoint.

4. Multi-country OneKey caveats

OneKey coverage and attributes vary by country; map per country and fall back to MDM-led where coverage is thin.
Respect licence terms per country on which attributes may be shown to which users.

5. Resolve identity in Data 360

Ingest the golden ID and crosswalk so Data 360 unifies engagement across channels on the same person.

6. Security, privacy, and data integrity

Validate the integration under GAMP 5 — requirements, design, IQ/OQ/PQ evidence, and a traceability matrix retained for inspection.
Meet 21 CFR Part 11 and EU Annex 11 for electronic records and signatures on every GxP-relevant flow.
Preserve ALCOA+ data integrity — attributable, legible, contemporaneous, original, and accurate — with audit trails no operator can edit.
Encrypt regulated data in transit and at rest, and keep production payload visibility to validated support roles only.
Treat a mapping change on a GxP flow as a controlled change under change management, never as a hotfix.
Honour OneKey licence restrictions on attribute distribution per consumer.

For pre-built API specifications, implementation templates, and reference architecture, see the MuleSoft Accelerator for Life Sciences on Anypoint Exchange.

Testing and validation

Create an HCP in LSC who exists in OneKey and confirm it links instead of duplicating.
Merge two masters in MDM and confirm LSC and Data 360 repoint.
Look up a legacy Veeva ID and confirm the crosswalk returns the LSC record.

Phased rollout

Phase 1 — Connect

Deploy Provider Bulk Sync and Provider Services from MuleSoft Direct, or build the OneKey System API, then build the MDM System API and load the golden record for the pilot country.
Populate the crosswalk from Veeva.

Phase 2 — Map and validate

Bulk-load LSC and turn on search before create.
Ingest into Data 360 and check identity resolution.

Phase 3 — Production

Switch to delta sync and roll country by country.
Hand duplicate-rate monitoring to stewards.

Success metrics

Duplicate HCP creation in LSC after go-live, trending to zero.
Share of LSC providers with a full crosswalk.
Steward queue age within service level.

Troubleshooting

Duplicates appear in LSC after go-live — Likely cause: a create path that skips search before create, often a data load or integration user. Fix: Route every create, including integrations, through the match API.

Deliverable: A golden HCP and HCO master in Informatica MDM, loaded into Life Sciences Cloud with search-before-create, a full Veeva/OneKey/LSC crosswalk, and identity resolved in Data 360.

Related MuleSoft accelerators

Customer, HCP, and HCO Data Management: CRM, MDM, and Veeva — Give every commercial, service, and safety system the same answer about who the customer is — match and merge prescribers, surgeons, hospitals, and buying orga…

Patient Services on Life Sciences Cloud: Moving Off Health Cloud Behind the System Layer — Rebuild patient support programs on Life Sciences Cloud while Health Cloud is retired behind a System API — enrollment with document intake through IDP, electr…

Veeva CRM to Life Sciences Cloud Migration: Abstract, Coexist, and Repoint by Wave — Move field teams from Veeva CRM, OCE, or Health Cloud to Salesforce Life Sciences Cloud without a big-bang cutover — put System APIs in front of the old and ne…

Visit Expenses and Aggregate Spend: Concur to Life Sciences Cloud and Transparency Reporting — Connect SAP Concur expenses to the Life Sciences Cloud visits and HCPs they were spent on, keyed on the golden HCP ID, and feed aggregate spend for US Open Pay…

Clinical Site Lifecycle on Life Sciences Cloud: Identify, Feasibility, Select, Activate, Monitor — Run the clinical site lifecycle in Life Sciences Cloud — identify sites and investigators, send and score feasibility, select, activate with documents and cont…

Territory and Alignment Feeds into Life Sciences Cloud: Recurring Loads with Validation and Replay — Load territories, rep assignments, and account alignments into Life Sciences Cloud on a schedule — from an alignment tool, a data warehouse, or files — with va…

Consent API for Life Sciences Cloud: OneTrust Enforced at the Gateway — Put one Consent API in front of OneTrust and enforce it as an Omni Gateway policy on every channel and agent call into Life Sciences Cloud — email, visits, pat…

Controlled-Substance Product Returns: Salesforce LSC, Agent Fabric, and SAP — A distributor calling in a Schedule II product return today either stalls a CSR in a system that can't see the SAP order or return-processing logic, or lets a…

All MuleSoft Solution Blueprints

Muley Solutions — MuleSoft integration accelerators: Solution Blueprints with reference architectures and build steps, working tools and plain-language answers for Agent Fabric and Anypoint Platform — built by MuleSoft Solution Engineering.

Solution Blueprints — MuleSoft integration accelerators for Healthcare, Life Sciences, Financial Services and more: Solution Blueprints with reference architectures, API-led designs and build steps, ready for Vibes or any AI IDE.

Tools — Working tools and interactive demos that bring Agent Fabric and Anypoint Platform to life, from designing agentic assets to orchestrating end-to-end workflows.

Ask a Muley — Plain-language answers about Agent Fabric, Omni Gateway and Anypoint Platform — the questions people actually ask, answered with the slides that go with them.

Agent Fabric Effect — What changes when agents run on a control plane: the same enterprise use cases before and after Agent Fabric.

Agent Fabric Layers — A product-agnostic agentic control plane architecture and how Agent Fabric delivers discover, govern, orchestrate, actionability, and observe — with Ask a Muley slides for each capability.

Agent Fabric Live — The Omni Gateway broker in action: every prompt priced against a premium-model-for-everything baseline, routed to the right model in real time, with a deterministic policy gate blocking unsafe prompts — and the savings quantified.

Muleymatica — The composable data foundation an agentic enterprise stands on: trusted context, governed control and real-time activation, and what MuleSoft, Informatica and Data 360 each own of it.

Hands-On Labs — Step-by-step labs for MuleSoft: set up Vibes, connect to Salesforce, SAP, Azure, Google and more, with a checklist that keeps your place.

Journeys — From business outcomes to target architecture, the steps to get there, and questions answered — the public journeys, plus the door to a private one.

Help — How to use Muley Solutions — find a Solution Blueprint, read it, take it to Vibes or your AI IDE, and publish what you build.

Privacy Policy — What Muley Solutions stores, the cookies it uses, and how the Google Slides export uses only the Drive files it creates.

Our Story — The Muley Solutions story, slide by slide: the problem it solves, what a Solution Blueprint is, and how you find one, build from it and publish what you ship.