DR. JACOB L ARMANIOUS DDS
NPI 1841492626
Dentist in Daytona Beach, FL
About Dr. Jacob L Armanious Dds NPPES
Official registry information on file with the National Plan and Provider Enumeration System.
DR. JACOB L ARMANIOUS DDS (NPI 1841492626) is an individual dentist in Daytona Beach, Florida, licensed in Florida (8083) and active in the NPI registry since June 2007. He is enrolled in Medicare PECOS.
NPPES Registry Identity
Specialties & Licenses
Other Identifiers 1
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. Jacob L Armanious Dds 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 32118 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 Jacob Armanious's NPI number?
The NPI number for Jacob Armanious is 1841492626. It was assigned to this individual provider in the NPPES registry on June 4, 2007.
Where is Jacob Armanious located?
Jacob Armanious practices at 150 S Peninsula Dr, Daytona Beach, FL 32118. The listed phone number is (386) 253-7276.
What is Jacob Armanious's specialty?
The primary specialty registered for this NPI is Dentist with taxonomy code 122300000X.
Is Jacob Armanious enrolled in Medicare?
Yes. Jacob Armanious is registered in the Medicare PECOS enrollment system.
When was this NPI record last updated?
The NPPES record for Jacob Armanious was last updated on January 11, 2011. NPI Profile syncs weekly with the NPPES registry data releases published by CMS. This NPI record was last updated 15 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.