Healthcare provider profile · identity verified

David Sukmin Lee, M.D.

Allopathic & Osteopathic Physicians|Internal Medicine|Cardiovascular Disease · MONTROSE, CO · NPI 1457397028

Profile state: payments and partd Open Payments: 2025 Medicare Part D: 2024 Last identity check: 2026-08-10 Page data build: 2026-08-12

Verified facts

What the public records show

CMS Open Payments records show David Sukmin Lee, M.D. received $196.34 in general payments during 2025 across 8 reported records.

ABIOMED accounted for 22.1% of that reported general-payment amount.

The Open Payments records used for this analysis explicitly named 6 associated products.

E.R. Squibb & Sons, L.L.C. reported payments to this doctor in 2025. Across the 2025 Open Payments General Payment records loaded for this analysis, that same reporting entity reported ELIQUIS as an associated drug or biological on 27956 records involving 14870 distinct recipient NPIs. Public Medicare Part D data also shows 256 claims for Eliquis by this doctor in 2024.

PFIZER INC. reported payments to this doctor in 2025. Across the 2025 Open Payments General Payment records loaded for this analysis, that same reporting entity reported ELIQUIS as an associated drug or biological on 87112 records involving 36032 distinct recipient NPIs. Public Medicare Part D data also shows 256 claims for Eliquis by this doctor in 2024.

These records do not establish that a payment influenced prescribing or medical care.

Payment overview · 2025

General Payments

$196.34

8 reported records · 7 companies

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 companyCanonical companyAmountShareRecordsYear
ABIOMED Unresolved — no canonical attribution shown $43.4622.1%12025
Amgen Inc. Unresolved — no canonical attribution shown $41.8121.3%22025
Dilon Technologies, Inc. Unresolved — no canonical attribution shown $26.9013.7%12025
E.R. Squibb & Sons, L.L.C. Unresolved — no canonical attribution shown $23.3011.9%12025
PFIZER INC. Unresolved — no canonical attribution shown $23.2211.8%12025
Boston Scientific Corporation Unresolved — no canonical attribution shown $19.9410.2%12025
Bayer Healthcare Pharmaceuticals Inc. Unresolved — no canonical attribution shown $17.719.0%12025

What were the payments for?

Payment categories

CategoryAmountRecords
Food and Beverage$196.348

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 productTypeReported companyRelated amount*RecordsYear
REPATHA
Normalized: repatha
Biological Amgen Inc. $41.81 2 2025
Source payment records
HEMOBLAST BELLOWS
Normalized: hemoblast bellows
Device Dilon Technologies, Inc. $26.90 1 2025
Source payment records
CAMZYOS
Normalized: camzyos
Drug E.R. Squibb & Sons, L.L.C. $23.30 1 2025
Source payment records
VYNDAQEL
Normalized: vyndaqel
Drug PFIZER INC. $23.22 1 2025
Source payment records
WATCHMAN
Normalized: watchman
Device Boston Scientific Corporation $19.94 1 2025
Source payment records
Kerendia
Normalized: kerendia
Drug Bayer Healthcare Pharmaceuticals Inc. $17.71 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.

Paying companyPayment yearDrug reported by same entityOpen Payments evidencePart DClaimsBeneficiaries
E.R. Squibb & Sons, L.L.C.
Exact reporting entity; no affiliate inference
2025 ELIQUIS
open payments reported associated product
CMS Open Payments — General Payments
27956 supporting records · 14870 recipient NPIs · example record 1184377713
Eliquis · 2024
Exact normalized brand match · 1 Part D row
256 72
PFIZER INC.
Exact reporting entity; no affiliate inference
2025 ELIQUIS
open payments reported associated product
CMS Open Payments — General Payments
87112 supporting records · 36032 recipient NPIs · example record 1228794063
Eliquis · 2024
Exact normalized brand match · 1 Part D row
256 72

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.

Public Medicare Part D data

Provider-and-drug rows loaded for 2024

BrandGenericClaimsBeneficiaries
Metoprolol SuccinateMetoprolol Succinate468148
Atorvastatin CalciumAtorvastatin Calcium385113
EliquisApixaban25672
SpironolactoneSpironolactone24775
ClopidogrelClopidogrel Bisulfate22962
JardianceEmpagliflozin21954
Isosorbide Mononitrate ErIsosorbide Mononitrate20855
Losartan PotassiumLosartan Potassium16850
LisinoprilLisinopril15153
Amlodipine BesylateAmlodipine Besylate14949
Rosuvastatin CalciumRosuvastatin Calcium14952
EzetimibeEzetimibe11234
Amiodarone HclAmiodarone Hcl10236
CarvedilolCarvedilol9228
XareltoRivaroxaban7119
DofetilideDofetilide5915
EntrestoSacubitril/Valsartan5515
FurosemideFurosemide5521
TorsemideTorsemide5123
Repatha SureclickEvolocumab44suppressed
Flecainide AcetateFlecainide Acetate3811
NitroglycerinNitroglycerin3835
Potassium ChloridePotassium Chloride3815
Metoprolol TartrateMetoprolol Tartrate3612
Pantoprazole SodiumPantoprazole Sodium2911
Warfarin SodiumWarfarin Sodium27suppressed
SotalolSotalol Hcl21suppressed
BrilintaTicagrelor20suppressed
Pravastatin SodiumPravastatin Sodium15suppressed
AmoxicillinAmoxicillin13suppressed
DigoxinDigoxin13suppressed
Praluent PenAlirocumab12suppressed
Ranolazine ErRanolazine12suppressed

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.

YearGeneral PaymentsMain payerExplicit productsCompany overlapsPart D coverage
2025 $196.34 · 8 records ABIOMED CAMZYOS, HEMOBLAST BELLOWS, Kerendia, REPATHA, VYNDAQEL, WATCHMAN 2
2024 Complete

Questions to ask

Questions you could discuss with your doctor

These are general questions generated from reviewed templates. They are not personalized medical advice.

Sources and limitations

How to read this page

Loaded source releases

DatasetYearPublicationSource
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

Methodology version: 2.1

Editorial template version: 2.4

Product contract version: 2.0

Schema version: 0.7.0

Page data build: 2026-08-12T23:34:59.370714+00:00

Publication policy: eligible for indexing after public-launch controls are enabled

Full methodology · Questions & answers · Report a possible error