DR. TROY L MANCHESTER M.D.
NPI 1689692139
General Practice in Longmont, CO
About Dr. Troy L Manchester M.d. NPPES
Official registry information on file with the National Plan and Provider Enumeration System.
DR. TROY L MANCHESTER M.D. (NPI 1689692139) is an individual general practice provider in Longmont, Colorado, licensed in Colorado (DR.0062776) and active in the NPI registry since July 2006. He is enrolled in Medicare PECOS and is a graduate of University Of Arizona College Of Medicine (1996).
NPPES Registry Identity
Specialties & Licenses 2
Medicare Participation & PECOS CMS
Medicare enrollment, assignment, and ordering and referring status from the CMS PECOS system.
Medicare Enrollment Status
Enrolled in Medicare and accepts Medicare assignment
Dr. Troy L Manchester M.d. is registered in PECOS and agrees to accept the Medicare-approved amount as full payment. Medicare patients are not billed beyond the standard deductible and coinsurance.
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 Troy Manchester's NPI number?
The NPI number for Troy Manchester is 1689692139. It was assigned to this individual provider in the NPPES registry on July 17, 2006.
Where is Troy Manchester located?
Troy Manchester practices at 1860 Industrial Cir Ste 2, Longmont, CO 80501. The listed phone number is (303) 682-2473.
What is Troy Manchester's specialty?
The primary specialty registered for this NPI is General Practice with taxonomy code 208D00000X.
Is Troy Manchester enrolled in Medicare?
Yes. Troy Manchester is registered in the Medicare PECOS system and accepts Medicare assignment, which means accepting the Medicare-approved amount as payment in full for covered services.
When was this NPI record last updated?
The NPPES record for Troy Manchester was last updated on June 2, 2026. NPI Profile syncs weekly with the NPPES registry data releases published by CMS. This NPI record was last updated 2 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.