Pharma Payment–Prescribing Exposure Analytics

What you get

• brand_influence — 288 drug brands: paid-prescriber share, claims & cost ratios of paid vs. unpaid prescribers, top paying manufacturer (public)
• specialty_payment_benchmarks — 92 specialties: payment penetration, median/mean payment, total Part D drug cost (public)
• npi_exposure — 734,622 physician-level exposure profiles with payment-per-$1k-drug-cost metric (gated, approval required)
• Methodology doc with honest association-not-causation framing + reproducible pipeline reference

Sample preview

First 50 rows of the real free-sample file — the identical schema you get in every package. Click a column to sort, or filter across all rows.

Coverage statistics

Records

735,002

Largest package

81.7 MB

Available packages

Real contents of the current builds — row counts, sizes and checksums come from the packaging manifest, not estimates.

Full package inventory

Every package registered in the delivery catalog for this dataset — 2 packages, 81.8 MB total, 735,382 rows. Sizes, row counts and SHA-256 checksums come straight from the packaging pipeline.

How to get this data

# Machine-readable package index (size / sha256 / rows / channels)
curl -s https://data.zalize.com/datasets/pharma-payment-prescribing-exposure/packages.json | jq '.packages[0]'

# Request a free sample (signed link sent to your email)
curl -X POST https://dl.zalize.com/api/sample \
  -H 'Content-Type: application/json' \
  -d '{"dataset":"pharma-payment-prescribing-exposure","email":"you@company.com"}'

Pricing

AI-training use requires the AI-Training tier (1.5× base); redistribution licensing is quoted individually. Annual subscriptions get 2 months free. License details →

Update frequency & delivery

• Built from CMS Open Payments (PY2025) × Medicare Part D Prescriber (2024) — both official public-domain CMS releases.
• Physician-level file is never sold self-serve: gated with manual approval, per our PII policy.

Compliance & provenance

Collected only from publicly accessible pages and endpoints — no login-required data, no CAPTCHA solving, no forged authentication. Collection is rate-limited with an identified User-Agent, and collection logs are retained. PII is removed or pseudonymized. Every record carries its source URL and collection timestamp. Sold under a tiered commercial license.

FAQ