DR. THOMAS ROGER PEAY PH.D.
NPI 1073791729
Counselor - Professional in Park City, UT
About Dr. Thomas Roger Peay Ph.d. NPPES
Official registry information on file with the National Plan and Provider Enumeration System.
DR. THOMAS ROGER PEAY PH.D. (NPI 1073791729) is an individual professional provider in Park City, Utah, licensed in Utah (113517-3902) and active in the NPI registry since February 2008. He is enrolled in Medicare PECOS.
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. Thomas Roger Peay Ph.d. 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 Thomas Peay's NPI number?
The NPI number for Thomas Peay is 1073791729. It was assigned to this individual provider in the NPPES registry on February 5, 2008.
Where is Thomas Peay located?
Thomas Peay practices at 2559 Aspen Springs Dr, Park City, UT 84060. The listed phone number is (801) 376-8775.
What is Thomas Peay's specialty?
The primary specialty registered for this NPI is Counselor, specializing in Professional, with taxonomy code 101YP2500X.
Is Thomas Peay enrolled in Medicare?
Yes. Thomas Peay is registered in the Medicare PECOS enrollment system.
What insurance does Thomas Peay accept?
Health plans from Providence Health Plan, Select Health and University of Utah Health Plans list Thomas Peay 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 Thomas Peay was last updated on February 5, 2008. NPI Profile syncs weekly with the NPPES registry data releases published by CMS. This NPI record was last updated 18 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.