Payment overview · 2025
General Payments
$4,752.38
5 reported records · 4 companies
Healthcare provider profile · identity verified
Ryan Patrick Huffman, MD
Allopathic & Osteopathic Physicians|Anesthesiology · PHOENIX, AZ · NPI 1831362920
Verified facts
What the public records show
CMS Open Payments records show Ryan Patrick Huffman, MD received $4,752.38 in general payments during 2025 across 5 reported records.
Delcath Systems accounted for 98.6% of that reported general-payment amount.
The Open Payments records used for this analysis explicitly named 4 associated products.
These records do not establish that a payment influenced prescribing or medical care.
Separate record types
Research & Ownership
Research Payments (direct recipient): not present in the loaded data
Associated Research Funding (for example, named PI): not present in the loaded data
Ownership / Investment: not present in the loaded data
These categories are never added into the General Payments headline. Associated research funding must not be described as money the doctor personally received unless the source record supports that conclusion.
Who paid this doctor?
Companies in 2025 General Payments
| Reported company | Canonical company | Amount | Share | Records | Year |
|---|---|---|---|---|---|
| Delcath Systems | Unresolved — no canonical attribution shown | $4,685.68 | 98.6% | 2 | 2025 |
| Merck Sharp & Dohme LLC | Unresolved — no canonical attribution shown | $32.47 | 0.7% | 1 | 2025 |
| Hologic Sales and Service, LLC | Unresolved — no canonical attribution shown | $18.79 | 0.4% | 1 | 2025 |
| Fisher & Paykel Healthcare Inc | Unresolved — no canonical attribution shown | $15.44 | 0.3% | 1 | 2025 |
What were the payments for?
Payment categories
| Category | Amount | Records |
|---|---|---|
| Consulting Fee | $4,500.00 | 1 |
| Travel and Lodging | $185.68 | 1 |
| Food and Beverage | $66.70 | 3 |
A meal, consulting fee, royalty, and travel payment describe different kinds of reported relationships and should not be interpreted as equivalent.
Analysis 1 · Payment-linked products
Products named in Open Payments records
| Reported product | Type | Reported company | Related amount* | Records | Year |
|---|---|---|---|---|---|
| Hepzato Kit Normalized: hepzato kit |
Drug | Delcath Systems | $4,685.68 | 2 | 2025 |
Source payment records
|
|||||
| BRIDION Normalized: bridion |
Drug | Merck Sharp & Dohme LLC | $32.47 | 1 | 2025 |
Source payment records
|
|||||
| ACESSA PROVU SYSTEM Normalized: acessa provu system |
Device | Hologic Sales and Service, LLC | $18.79 | 1 | 2025 |
Source payment records
|
|||||
| FISHER & PAYKEL HEALTHCARE Normalized: fisher paykel healthcare |
Device | Fisher & Paykel Healthcare Inc | $15.44 | 1 | 2025 |
Source payment records
|
|||||
* Product-associated amounts are non-additive because one payment record may name more than one product.
These products were named on specific Open Payments records. A named product does not show that the payment influenced treatment or prescribing.
Public prescribing for products named in payments
No exact normalized or approved-alias overlap was found in the loaded Part D year. This does not mean the doctor never prescribed the product.
The presence of the same drug in both datasets does not show that a payment caused or influenced a prescription.
Analysis 2 · Same-company prescribing overlap
Drugs reported in other payments from the same company that also appear in Medicare Part D
This analysis is independent from products named on this doctor’s individual payment records. A row appears only when the exact Open Payments reporting entity paid this doctor, that same reporting entity reported the drug or biological on at least 10 loaded General Payment records involving at least 2 distinct recipient NPIs, and this doctor has the same non-generic brand in public Part D data. This does not mean the company owns or manufactures the drug.
No publishable same-company prescribing overlap was found in the loaded Part D year. This does not mean the doctor never prescribed a drug reported elsewhere by a paying company.
These facts do not show that a payment was for the drug, that the company owns or manufactures the drug, or that a payment caused or influenced prescribing.
Timeline
Payment and prescribing data by year
Open Payments and Medicare Part D may refer to different years. They are shown separately rather than aligned as if they describe the same period.
| Year | General Payments | Main payer | Explicit products | Company overlaps | Part D coverage |
|---|---|---|---|---|---|
| 2025 | $4,752.38 · 5 records | Delcath Systems | ACESSA PROVU SYSTEM, BRIDION, FISHER & PAYKEL HEALTHCARE, Hepzato Kit | — | — |
| 2024 | — | — | — | — | Complete |
Questions to ask
Questions you could discuss with your doctor
- Are there reasonable alternatives I should understand when we discuss treatment options?
- How should I interpret the industry-payment records shown here in the context of my care?
These are general questions generated from reviewed templates. They are not personalized medical advice.
Sources and limitations
How to read this page
- Payment and Medicare prescribing data can cover different years; every comparison shows both years explicitly.
- Part D does not represent a doctor’s entire practice; it excludes many patients and is subject to CMS public-release thresholds.
- Company–drug relationships must have an auditable source, a precise relationship type, and a valid evidence period. Unresolved mappings are not published.
- Generic drug claims are not attributed to a specific manufacturer without manufacturer-level evidence.
- When a source extract is incomplete, missing rows are never treated as proof of no payments or no prescriptions.
Loaded source releases
| Dataset | Year | Publication | Source |
|---|---|---|---|
| CMS Open Payments — General Payments | 2025 | 2026-06-30 | Original source |
| Medicare Part D Prescribers by Provider and Drug | 2024 | 2026-05-06 | Original source |
| NPPES Data Dissemination V2 | current / reference data | 2026-08-10 | Original source |
Full methodology · Questions & answers · Report a possible error