Jeremy A. Rieks, PA-C

  • Englewood, CO
  • Physician assistant
NPI1154548824
Hospital affiliations
1
Medical group
1
State license
1
Year NPI issued
2007
Practice address
3425 S Clarkson St, Englewood, CO 80113
Practice phone
Call (303) 789-8000
Professional email
Get professional email
Personal email
Get personal email
Mobile number
Get mobile number
Social profiles

Primary practice

Craig Hospital

Hospital · Englewood, Colorado

Find Jeremy Rieks' professional email, personal email and mobile number

Dmand AI checks each channel through healthcare-specific waterfall enrichment. See what is on file with a free account, with practice phones, licenses and affiliations.

View contacts for free

Jeremy A. Rieks is a physician assistant in Englewood, Colorado

Jeremy Rieks practices at Craig Hospital in Englewood, Colorado, part of Craig Hospital.

Jeremy Rieks' NPI, 1154548824, was assigned on April 20, 2007. Jeremy Rieks holds Colorado license PA-1719.

NPI and contact details
NPI enumeration date
April 20, 2007
NPI status
Active
Practice phone
(303) 789-8000
Professional email
Get email
Personal email
Get email
Mobile number
Get number
Sex
Male

Sources: NPPES NPI Registry (CMS); Dmand AI Professional Profile Data; Dmand AI Affiliation Data; and Doctors and Clinicians National Downloadable File (CMS)

Jeremy A. Rieks practices at Craig Hospital in Englewood, Colorado

Jeremy Rieks' primary practice is Craig Hospital, at 3425 S Clarkson St, Englewood, CO 80113 in Arapahoe County. The practice phone is (303) 789-8000.

  • Craig Hospital
    3425 S Clarkson St, Englewood, CO 80113 · Arapahoe CountyPhone(303) 789-8000

Sources: Dmand AI Affiliation Data; and Doctors and Clinicians National Downloadable File (CMS)

Jeremy A. Rieks is affiliated with 1 site of care and 1 medical group

Jeremy Rieks' primary practice is Craig Hospital in Englewood, Colorado, part of Craig Hospital. The medical group on file is CNS Medical Group.

Sources: Dmand AI Affiliation Data; Doctors and Clinicians National Downloadable File (CMS); and Dmand AI Org Hierarchy Data

Dmand AI tracks the EHR system at Jeremy A. Rieks' practice

Dmand AI tracks the electronic health record (EHR) system at each site where Jeremy Rieks practices. Vendor and product names are available with a free account.

EHR by site
SiteEHR vendor and product
Craig HospitalAvailable with a free account

Source: Dmand AI Technology Install Data

For health IT teams

See the EHR and IT leaders at every hospital where Jeremy Rieks practices

Dmand AI maps EHR vendors, IT decision makers and buying committees across Craig Hospital and 6.2K+ hospitals, with verified contacts in the same login.

Jeremy A. Rieks is one of 1,042 physician assistants in Colorado

Medical is Jeremy Rieks' primary specialty in the NPI Registry, under taxonomy code 363AM0700X. Jeremy Rieks is licensed in Colorado.

Specialties and state licenses

  • Medical physician assistant, ColoradoPrimaryLicense PA-1719 · taxonomy 363AM0700X

Physician assistants near Jeremy Rieks

Counts of physician assistants with a Dmand AI profile, by place and practice. Each opens the list.

Sources: NPPES NPI Registry (CMS); Dmand AI Professional Profile Data; and Dmand AI Peer Benchmarks

Jeremy A. Rieks' patients have a median age of 37

Across all payers, Dmand AI patient panel data puts Jeremy Rieks' median patient age at 37, with 22% women.

Jeremy Rieks' patients across all payers

Dmand AI patient panel data covers Medicare, Medicaid and commercial patients.

Patient panel by age, all payers

Median age 37

Patient panel by sex, all payers

  • Women22%
  • Men77%

Source: Dmand AI Patient Panel Data

Sources for Jeremy A. Rieks's profile data

Sources for the data on this page
Data on this pageSource
NPI, name, sex, specialty and licensesNPPES NPI Registry (CMS) (opens in a new tab)Dmand AI Professional Profile Data
Practice locations and phoneDmand AI Affiliation DataDoctors and Clinicians National Downloadable File (CMS) (opens in a new tab)
Primary practice, affiliations and health systemDmand AI Affiliation DataDoctors and Clinicians National Downloadable File (CMS) (opens in a new tab)Dmand AI Org Hierarchy Data
Medicare patients and the all-payer patient panelDmand AI Patient Panel Data
EHR at each practice siteDmand AI Technology Install Data
Similar physiciansDmand AI Affiliation Data

Data last refreshed October 2026Report an inaccuracyRemove my information

FAQ

Frequently asked questions about Jeremy A. Rieks

Spotted something out of date? Email hello@dmand.ai and we will check the record. Contact details live in the free trial.

What is Jeremy A. Rieks' NPI number?

Jeremy A. Rieks' NPI number is 1154548824. It was assigned on April 20, 2007, and it is active in the NPI Registry.

What does Jeremy A. Rieks specialize in?

Jeremy A. Rieks is a physician assistant in Englewood, Colorado. The primary specialty in the NPI Registry is Medical Physician Assistant (taxonomy code 363AM0700X).

Where does Jeremy A. Rieks practice?

Jeremy Rieks practices at 3425 S Clarkson St, Englewood, CO 80113. Jeremy Rieks' primary practice is Craig Hospital in Englewood, Colorado, part of Craig Hospital.

What is Jeremy A. Rieks' office phone number?

The practice phone on file for Jeremy Rieks is (303) 789-8000.

What is Jeremy A. Rieks' medical license number?

Jeremy Rieks holds Colorado license PA-1719.

Which hospitals is Jeremy A. Rieks affiliated with?

Jeremy Rieks practices at Craig Hospital in Englewood, Colorado.

What medical group is Jeremy A. Rieks part of?

Jeremy Rieks is linked to CNS Medical Group.

How long has Jeremy A. Rieks been practicing?

Jeremy Rieks' NPI was assigned in 2007.

Selling to medical practices?

See physician assistants in Colorado by site of care and group

Find the practices, groups and hospitals they work with, and the right people to contact at each.

  • 30 days free
  • Self-serve
  • No credit card

Cookie settings

Turn each category on or off. Your choice is kept for 12 months and you can change it here at any time.

Necessary

Always on. Sign-in, security, downloads you asked for, your cookie choice, and the page that led to a signup.

View cookies (6)
  • dm_consentDmand AI. Your cookie choices and whether your browser sent a Global Privacy Control signal. 12 months.
  • dm_ft, dm_ltDmand AI. The first and the latest page you arrived on, with the date, so a signup is credited to the page that worked. 90 days, 30 days.
  • dm_fs, dm_lsDmand AI. The first and the latest source of a visit (a search engine, a campaign or the site that linked here). 90 days, 30 days.
  • dm_dl, dm_dl_okDmand AI. After you give an email address for a download, lets you download files without being asked again. 30 days.
  • Session and CSRF cookiesDmand AI (app.dmand.ai). Sign-in and form protection in the application. Session.
  • __cf_bm, cf_clearanceCloudflare. Tells people from automated traffic and keeps the site available. 30 minutes; cf_clearance while a security check is valid.

Analytics

On unless you turn it off. How pages are used, in aggregate, and recordings of how pages are used.

View cookies (6)
  • Google Tag ManagerGoogle. Loads the analytics and marketing tags that are on. Sets no cookie of its own and does not load when both categories are off. n/a.
  • _ga, _ga_<container-id>Google Analytics 4. Visits and page views in aggregate on dmand.ai. 2 years.
  • _clck, _clskMicrosoft Clarity. Recordings and heatmaps of how pages are used, with form fields masked. 1 year, 1 day.
  • CLID, MUID, ANONCHK, MR, SMMicrosoft (clarity.ms). Set by Microsoft when Clarity loads, to recognize a browser across sites that use Clarity. Up to 1 year.
  • None (cookieless)Ahrefs Analytics. Page views in aggregate. n/a.
  • ph_<project>_posthogPostHog. Product usage, errors and performance in app.dmand.ai, used to fix bugs and improve features. 365 days.

Marketing

On unless you turn it off, and always off when your browser sends a Global Privacy Control signal. A visitor identification service tells our sales team which companies and people visit.

View cookies (6)
  • _reb2buid, _reb2butkRB2B. Recognizes a returning browser for visitor identification. 360 days, 1 year.
  • _reb2bgeoRB2B. The location used to decide whether a visit can be identified. 20 days.
  • _reb2brefRB2B. The page or site that referred the visit. 15 days.
  • _reb2bfxf, _reb2btd, _reb2bliRB2B. Links the visit to an identified business profile. 1 month.
  • _reb2bresolveRB2B. Holds a match while it is being resolved. 2 days.
  • _reb2sessionID, _reb2bloadedRB2B. The current visit, and a guard against loading the script twice. 30 minutes, 1 second.

Functional

On unless you turn it off. Remembers choices such as a collapsed section.

View cookies (none today)