DYLAN STAHLY
NPI 1174267587
Physician Assistant in Sioux Falls, SD
About Dylan Stahly NPPES
Official registry information on file with the National Plan and Provider Enumeration System.
DYLAN STAHLY (NPI 1174267587) is an individual physician assistant in Sioux Falls, South Dakota and active in the NPI registry since April 2022. He is enrolled in Medicare PECOS.
NPPES Registry Identity
Specialties & Licenses 2
Medicare Participation & PECOS CMS
Medicare enrollment, assignment, and ordering and referring status from the CMS PECOS system.
Medicare Enrollment Status
Enrolled in Medicare (PECOS)
Dylan Stahly is registered in the CMS Provider Enrollment, Chain and Ownership System (PECOS).
Physician Visit Costs CMS claims · ZIP area
Typical Medicare office-visit costs in the 57104 ZIP code area, from fee-for-service claims. These are area statistics, not this provider’s prices; actual charges vary by service and coverage.
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.
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 Dylan Stahly's NPI number?
The NPI number for Dylan Stahly is 1174267587. It was assigned to this individual provider in the NPPES registry on April 21, 2022.
Where is Dylan Stahly located?
Dylan Stahly practices at 1210 W 18th St Ste 100, Sioux Falls, SD 57104. The listed phone number is (605) 312-8500.
What is Dylan Stahly's specialty?
The primary specialty registered for this NPI is Physician Assistant with taxonomy code 363A00000X.
Is Dylan Stahly enrolled in Medicare?
Yes. Dylan Stahly is registered in the Medicare PECOS enrollment system.
When was this NPI record last updated?
The NPPES record for Dylan Stahly was last updated on January 24, 2024. NPI Profile syncs weekly with the NPPES registry data releases published by CMS. This NPI record was last updated 2 years 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.