Jordan Lyman Dye, LCSW

  • Layton, UT
  • Clinical social worker
NPI1619232386
Affiliated sites
1
Medical group
1
State license
1
Year NPI issued
2012
Practice address
2950 N Church St, Layton, UT 84040
Practice phone
Call (801) 475-3000
Professional email
Get professional email
Personal email
Get personal email
Mobile number
Get mobile number
Social profiles

Primary practice

Ogden Clinic

Layton, Utah

See all 3 affiliations

Find Jordan Dye's 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

Jordan Lyman Dye is a clinical social worker in Layton, Utah

Jordan Dye practices at Ogden Clinic in Layton, Utah.

Jordan Dye's NPI, 1619232386, was assigned on July 9, 2012. Jordan Dye holds Utah license 117725763501.

NPI and contact details
NPI enumeration date
July 9, 2012
NPI status
Active
Practice phone
(801) 475-3000
Professional email
Get email
Personal email
Get email
Mobile number
Get number
Sex
Male
Estimated age
32
Medical school graduation
2020

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

Jordan Lyman Dye practices at Ogden Clinic in Layton, Utah

Jordan Dye's primary practice is Ogden Clinic, at 2950 N Church St, Layton, UT 84040 in Davis County. The practice phone is (801) 475-3000.

  • Ogden Clinic
    2950 N Church St, Layton, UT 84040 · Davis CountyPhone(801) 475-3000

Sources: NPPES NPI Registry (CMS); and Dmand AI Practice Data

Jordan Lyman Dye is affiliated with 2 sites of care and 1 medical group

Jordan Dye's primary practice is Ogden Clinic in Layton, Utah. The medical group on file is Rula Health. Dmand AI also links Jordan Dye to 1 more physician office, named with a free account.

See all 3 affiliations for Jordan Dye

Sources: NPPES NPI Registry (CMS); Dmand AI Practice Data; and Dmand AI Affiliation Data

Dmand AI tracks the EHR system at Jordan Lyman Dye's practice

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

EHR by site
SiteEHR vendor and product
Ogden ClinicAvailable with a free account
+1 more affiliated siteAvailable with a free account

Source: Dmand AI Technology Install Data

For health IT teams

See the EHR and IT leaders at every site where Jordan Dye practices

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

Jordan Lyman Dye is one of 1,456 clinical social workers in Utah

Social worker is Jordan Dye's primary specialty in the NPI Registry, under taxonomy code 1041C0700X. The record also lists clinical. Jordan Dye is licensed in Utah.

Specialties and state licenses

  • Clinical social worker, UtahPrimaryLicense 117725763501 · taxonomy 1041C0700X

Clinical social workers near Jordan Dye

Counts of clinical social workers 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

Jordan Lyman Dye's patients have a median age of 29

Across all payers, Dmand AI patient panel data puts Jordan Dye's median patient age at 29, with 29% women.

Jordan Dye's patients across all payers

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

Patient panel by age, all payers

Median age 29

Patient panel by sex, all payers

  • Women29%
  • Men71%

Source: Dmand AI Patient Panel Data

Sources for Jordan Lyman Dye'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 phoneNPPES NPI Registry (CMS) (opens in a new tab)Dmand AI Practice Data
Primary practice, affiliations and health systemNPPES NPI Registry (CMS) (opens in a new tab)Dmand AI Practice DataDmand AI Affiliation 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 Jordan Lyman Dye

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

What is Jordan Lyman Dye's NPI number?

Jordan Lyman Dye's NPI number is 1619232386. It was assigned on July 9, 2012, and it is active in the NPI Registry.

What does Jordan Lyman Dye specialize in?

Jordan Lyman Dye is a clinical social worker in Layton, Utah. The primary specialty in the NPI Registry is Clinical Social Worker (taxonomy code 1041C0700X).

Where does Jordan Lyman Dye practice?

Jordan Dye practices at 2950 N Church St, Layton, UT 84040. Jordan Dye's primary practice is Ogden Clinic in Layton, Utah. Dmand AI also links Jordan Dye to 1 physician office.

What is Jordan Lyman Dye's office phone number?

The practice phone on file for Jordan Dye is (801) 475-3000.

What is Jordan Lyman Dye's medical license number?

Jordan Dye holds Utah license 117725763501.

What medical group is Jordan Lyman Dye part of?

Jordan Dye is linked to Rula Health.

How long has Jordan Lyman Dye been practicing?

Jordan Dye graduated from medical school in 2020, 6 years ago.

Selling to social worker practices?

See clinical social workers in Utah 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)