DR. JERIMYA MATTHEW FOX LPC
NPI 1639664113
Counselor - Professional in Tucson, AZ
About Dr. Jerimya Matthew Fox Lpc NPPES
Official registry information on file with the National Plan and Provider Enumeration System.
DR. JERIMYA MATTHEW FOX LPC (NPI 1639664113) is an individual professional provider in Tucson, Arizona, licensed in Arizona (LPC-16463) and active in the NPI registry since June 2018. He is enrolled in Medicare PECOS and is a graduate of Other (2012).
NPPES Registry Identity
Specialties & Licenses
Accepted Insurance
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. Jerimya Matthew Fox Lpc is registered in the CMS Provider Enrollment, Chain and Ownership System (PECOS).
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 Jerimya Fox's NPI number?
The NPI number for Jerimya Fox is 1639664113. It was assigned to this individual provider in the NPPES registry on June 26, 2018.
Where is Jerimya Fox located?
Jerimya Fox practices at 4621 N 1st Ave Ste 7, Tucson, AZ 85718. The listed phone number is (520) 975-7946.
What is Jerimya Fox's specialty?
The primary specialty registered for this NPI is Counselor, specializing in Professional, with taxonomy code 101YP2500X.
Is Jerimya Fox enrolled in Medicare?
Yes. Jerimya Fox is registered in the Medicare PECOS enrollment system.
What insurance does Jerimya Fox accept?
Health plans from Blue Cross Blue Shield of Arizona, Oscar Health Plan, Inc. and UnitedHealthcare list Jerimya Fox as in-network in at least one marketplace plan. Coverage varies by plan and year; verify with the insurer or the provider before a visit.
When was this NPI record last updated?
The NPPES record for Jerimya Fox was last updated on June 26, 2018. NPI Profile syncs weekly with the NPPES registry data releases published by CMS. This NPI record was last updated 8 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.