NITSANA A SPIGLAND MD
NPI 1710074802
Surgery in New York, NY
About Nitsana A Spigland Md NPPES
Official registry information on file with the National Plan and Provider Enumeration System.
NITSANA A SPIGLAND MD (NPI 1710074802) is an individual surgery provider in New York, New York, licensed in New York (170863) and active in the NPI registry since October 2006. She is enrolled in Medicare PECOS.
NPPES Registry Identity
Specialties & Licenses 2
Other Identifiers 3
Medicare Participation & PECOS CMS
Medicare enrollment, assignment, and ordering and referring status from the CMS PECOS system.
Medicare Enrollment Status
Enrolled in Medicare (PECOS)
Nitsana A Spigland Md 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 10021 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 Nitsana Spigland's NPI number?
The NPI number for Nitsana Spigland is 1710074802. It was assigned to this individual provider in the NPPES registry on October 9, 2006.
Where is Nitsana Spigland located?
Nitsana Spigland practices at 525 E 68th St # F-763, New York, NY 10021. The listed phone number is (212) 746-5648.
What is Nitsana Spigland's specialty?
The primary specialty registered for this NPI is Surgery with taxonomy code 208600000X.
Is Nitsana Spigland enrolled in Medicare?
Yes. Nitsana Spigland is registered in the Medicare PECOS enrollment system.
When was this NPI record last updated?
The NPPES record for Nitsana Spigland was last updated on September 19, 2011. NPI Profile syncs weekly with the NPPES registry data releases published by CMS. This NPI record was last updated 14 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.