DR. JEFFREY SCOTT CHASE M.D.
NPI 1417040668
Obstetrics & Gynecology - Reproductive Endocrinology in Horsham, PA
About Dr. Jeffrey Scott Chase M.d. NPPES
Official registry information on file with the National Plan and Provider Enumeration System.
DR. JEFFREY SCOTT CHASE M.D. (NPI 1417040668) is an individual reproductive endocrinology provider in Horsham, Pennsylvania, licensed in Pennsylvania (MD 019637E) and active in the NPI registry since October 2006. 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. Jeffrey Scott Chase M.d. 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 19044 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 Jeffrey Chase's NPI number?
The NPI number for Jeffrey Chase is 1417040668. It was assigned to this individual provider in the NPPES registry on October 2, 2006.
Where is Jeffrey Chase located?
Jeffrey Chase practices at 3 Barley Way, Horsham, PA 19044. The listed phone number is (215) 651-5599.
What is Jeffrey Chase's specialty?
The primary specialty registered for this NPI is Obstetrics & Gynecology, specializing in Reproductive Endocrinology, with taxonomy code 207VE0102X.
Is Jeffrey Chase enrolled in Medicare?
Yes. Jeffrey Chase is registered in the Medicare PECOS enrollment system.
When was this NPI record last updated?
The NPPES record for Jeffrey Chase was last updated on January 25, 2020. NPI Profile syncs weekly with the NPPES registry data releases published by CMS. This NPI record was last updated 6 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.