DR. GIORGIO T DIVINCENZO DMD
NPI 1396852679
Dentist - Periodontics in Jersey City, NJ
About Dr. Giorgio T Divincenzo Dmd NPPES
Official registry information on file with the National Plan and Provider Enumeration System.
DR. GIORGIO T DIVINCENZO DMD (NPI 1396852679) is an individual periodontics provider in Jersey City, New Jersey, licensed in New Jersey (17226) and active in the NPI registry since August 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. Giorgio T Divincenzo Dmd 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 07306 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 Giorgio Divincenzo's NPI number?
The NPI number for Giorgio Divincenzo is 1396852679. It was assigned to this individual provider in the NPPES registry on August 24, 2006.
Where is Giorgio Divincenzo located?
Giorgio Divincenzo practices at 312 Academy Street, Jersey City, NJ 07306. The listed phone number is (201) 216-9191.
What is Giorgio Divincenzo's specialty?
The primary specialty registered for this NPI is Dentist, specializing in Periodontics, with taxonomy code 1223P0300X.
Is Giorgio Divincenzo enrolled in Medicare?
Yes. Giorgio Divincenzo is registered in the Medicare PECOS enrollment system.
When was this NPI record last updated?
The NPPES record for Giorgio Divincenzo was last updated on June 16, 2014. NPI Profile syncs weekly with the NPPES registry data releases published by CMS. This NPI record was last updated 12 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.