HCP Brand Portal: API & Integration Strategy

A major pharma customer is launching a gated brand portal for a newly approved allergy drug. Healthcare Professionals (HCPs) register on the portal to verify their identity, declare product interests, update their practice information, and request drug samples.

None of these actions are standalone — each must connect to the customer's healthcare Master Data Management (MDM) system, which is the system of record for every HCP in the network. The integration layer I designed sits between the portal and the MDM, handling identity verification, controlled data ingestion, and high-value event routing to the Pharma CRM.

I served as the product owner for the API and integration strategy — responsible for defining the integration architecture, authoring the API contracts, establishing the data ingestion rules, conducting a gap analysis against the existing MDM API surface, and proposing a roadmap to close the gaps.

The work required deep collaboration with engineering on technical feasibility and close alignment with compliance stakeholders on data governance — particularly around the principle that the portal is a data collector, not a data owner.

• Defined four core integration requirements — identity verification, registration & interest tracking, profile updates via DCR, and near-real-time CRM push for high-value engagements (sample requests)
• Established key design decisions: strict matching over flexible matching to protect MDM integrity; no direct overwrite (all portal submissions enter pending Data Change Request state); tiered sync model (synchronous for registration, near-real-time for sample requests, async batch for profile updates)
• Designed a 3-tier matching engine using NPI as the primary key — Tier 1 exact match auto-verifies, Tier 2 fuzzy match (≥85% Jaro-Winkler) routes to human review, Tier 3 no match rejects and prompts for additional credentials
• Authored five data ingestion rules governing source priority, address deduplication, specialty validation via medical board registries, email/phone as alternates (not replacements), and a full audit trail per ingestion event
• Authored the API contracts for registration/verification (synchronous, NPI-keyed) and profile updates (DCR-based, async)
• Conducted a gap analysis identifying 4 platform gaps — no atomic registration endpoint, no idempotency key on ingest, no native product interest object, no outbound CRM webhook
• Proposed a new endpoint (POST /v1/hcp/portal-engage) that resolves all 4 gaps in a single atomic call — combining match, verify, ingest, product interest capture, and CRM webhook in one contract

• Data integrity over convenience: prioritizing strict MDM matching — even at the cost of registration friction — prevents downstream corruption in CRM, compliance, and sampling systems that depend on the Golden Record as source of truth
• The portal is a data collector, not a data owner: framing this principle early shaped every ingestion rule and governance decision throughout the design
• Gap analysis as roadmap input: documenting platform gaps with evidence (HIGH/MEDIUM severity, root cause per gap) gave the engineering team a concrete, prioritized pitch rather than vague technical debt
• Atomic API design reduces operational surface: consolidating 3+ chained calls into one endpoint eliminates partial-failure states, removes duplicate-record risk, and makes the integration dramatically easier to test and monitor