Close the loop from prescription to patient — connect the patient support hub, specialty pharmacy dispense feeds, and copay programs into Veeva CRM or Salesforce Life Sciences Cloud, with consent enforced, adverse events routed to safety inside the reporting window, and field teams seeing therapy status rather than guessing.
Commercial and Patient Services: CRM, Specialty Pharmacy, and Patient Support
Objective: Give commercial and patient services teams one current view of a therapy journey — enrollment, benefits verification, copay, dispense, and adherence — while enforcing consent and routing any adverse event to pharmacovigilance inside the regulatory window. This phase closes the loop, feeding real-world evidence back to the research phase where the chain began.
What's Getting Built
- Patient support hub (System API) — wraps the hub platform for enrollment, benefits verification, copay, and case status with consent as the authority ·
GET /enrollments/{id}, GET /benefits-verification/{id}, GET /consent/{patientProgramId}
- Specialty pharmacy (System API) — normalizes each pharmacy's dispense and status feed into a canonical event, keeping pharmacy quirks out of the Process layer ·
POST /dispense-events, GET /shipment-status/{rxId}
- Consent and identity (Process API) — resolves patient and HCP identity, enforces the consent gate at use time, and builds one occurrence-ordered therapy timeline ·
POST /therapy-events, GET /therapy-timeline/{patientProgramId}, POST /consent/evaluate
- Veeva CRM / Life Sciences Cloud (target) — receives synchronized case and therapy status with role-filtered, consent-scoped field visibility ·
POST /therapy-status, GET /account/{hcpId}
- Pharmacovigilance E2B intake (target) — receives adverse events immediately on first receipt via a dedicated synchronous path with acknowledgment captured ·
POST /adverse-events, GET /adverse-events/{id}/ack
- Commercial analytics and field insights (target) — consumes de-identified or aggregated therapy signal for program-performance metrics and the value chain backbone ·
POST /therapy-events/aggregated
Value chain phase
Phase 06 — Commercial & Patient Services. Marketing to healthcare providers (HCPs) and patient support program delivery.
- Scope of this plan: Patient support hub, specialty pharmacy, and copay data flowing into CRM with consent, adverse event routing, and field-team visibility.
- 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 and a non-production deployment target.
- Secrets Manager or secure properties configured for every regulated system credential.
- Named validation owner — GxP flows need a change-control path agreed before the first deployment.
- Veeva CRM or Salesforce Life Sciences Cloud org with a connected app for the System API.
- Patient support hub platform with API access to enrollment, benefits verification, and case status.
- Specialty pharmacy data feeds agreed with each pharmacy — format, cadence, and identifier scheme.
- Pharmacovigilance system able to receive intake in the agreed format, with the reporting clock defined.
- HCP/HCO master data source for identity resolution across commercial systems.
Choose your path
- Patient support hub-led — Choose when a hub runs enrollment and benefits — integration synchronizes case and therapy status into CRM and keeps consent authoritative in one place.
- Specialty pharmacy data-led — Choose when dispense and adherence data from specialty pharmacies is the primary signal — integration normalizes feeds across pharmacies into one therapy timeline.
Platform notes
Veeva CRM / Salesforce Life Sciences Cloud
- Resolve HCP and HCO identity against the customer master before writing — creating a duplicate account is far more expensive to unwind than a rejected write.
- Keep patient-level data segregated from field-facing HCP data; a rep's view must not expose identifiable patient information.
Specialty pharmacies
- Every pharmacy sends a different shape on a different cadence — normalize at the System API and keep pharmacy-specific quirks out of the Process layer.
- Dispense and status data arrive late and out of order; build the therapy timeline to tolerate both.
Patient support hub
- Consent lives with the hub in most programs — treat it as the authority and enforce it on every downstream use.
- Benefits verification and prior authorization statuses change frequently; sync on event rather than nightly batch where the platform allows.
Architecture
1. Business requirements
- Show one therapy journey per patient across hub, pharmacy, and copay sources.
- Enforce patient consent on every use of patient data, with the scope recorded.
- Route any potential adverse event to pharmacovigilance within the regulatory reporting window.
- Give field teams therapy and access status without exposing identifiable patient data.
2. Identity and consent
- Resolve patient identity across hub, pharmacy, and copay feeds without creating duplicates.
- Resolve HCP and HCO identity against the customer master before any CRM write.
- Treat consent as a gate evaluated at use time, not a flag copied at ingestion.
- Record consent scope and revocation with timestamps, and propagate revocation downstream promptly.
3. Therapy timeline
- Normalize enrollment, benefits verification, prior authorization, shipment, dispense, and refill into one ordered timeline.
- Handle late and out-of-order events by ordering on occurrence time, not arrival time.
- Derive adherence and time-to-therapy from the timeline rather than from any single source system.
- Keep source attribution per event so a disputed status can be traced to the feed that reported it.
4. Adverse event routing
- Detect potential adverse events in any inbound channel — hub notes, pharmacy feeds, and support interactions.
- Route intake to the pharmacovigilance system immediately, with the reporting clock starting at first receipt.
- Never let an adverse event depend on a batch window or a retry queue for delivery.
- Track and alert on intake acknowledgment — an unacknowledged report is a compliance exposure.
5. Field and commercial visibility
- Surface aggregated access and therapy status to field teams, filtered by role and consent scope.
- Feed commercial analytics with de-identified or aggregated data rather than raw patient records.
- Publish therapy events to the value chain backbone so real-world signal reaches research and supply.
- Report on program performance — time to therapy, abandonment, and adherence — as first-class metrics.
6. Security, privacy, and compliance
- 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.
- Patient data in support programs is protected health information — encrypt it, minimize it, and restrict it to the roles the consent covers.
- Adverse event handling is regulated: the reporting clock starts at first receipt by anyone in the organization, including an integration.
- Keep HCP spend and interaction data aligned with transparency reporting obligations under the Sunshine Act.
For pre-built API specifications, implementation templates, and reference architecture, see the MuleSoft Accelerator for Life Sciences on Anypoint Exchange.
Sample payload — Therapy timeline event
{
"patientProgramId": "PSP-0091284",
"productCanonicalId": "PROD-00931",
"eventType": "dispense",
"occurredAt": "2026-07-28T00:00:00Z",
"receivedAt": "2026-07-31T06:15:00Z",
"source": { "system": "SPECIALTY_PHARMACY_A", "recordId": "RX-88213-04" },
"details": { "fillNumber": 4, "daysSupply": 30, "shipped": true },
"consent": { "scope": ["program-services", "adherence-outreach"], "verifiedAt": "2026-07-31T06:15:01Z" }
}
Testing and validation
- Enroll a test patient in the hub and confirm the therapy timeline appears in CRM with consent scope attached.
- Deliver two pharmacy events out of order and confirm the timeline orders them on occurrence, not arrival.
- Revoke consent and verify downstream use stops, including field-facing views, within the agreed window.
- Submit an interaction containing a potential adverse event and confirm immediate pharmacovigilance intake with acknowledgment captured.
- Confirm a field user's view exposes access status without any identifiable patient data.
Phased rollout
Phase 1 — Connect
- Wrap the hub platform and one specialty pharmacy feed with System APIs against non-production data.
- Establish identity resolution and the consent gate before any CRM write is enabled.
Phase 2 — Map and validate
- Build the therapy timeline for one product and validate ordering, adherence derivation, and source attribution.
- Wire adverse event routing and prove the reporting clock and acknowledgment handling with safety operations.
Phase 3 — Production
- Onboard remaining pharmacies and programs, keeping pharmacy-specific handling inside System APIs.
- Hand consent, adverse event, and program performance monitoring to operations with named owners.
Success metrics
- Time from prescription to first dispense reduced against the program baseline.
- 100% of potential adverse events routed to pharmacovigilance on first receipt, with acknowledgment recorded.
- Zero patient-identifiable data reaching field-facing views.
- Consent revocations propagated downstream within the agreed window, every time.
Troubleshooting
- Duplicate patient records across pharmacy feeds — Likely cause: identity resolution keyed on pharmacy-local identifiers. Fix: Resolve to the program identity at the System API and route ambiguous matches to a stewardship queue.
- Therapy status flips backwards — Likely cause: late-arriving events applied in arrival order. Fix: Order the timeline on occurrence time and make status derivation a function of the whole timeline.
- Adverse event intake delayed by a batch window — Likely cause: safety routing built on the same scheduled path as commercial data. Fix: Give adverse events a dedicated synchronous path with guaranteed delivery and acknowledgment.
- Field view shows more than consent allows — Likely cause: consent evaluated at ingestion and cached rather than at use. Fix: Evaluate the consent gate at request time and filter the response by the caller's role.
Deliverable: An integration unifying patient support hub, specialty pharmacy, and copay data into one consent-governed therapy timeline in Veeva CRM or Salesforce Life Sciences Cloud, with guaranteed adverse event routing and role-filtered field visibility.