What it does
CMS Open Payments Pro takes Sunshine Act pharma-to-physician payment records and enriches each one with NPI Registry data — physician specialty, license state, and practice address — then computes a per (physician × manufacturer) payment-intensity signal. Filters cover consulting, speaking, meals, travel, and research payments, so you can isolate exactly the relationship type you care about.
Who it's for
Compliance teams auditing industry relationships; plaintiff law firms building mass-tort and kickback cases; payers auditing prescriber influence; and medical journalists investigating pharma money flows.
Sample fields / output
Each record is clean JSON with 47 fields, including:
physician_npiphysician_first_namephysician_last_namephysician_op_specialtyphysician_primary_typephysician_license_statephysician_op_cityphysician_op_state
Example use cases
- Prescriber-influence audits: rank physicians by payment intensity from a specific manufacturer, filtered to consulting or speaking fees.
- Litigation research: pull the full payment history between a device maker and the physicians in a case, enriched with specialty and location.
- Investigative journalism: map which specialties and regions receive the most industry money for a given drug launch.
Try CMS Open Payments Pro on Apify →
Related actors
FAQ
What makes this 'Pro' versus raw Open Payments data?
Every record is joined with the NPI Registry (specialty, practice address, license state) and carries a per physician-manufacturer payment-intensity signal — work you'd otherwise do yourself across two datasets.
How is it priced?
Pay-per-event at $0.150 per record — about 7 enriched records per $1.
Is this public data?
Yes — CMS Open Payments (Sunshine Act) and the NPI Registry are both public federal datasets. This is public regulatory data, not medical advice.
Top comments (0)