DR. SAMUEL HADDAD DO
NPI 1407558984
Student in an Organized Health Care Education/Training Program in St Petersburg, FL
About Dr. Samuel Haddad Do NPPES
Official registry information on file with the National Plan and Provider Enumeration System.
DR. SAMUEL HADDAD DO (NPI 1407558984) is an individual student in an organized health care education/training program in St Petersburg, Florida and active in the NPI registry since March 2023. 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. Samuel Haddad Do is registered in the CMS Provider Enrollment, Chain and Ownership System (PECOS).
Other Providers at the Same Location NPPES 20
Providers registered at the same practice address, or within the immediate area, according to the NPPES registry.
ST PETERSBURG, FL 33710
ST PETERSBURG, FL 33710
ST PETERSBURG, FL 33710
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 Samuel Haddad's NPI number?
The NPI number for Samuel Haddad is 1407558984. It was assigned to this individual provider in the NPPES registry on March 20, 2023.
Where is Samuel Haddad located?
Samuel Haddad practices at 6500 38th Ave N, St Petersburg, FL 33710. The listed phone number is (727) 384-7727.
What is Samuel Haddad's specialty?
The primary specialty registered for this NPI is Student in an Organized Health Care Education/Training Program with taxonomy code 390200000X.
Is Samuel Haddad enrolled in Medicare?
Yes. Samuel Haddad is registered in the Medicare PECOS enrollment system.
When was this NPI record last updated?
The NPPES record for Samuel Haddad was last updated on March 20, 2023. NPI Profile syncs weekly with the NPPES registry data releases published by CMS. This NPI record was last updated 3 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.