GLENN ROBERT STEHMAN DO
NPI 1457419053
Internal Medicine - Cardiovascular Disease in Voorhees, NJ
About Glenn Robert Stehman Do NPPES
Official registry information on file with the National Plan and Provider Enumeration System.
GLENN ROBERT STEHMAN DO (NPI 1457419053) is an individual cardiovascular disease provider in Voorhees, New Jersey, licensed in New Jersey (25MB03812800) and active in the NPI registry since December 2006. He is enrolled in Medicare PECOS.
NPPES Registry Identity
Specialties & Licenses
Other Identifiers 3
Medicare Participation & PECOS CMS
Medicare enrollment, assignment, and ordering and referring status from the CMS PECOS system.
Medicare Enrollment Status
Enrolled in Medicare (PECOS)
Glenn Robert Stehman Do 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 08043 ZIP code area, from fee-for-service claims. These are area statistics, not this provider’s prices; actual charges vary by service and coverage.
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 Glenn Stehman's NPI number?
The NPI number for Glenn Stehman is 1457419053. It was assigned to this individual provider in the NPPES registry on December 5, 2006.
Where is Glenn Stehman located?
Glenn Stehman practices at 15 Dutchtown Rd, Voorhees, NJ 08043. The listed phone number is (856) 753-8062.
What is Glenn Stehman's specialty?
The primary specialty registered for this NPI is Internal Medicine, specializing in Cardiovascular Disease, with taxonomy code 207RC0000X.
Is Glenn Stehman enrolled in Medicare?
Yes. Glenn Stehman is registered in the Medicare PECOS enrollment system.
When was this NPI record last updated?
The NPPES record for Glenn Stehman was last updated on December 13, 2012. NPI Profile syncs weekly with the NPPES registry data releases published by CMS. This NPI record was last updated 13 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.