DR. LUKE FARSON MD
NPI 1407650856
Student in an Organized Health Care Education/Training Program in Dallas, TX
About Dr. Luke Farson Md NPPES
Official registry information on file with the National Plan and Provider Enumeration System.
DR. LUKE FARSON MD (NPI 1407650856) is an individual student in an organized health care education/training program in Dallas, Texas and active in the NPI registry since April 2025. He is enrolled in Medicare PECOS.
NPPES Registry Identity
Specialties & Licenses
Medicare Participation & PECOS CMS
Medicare enrollment, assignment, and ordering and referring status from the CMS PECOS system.
Medicare Enrollment Status
Enrolled in Medicare (PECOS)
Dr. Luke Farson Md is registered in the CMS Provider Enrollment, Chain and Ownership System (PECOS).
Other Providers at the Same Location NPPES 20
Providers registered at the same practice address, or within the immediate area, according to the NPPES registry.
DALLAS, TX 75390
DALLAS, TX 75390
DALLAS, TX 75390
DALLAS, TX 75390
DALLAS, TX 75390
DALLAS, TX 75390
DALLAS, TX 75390
Frequently Asked Questions NPPES & CMS
Common questions about this NPI record, answered from the official NPPES registry and CMS datasets shown on this page.
What is Luke Farson's NPI number?
The NPI number for Luke Farson is 1407650856. It was assigned to this individual provider in the NPPES registry on April 3, 2025.
Where is Luke Farson located?
Luke Farson practices at 5323 Harry Hines Blvd Stop 7200, Dallas, TX 75390. The listed phone number is (214) 648-3433.
What is Luke Farson's specialty?
The primary specialty registered for this NPI is Student in an Organized Health Care Education/Training Program with taxonomy code 390200000X.
Is Luke Farson enrolled in Medicare?
Yes. Luke Farson is registered in the Medicare PECOS enrollment system.
When was this NPI record last updated?
The NPPES record for Luke Farson was last updated on June 15, 2026. NPI Profile syncs weekly with the NPPES registry data releases published by CMS. This NPI record was last updated 2 months ago. If this record has changed at CMS more recently, you can request an on-demand re-check against the live CMS registry, directly from this page.