ALEX GREGORY TAMIRIAN APN
NPI 1801749122
Nurse Practitioner - Psychiatric/Mental Health in Allendale, NJ
About Alex Gregory Tamirian Apn NPPES
Official registry information on file with the National Plan and Provider Enumeration System.
ALEX GREGORY TAMIRIAN APN (NPI 1801749122) is an individual psychiatric/mental health provider in Allendale, New Jersey, licensed in New Jersey (26NJ15509400) and active in the NPI registry since February 2026. 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)
Alex Gregory Tamirian Apn 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 07401 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 Alex Tamirian's NPI number?
The NPI number for Alex Tamirian is 1801749122. It was assigned to this individual provider in the NPPES registry on February 17, 2026.
Where is Alex Tamirian located?
Alex Tamirian practices at 55 Meeker Ave, Allendale, NJ 07401. The listed phone number is (201) 779-8527.
What is Alex Tamirian's specialty?
The primary specialty registered for this NPI is Nurse Practitioner, specializing in Psychiatric/Mental Health, with taxonomy code 363LP0808X.
Is Alex Tamirian enrolled in Medicare?
Yes. Alex Tamirian is registered in the Medicare PECOS enrollment system.
When was this NPI record last updated?
The NPPES record for Alex Tamirian was last updated on February 17, 2026. NPI Profile syncs weekly with the NPPES registry data releases published by CMS. This NPI record was last updated 7 months 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.