DR. KEVIN ANDREW STIERER SR. MD
NPI 1811073695
Anesthesiology in Baltimore, MD
About Dr. Kevin Andrew Stierer Sr. Md NPPES
Official registry information on file with the National Plan and Provider Enumeration System.
DR. KEVIN ANDREW STIERER SR. MD (NPI 1811073695) is an individual anesthesiology provider in Baltimore, Maryland, licensed in Pennsylvania (MD457549) and active in the NPI registry since October 2006. He is enrolled in Medicare PECOS and maintains a secondary practice location in Hershey.
NPPES Registry Identity
Specialties & Licenses
Secondary Practice Location 1
Other Identifiers 4
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. Kevin Andrew Stierer Sr. Md is registered in the CMS Provider Enrollment, Chain and Ownership System (PECOS).
Other Providers at the Same Location NPPES 19
Providers registered at the same practice address, or within the immediate area, according to the NPPES registry.
BALTIMORE, MD 21201
BALTIMORE, MD 21201
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 Kevin Stierer's NPI number?
The NPI number for Kevin Stierer is 1811073695. It was assigned to this individual provider in the NPPES registry on October 27, 2006.
Where is Kevin Stierer located?
Kevin Stierer practices at 22 S Greene St Fl 11, Baltimore, MD 21201. The listed phone number is (667) 214-1616.
What is Kevin Stierer's specialty?
The primary specialty registered for this NPI is Anesthesiology with taxonomy code 207L00000X.
Is Kevin Stierer enrolled in Medicare?
Yes. Kevin Stierer is registered in the Medicare PECOS enrollment system.
When was this NPI record last updated?
The NPPES record for Kevin Stierer was last updated on April 27, 2026. NPI Profile syncs weekly with the NPPES registry data releases published by CMS. This NPI record was last updated 3 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.