DR. JEREMY MARK GILILLAND MD
NPI 1881849669
Orthopaedic Surgery in Salt Lake City, UT
About Dr. Jeremy Mark Gililland Md NPPES
Official registry information on file with the National Plan and Provider Enumeration System.
DR. JEREMY MARK GILILLAND MD (NPI 1881849669) is an individual orthopaedic surgery provider in Salt Lake City, Utah, licensed in Utah (7151934-1205) and active in the NPI registry since November 2008. He is enrolled in Medicare PECOS, is affiliated with William Bee Ririe Hospital, and is a graduate of University Of California, Irvine, California College Of Medicine (2007).
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 and accepts Medicare assignment
Dr. Jeremy Mark Gililland Md 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.
Areas of Expertise CMS Part B claims 10
Services this provider delivered to Medicare fee-for-service patients, from the CMS Medicare utilization data. Higher counts generally reflect more experience with a service; care delivered outside Medicare is not included.
Hospital Affiliations CMS Care Compare 2
Hospitals where this provider delivers care, identified from recent Medicare claims and place-of-service records.
William Bee Ririe Hospital
Critical Access Hospitals · Ely, NVUniversity Of Utah Hospitals And Clinics
Acute Care Hospitals · Salt Lake City, UTPhysician Visit Costs CMS claims · ZIP area
Typical Medicare office-visit costs in the 84108 ZIP code area, from fee-for-service claims. These are area statistics, not this provider’s prices; actual charges vary by service and coverage.
Medicare Quality Performance CMS QPP · MIPS
Performance in the CMS Quality Payment Program: the MIPS final score across four weighted categories, and the individual quality measures reported to Medicare.
Reported Quality Measures
Referred Medical Equipment & Supplies CMS DME claims
Durable medical equipment, devices and supplies this provider ordered from DME suppliers for patients, from Medicare fee-for-service claims.
Other Providers at the Same Location NPPES 20
Providers registered at the same practice address, or within the immediate area, according to the NPPES registry.
SALT LAKE CITY, UT 84108
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 Jeremy Gililland's NPI number?
The NPI number for Jeremy Gililland is 1881849669. It was assigned to this individual provider in the NPPES registry on November 20, 2008.
Where is Jeremy Gililland located?
Jeremy Gililland practices at 590 S Wakara Way, Salt Lake City, UT 84108. The listed phone number is (801) 587-7100.
What is Jeremy Gililland's specialty?
The primary specialty registered for this NPI is Orthopaedic Surgery with taxonomy code 207X00000X.
Is Jeremy Gililland enrolled in Medicare?
Yes. Jeremy Gililland 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.
What insurance does Jeremy Gililland accept?
Health plans from BridgeSpan Health Company, Molina Healthcare, Regence BlueCross BlueShield of Utah and University of Utah Health Plans list Jeremy Gililland 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.
Is Jeremy Gililland affiliated with any hospitals?
According to CMS data, Jeremy Gililland is affiliated with William Bee Ririe Hospital and University Of Utah Hospitals And Clinics.
When was this NPI record last updated?
The NPPES record for Jeremy Gililland was last updated on November 1, 2021. NPI Profile syncs weekly with the NPPES registry data releases published by CMS. This NPI record was last updated 4 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.