DR. JEFFREY ALAN GRIFFIN D.O.
NPI 1235661182
Surgery in Langley, VA
About Dr. Jeffrey Alan Griffin D.o. NPPES
Official registry information on file with the National Plan and Provider Enumeration System.
DR. JEFFREY ALAN GRIFFIN D.O. (NPI 1235661182) is an individual surgery provider in Langley, Virginia, licensed in Texas (T6245) and active in the NPI registry since March 2017. He is enrolled in Medicare PECOS and maintains 2 additional practice locations.
NPPES Registry Identity
Specialties & Licenses
Secondary Practice Locations 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)
Dr. Jeffrey Alan Griffin D.o. 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 23669 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 Griffin's NPI number?
The NPI number for Jeffrey Griffin is 1235661182. It was assigned to this individual provider in the NPPES registry on March 30, 2017.
Where is Jeffrey Griffin located?
Jeffrey Griffin practices at 633D Medical Group 77 Nealy Ave, Langley, VA 23669. The listed phone number is (757) 764-1957.
What is Jeffrey Griffin's specialty?
The primary specialty registered for this NPI is Surgery with taxonomy code 208600000X.
Is Jeffrey Griffin enrolled in Medicare?
Yes. Jeffrey Griffin is registered in the Medicare PECOS enrollment system.
When was this NPI record last updated?
The NPPES record for Jeffrey Griffin was last updated on January 18, 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.