CHRISTOPHER G ROGERS FNP
NPI 1730799214
Nurse Practitioner - Primary Care in Saint George, UT
About Christopher G Rogers Fnp NPPES
Official registry information on file with the National Plan and Provider Enumeration System.
CHRISTOPHER G ROGERS FNP (NPI 1730799214) is an individual primary care provider in Saint George, Utah, licensed in Utah (5638947-4405) and active in the NPI registry since August 2020. 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)
Christopher G Rogers Fnp 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 84790 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 Christopher Rogers's NPI number?
The NPI number for Christopher Rogers is 1730799214. It was assigned to this individual provider in the NPPES registry on August 9, 2020.
Where is Christopher Rogers located?
Christopher Rogers practices at 2306 E 3860 S, Saint George, UT 84790. The listed phone number is (435) 535-1668.
What is Christopher Rogers's specialty?
The primary specialty registered for this NPI is Nurse Practitioner, specializing in Primary Care, with taxonomy code 363LP2300X.
Is Christopher Rogers enrolled in Medicare?
Yes. Christopher Rogers is registered in the Medicare PECOS enrollment system.
When was this NPI record last updated?
The NPPES record for Christopher Rogers was last updated on October 23, 2024. NPI Profile syncs weekly with the NPPES registry data releases published by CMS. This NPI record was last updated 21 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.