LAWRENCE A SEITZMAN MD
NPI 1760583058
Obstetrics & Gynecology - Gynecology in Edison, NJ
About Lawrence A Seitzman Md NPPES
Official registry information on file with the National Plan and Provider Enumeration System.
LAWRENCE A SEITZMAN MD (NPI 1760583058) is an individual gynecology provider in Edison, New Jersey, licensed in New Jersey (19392) and active in the NPI registry since September 2006. He is enrolled in Medicare PECOS.
NPPES Registry Identity
Specialties & Licenses
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)
Lawrence A Seitzman 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 08818 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 Lawrence Seitzman's NPI number?
The NPI number for Lawrence Seitzman is 1760583058. It was assigned to this individual provider in the NPPES registry on September 26, 2006.
Where is Lawrence Seitzman located?
Lawrence Seitzman practices at 799 Amboy Ave, Edison, NJ 08818. The listed phone number is (732) 738-7600.
What is Lawrence Seitzman's specialty?
The primary specialty registered for this NPI is Obstetrics & Gynecology, specializing in Gynecology, with taxonomy code 207VG0400X.
Is Lawrence Seitzman enrolled in Medicare?
Yes. Lawrence Seitzman is registered in the Medicare PECOS enrollment system.
When was this NPI record last updated?
The NPPES record for Lawrence Seitzman was last updated on July 8, 2007. NPI Profile syncs weekly with the NPPES registry data releases published by CMS. This NPI record was last updated 19 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.