HCP Engage governs the full lifecycle of healthcare professional interactions — from NPI-verified onboarding and debarment screening through FMV-enforced engagements, approval workflows, and Sunshine Act-ready reporting. Zero compliance exposure, by design.
Built for Compliance-First Teams
Live NPI verification via CMS NPPES — canonical HCP identity
OIG LEIE + SAM.gov debarment screening on every HCP
FMV rate snapshotted at engagement creation — immutable forever
Append-only audit log — no UPDATE or DELETE, ever
Sunshine Act-ready data structure from day one
SAML SSO + RBAC — enterprise-ready from the start
Every interaction with a healthcare professional is a compliance event. Here's why the usual way of managing it puts you at risk — and how HCP Engage closes the gaps.
0 / 4 essentials
The Requirement
Under the Sunshine Act, every transfer of value between a pharma company and an HCP must be documented, justified at fair market value, and reported to CMS.
The Broken Status Quo
Most teams juggle this across disconnected spreadsheets, email chains, and paper contracts — creating exactly the gaps that become audit findings.
How HCP Engage Fixes It
One compliance-first platform: every engagement is NPI-verified, debarment-screened, FMV-justified, approved, and recorded in an immutable audit trail — before a single dollar is paid.
The Compliance Risk
Payments to OIG-excluded individuals can trigger exclusion from federal healthcare programs; engagements above FMV without written justification expose you to DOJ False Claims Act liability.
HCP Engage enforces compliance at every stage — from first contact with an HCP through final invoice and proof of performance.
Every HCP is registered with live NPI lookup against the CMS NPPES API — retrieving canonical name, credentials, NUCC specialty code, primary state, and institutional affiliation. No manual entry, no identity drift.
Dual-source debarment checks against OIG LEIE and SAM.gov using NPI-first matching. Compliance officers record a written determination with rationale. Determinations are immutable and audit-logged.
Rate cards are uploaded as Excel/CSV, validated against NUCC taxonomy, and versioned with effective date ranges. At engagement creation, the applicable FMV rate is displayed and snapshotted — making every payment permanently justifiable.
Engagements move through a governed state machine — Draft → Submitted → Compliance Review → Legal Review → Approved or Rejected. Only named transitions are permitted; no direct status overrides, no gaps in the approval chain.
For completed engagements, business users attach proof-of-performance files (PDF, image, DOCX). Once submitted, PoP documents are stored immutably in cloud storage — the URL cannot be overwritten through any application path.
PDF invoices are auto-generated from the snapshotted FMV rate and activity count — stored write-once in cloud storage. The engagement record carries everything needed for Sunshine Act Open Payments reporting.
HCP Engage enforces rules in code — not in training documents — so your audit posture doesn't depend on individual behavior.
HCP identity confirmed at onboarding via CMS NPPES. Canonical name, credentials, specialty (NUCC taxonomy), and institutional affiliation stored as authoritative record.
Dual-source exclusion checks with NPI-first matching. Written determination and rationale recorded by compliance officer — immutable, auditable, and re-checkable on demand.
Rate cards uploaded as Excel or CSV, validated against NUCC taxonomy before activation. Rate versions never overwritten — historical engagements remain auditable against the rate in effect at creation time.
Applicable FMV rate locked to each engagement at creation. Once set, it cannot be changed — your payment justification is permanent and verifiable, independent of future rate card updates.
Only named transitions are permitted between engagement states. No direct field updates, no status skipping. Every transition is timestamped and logged with the actor's identity and role.
Audit entries are write-only at the database level. The application cannot UPDATE or DELETE them — giving regulators and auditors a guaranteed, tamper-proof record of every action.
Invoices generated from snapshotted FMV rate and activity count — stored write-once in cloud storage (Cloudflare R2). Compensation is calculated, documented, and preserved automatically.
Role-based access control with three tiers (Business, Compliance, Finance/Legal) enforced at the route level. SAML SSO integration with Okta, Azure AD, and other enterprise identity providers.
See how HCP Engage stacks up against legacy enterprise platforms.
| Capability | HCP Engage | Legacy Platforms |
|---|---|---|
| NPI Verification | Live NPPES API — real-time | Manual or batch lookup |
| Debarment Screening | OIG LEIE + SAM.gov, dual-source | Often single source or manual |
| FMV Rate Versioning | Immutable versioned rate cards | Rate overrides possible |
| Audit Log Integrity | Write-only DB role — no overwrites | Application-level logging only |
| Sunshine Act Readiness | ||
| SAML / SSO Integration | ||
| Time to Deploy | Configurable without code changes | Custom implementation required |
Designed for the teams responsible for governing HCP relationships inside pharma and biotech organizations.
HCP onboarding, debarment verification, engagement oversight, and policy enforcement from a single dashboard.
Approval workflows, FMV-justified spend tracking, invoice generation, and payment documentation without spreadsheet chaos.
Submit engagement requests, upload proof of performance, and track approval status — without needing to understand the compliance rules themselves.
Review engagements at the legal review gate, access the complete audit trail, and retrieve immutable engagement records for any regulatory inquiry.
Most platforms rely on training and SOPs to drive compliant behavior. HCP Engage builds the rules into the system — so non-compliant actions are structurally impossible, not just discouraged.
Every record carries a tenant_id — non-nullable, present from migration 1. Cross-tenant data access is structurally impossible, not just access-controlled.
The audit log lives in a separate database schema accessed through a write-only role. The application literally cannot issue UPDATE or DELETE on audit records — at any level.
Approval chains, engagement types, and policy settings are versioned database records scoped by tenant — configurable without code deployments, auditable like any other data.