Brian Pakyan Lam, PA-C

  • Falls Church, VA
  • Physician assistant
NPI1467563080PAC ID7911956669
Part D claims, 2024
111
MIPS score, 2024
83
Hospital affiliations
2
Industry payments
$15,652
Medical group
1
Practice address
3300 Gallows Rd, Falls Church, VA 22046
Practice phone
Call (703) 698-3659
Professional email
Get professional email
Personal email
Get personal email
Mobile number
Get mobile number
Social profiles

Primary practice

Inova Fairfax Hospital - Unit

Acute Care Hospital-Unit · Falls Church, Virginia

Find Brian Lam's professional email, personal email and mobile number

Dmand AI checks each channel through healthcare-specific waterfall enrichment. See what is on file with a free account, with practice phones, licenses and affiliations.

View contacts for free

Brian Pakyan Lam is a physician assistant in Falls Church, Virginia

Brian Lam practices at Inova Fairfax Hospital - Unit in Falls Church, Virginia.

Brian Lam's NPI, 1467563080, was assigned on August 31, 2006. Brian Lam holds Virginia license 0110001800.

NPI and contact details
Medicare PAC ID
7911956669
NPI enumeration date
August 31, 2006
NPI status
Active
Accepts Medicare assignment
Yes
Practice phone
(703) 698-3659
Professional email
Get email
Personal email
Get email
Mobile number
Get number
Sex
Male
Estimated age
49
Medical school graduation
2003

Sources: NPPES NPI Registry (CMS); Dmand AI Professional Profile Data; Dmand AI Affiliation Data; and Doctors and Clinicians National Downloadable File (CMS)

Brian Pakyan Lam practices at Inova Fairfax Hospital - Unit in Falls Church, Virginia

Brian Lam's primary practice is Inova Fairfax Hospital - Unit, at 3300 Gallows Rd, Falls Church, VA 22046 in Falls Church City. The practice phone is (703) 698-3659.

  • Inova Fairfax Hospital - Unit
    3300 Gallows Rd, Falls Church, VA 22046 · Falls Church CityPhone(703) 698-3659

Source: Dmand AI Affiliation Data

Brian Pakyan Lam is affiliated with 2 sites of care and 1 medical group

Brian Lam's primary practice is Inova Fairfax Hospital - Unit in Falls Church, Virginia. Brian Lam is also affiliated with Inova Fairfax Hospital. The medical group on file is Inova Urgent Care Center.

Inova Fairfax Hospital - UnitAcute Care Hospital-Unit · Falls Church, VirginiaPrimary
Inova Fairfax HospitalAcute care hospital, Falls Church, VAInova Urgent Care CenterPrimary care group, Vienna, VA

Source: Dmand AI Affiliation Data

Dmand AI tracks the EHR system at Brian Pakyan Lam's practice

Dmand AI tracks the electronic health record (EHR) system at each site where Brian Lam practices, 2 sites in all. Vendor and product names are available with a free account.

EHR by site
SiteEHR vendor and product
Inova Fairfax Hospital - UnitAvailable with a free account
+1 more affiliated siteAvailable with a free account

Source: Dmand AI Technology Install Data

For health IT teams

See the EHR and IT leaders at every site where Brian Lam practices

Dmand AI maps EHR vendors, IT decision makers and buying committees across each health system and 6.2K+ hospitals, with verified contacts in the same login.

Brian Pakyan Lam is one of 759 physician assistants in Virginia

Medical is Brian Lam's primary specialty in the NPI Registry, under taxonomy code 363AM0700X. Dmand AI has Brian Lam's licenses on file in 2 states: Virginia and Maryland.

Specialties and state licenses

  • Medical physician assistant, VirginiaPrimaryLicense 0110001800 · taxonomy 363AM0700X
  • Maryland licenseLicense C0002823

Physician assistants near Brian Lam

Counts of physician assistants with a Dmand AI profile, by place and practice. Each opens the list.

Sources: NPPES NPI Registry (CMS); Dmand AI Professional Profile Data; and Dmand AI Peer Benchmarks

Brian Pakyan Lam's patients have a median age of 58

Across all payers, Dmand AI patient panel data puts Brian Lam's median patient age at 58, with 45% women.

Brian Lam's patients across all payers

Dmand AI patient panel data covers Medicare, Medicaid and commercial patients.

Patient panel by age, all payers

Median age 58

Patient panel by sex, all payers

  • Women45%
  • Men54%

Source: Dmand AI Patient Panel Data

Brian Pakyan Lam wrote 111 Medicare Part D claims in 2024

In 2024, Brian Lam wrote 111 Medicare Part D claims for 19 patients. 56% of them were for generic drugs.

Part D claims, 2024111
Part D patients19

Brian Lam's Part D claims by kind of drug, 2024

  • Generic62 claims56%
  • Brand-name49 claims44%

Source: Medicare Part D Prescribers - by Provider (CMS), 2024 data

Brian Pakyan Lam scored 83 out of 100 in Medicare's MIPS program for 2024

CMS publishes a Merit-based Incentive Payment System (MIPS) score of 83 out of 100 for Brian Lam for performance year 2024, reported as part of a group. Brian Lam accepts Medicare assignment, so Medicare's approved amount is taken as full payment.

Accepts Medicare assignment
Yes

Brian Lam's MIPS scores, performance year 2024

  • 83of 100Final score
  • 73of 100Quality
  • 100of 100Promoting Interoperability
  • 40of 100Improvement Activities
  • 71of 100Cost

Each score is out of 100. The final score weighs the categories CMS scored for this clinician.

Sources: Doctors and Clinicians National Downloadable File (CMS); and Clinician Public Reporting: Overall MIPS Performance (CMS), 2024 data, released September 10, 2026

For MedTech and pharma teams

Find physician assistants like Brian Lam by procedure volume and prescribing

Filter 7.4M+ HCPs by Medicare procedures, Part D drugs and Open Payments history, then reach them with verified contacts in one login.

Brian Pakyan Lam received $15,652 in industry payments in 2025

CMS Open Payments shows 23 general payments to Brian Lam from 2 drug and device companies in 2025. Speaker and faculty fees make up the largest share, 85% of the total. Madrigal Pharmaceuticals paid the most, $12,116.

General payments to Brian Lam by kind, 2025 to 2025

$15.7Kin total
  • Speaker and faculty fees$13,36485%
  • Consulting fees$1,1557%
  • Food and beverage$8696%
  • Travel and lodging$2642%

Companies that paid Brian Lam the most, 2025 to 2025

Share is of all general payments to this clinician.

See all payments to Brian Lam

Source: Open Payments (CMS), 2025 data, released July 7, 2026

Sources for Brian Pakyan Lam's profile data

Sources for the data on this page
Data on this pageSource
NPI, name, sex, specialty and licensesNPPES NPI Registry (CMS) (opens in a new tab)Dmand AI Professional Profile Data
Practice locations and phoneDmand AI Affiliation Data
Primary practice, affiliations and health systemDmand AI Affiliation Data
Medicare patients and the all-payer patient panelDmand AI Patient Panel Data
Part D prescribingMedicare Part D Prescribers - by Provider (CMS) (opens in a new tab)
MIPS scores, telehealth, assignment and procedure percentilesDoctors and Clinicians National Downloadable File (CMS) (opens in a new tab)Clinician Public Reporting: Overall MIPS Performance (CMS) (opens in a new tab)
Industry paymentsOpen Payments (CMS) (opens in a new tab)
EHR at each practice siteDmand AI Technology Install Data
Similar physiciansDmand AI Affiliation Data

Data last refreshed October 2026Report an inaccuracyRemove my information

FAQ

Frequently asked questions about Brian Pakyan Lam

Spotted something out of date? Email hello@dmand.ai and we will check the record. Contact details live in the free trial.

What is Brian Pakyan Lam's NPI number?

Brian Pakyan Lam's NPI number is 1467563080. It was assigned on August 31, 2006, and it is active in the NPI Registry.

What does Brian Pakyan Lam specialize in?

Brian Pakyan Lam is a physician assistant in Falls Church, Virginia. The primary specialty in the NPI Registry is Medical Physician Assistant (taxonomy code 363AM0700X).

Where does Brian Pakyan Lam practice?

Brian Lam practices at 3300 Gallows Rd, Falls Church, VA 22046. Brian Lam's primary practice is Inova Fairfax Hospital - Unit in Falls Church, Virginia.

What is Brian Pakyan Lam's office phone number?

The practice phone on file for Brian Lam is (703) 698-3659.

What is Brian Pakyan Lam's medical license number?

Brian Lam holds Virginia license 0110001800, one of the licenses on file in 2 states.

Which states has Brian Pakyan Lam been licensed in?

Dmand AI has state licenses on file for Brian Lam in Virginia and Maryland.

Which hospitals is Brian Pakyan Lam affiliated with?

Brian Lam is affiliated with Inova Fairfax Hospital. Dmand AI links Brian Lam to 1 more hospital.

What medical group is Brian Pakyan Lam part of?

Brian Lam is linked to Inova Urgent Care Center.

Does Brian Pakyan Lam accept Medicare?

Yes. CMS lists Brian Lam as accepting Medicare assignment.

What is Brian Pakyan Lam's MIPS score?

Brian Lam's MIPS final score for performance year 2024 is 83 out of 100, reported as part of a group.

Has Brian Pakyan Lam received payments from drug or device companies?

CMS Open Payments shows $15,652 in general payments to Brian Lam from 2 companies from 2025 to 2025. The largest total came from Madrigal Pharmaceuticals.

How long has Brian Pakyan Lam been practicing?

Brian Lam graduated from medical school in 2003, 23 years ago.

Selling to medical practices?

See physician assistants in Virginia by site of care and group

Find the practices, groups and hospitals they work with, and the right people to contact at each.

  • 30 days free
  • Self-serve
  • No credit card

Cookie settings

Turn each category on or off. Your choice is kept for 12 months and you can change it here at any time.

Necessary

Always on. Sign-in, security, downloads you asked for, your cookie choice, and the page that led to a signup.

View cookies (6)
  • dm_consentDmand AI. Your cookie choices and whether your browser sent a Global Privacy Control signal. 12 months.
  • dm_ft, dm_ltDmand AI. The first and the latest page you arrived on, with the date, so a signup is credited to the page that worked. 90 days, 30 days.
  • dm_fs, dm_lsDmand AI. The first and the latest source of a visit (a search engine, a campaign or the site that linked here). 90 days, 30 days.
  • dm_dl, dm_dl_okDmand AI. After you give an email address for a download, lets you download files without being asked again. 30 days.
  • Session and CSRF cookiesDmand AI (app.dmand.ai). Sign-in and form protection in the application. Session.
  • __cf_bm, cf_clearanceCloudflare. Tells people from automated traffic and keeps the site available. 30 minutes; cf_clearance while a security check is valid.

Analytics

On unless you turn it off. How pages are used, in aggregate, and recordings of how pages are used.

View cookies (6)
  • Google Tag ManagerGoogle. Loads the analytics and marketing tags that are on. Sets no cookie of its own and does not load when both categories are off. n/a.
  • _ga, _ga_<container-id>Google Analytics 4. Visits and page views in aggregate on dmand.ai. 2 years.
  • _clck, _clskMicrosoft Clarity. Recordings and heatmaps of how pages are used, with form fields masked. 1 year, 1 day.
  • CLID, MUID, ANONCHK, MR, SMMicrosoft (clarity.ms). Set by Microsoft when Clarity loads, to recognize a browser across sites that use Clarity. Up to 1 year.
  • None (cookieless)Ahrefs Analytics. Page views in aggregate. n/a.
  • ph_<project>_posthogPostHog. Product usage, errors and performance in app.dmand.ai, used to fix bugs and improve features. 365 days.

Marketing

On unless you turn it off, and always off when your browser sends a Global Privacy Control signal. A visitor identification service tells our sales team which companies and people visit.

View cookies (6)
  • _reb2buid, _reb2butkRB2B. Recognizes a returning browser for visitor identification. 360 days, 1 year.
  • _reb2bgeoRB2B. The location used to decide whether a visit can be identified. 20 days.
  • _reb2brefRB2B. The page or site that referred the visit. 15 days.
  • _reb2bfxf, _reb2btd, _reb2bliRB2B. Links the visit to an identified business profile. 1 month.
  • _reb2bresolveRB2B. Holds a match while it is being resolved. 2 days.
  • _reb2sessionID, _reb2bloadedRB2B. The current visit, and a guard against loading the script twice. 30 minutes, 1 second.

Functional

On unless you turn it off. Remembers choices such as a collapsed section.

View cookies (none today)