Dr. James W. Ogilvie, MD

  • Salt Lake City, UT
  • Pediatric orthopaedic surgery physician
NPI1154497006
Part D claims, 2024
16
Publications
6
Industry payments
$2.7M
State license
1
Year NPI issued
2006
Practice address
5848 S Fashion Blvd, Salt Lake City, UT 84107
Practice phone
Call (801) 536-3600
Professional email
Get professional email
Personal email
Get personal email
Mobile number
Get mobile number
Social profiles

Find Dr. Ogilvie'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

Dr. James W. Ogilvie is a pediatric orthopaedic surgery physician in Salt Lake City, Utah

Dr. Ogilvie practices in Salt Lake City, Utah.

Dr. Ogilvie's NPI, 1154497006, was assigned on November 24, 2006. Dr. Ogilvie holds Utah license 150764-1205.

NPI and contact details
NPI enumeration date
November 24, 2006
NPI status
Active
Practice phone
(801) 536-3600
Professional email
Get email
Personal email
Get email
Mobile number
Get number
Sex
Male

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

Dr. James W. Ogilvie's practice address is in Salt Lake City, Utah

Dr. Ogilvie's practice address in the NPI Registry is 5848 S Fashion Blvd, Salt Lake City, UT 84107, in Salt Lake County. The practice phone is (801) 536-3600.

  • NPI Registry address
    5848 S Fashion Blvd, Salt Lake City, UT 84107 · Salt Lake CountyPhone(801) 536-3600

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

Dmand AI tracks the EHR system at Dr. James W. Ogilvie's practice

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

EHR by site
SiteEHR vendor and product
Dr. Ogilvie's practiceAvailable with a free account

Source: Dmand AI Technology Install Data

For health IT teams

See the EHR and IT leaders at every site where Dr. Ogilvie 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.

Dr. James W. Ogilvie is one of 12 pediatric orthopaedic surgery physicians in Utah

Pediatric orthopaedic surgery is Dr. Ogilvie's primary specialty in the NPI Registry, under taxonomy code 207XP3100X. Dr. Ogilvie is licensed in Utah.

Specialties and state licenses

  • Pediatric orthopaedic surgery, UtahPrimaryLicense 150764-1205 · taxonomy 207XP3100X

Pediatric orthopaedic surgery physicians near Dr. Ogilvie

Counts of pediatric orthopaedic surgery physicians 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

Dr. James W. Ogilvie wrote 16 Medicare Part D claims in 2024

In 2024, Dr. Ogilvie wrote 16 Medicare Part D claims.

Part D claims, 202416

Source: Medicare Part D Prescribers - by Provider (CMS), 2024 data

For MedTech and pharma teams

Find pediatric orthopaedic surgery physicians like Dr. Ogilvie by procedure volume and prescribing

Filter 7.4M+ HCPs by Medicare procedures, Part D drugs and Open Payments history, then reach them with verified contacts in one login.

Dr. James W. Ogilvie has 6 publications on record

Dmand AI links 6 papers to Dr. Ogilvie, published from 2010 to 2015. The most frequent topics are Scoliosis, Genetic Association Studies and Genetic Predisposition to Disease. Dr. Ogilvie has published most often in Spine (Phila Pa 1976). Dr. Ogilvie's most frequent co-authors are David W. Polly, MD and Kenneth Ward, MD.

Papers6
Years published2010 to 2015

Topics Dr. Ogilvie writes about most

  • Scoliosis
  • Genetic Association Studies
  • Genetic Predisposition to Disease
  • Genotype
  • Phenotype
  • Polymorphism, Single Nucleotide
  • White People

Dr. Ogilvie's most frequent co-authors

Recent publications by Dr. Ogilvie

See all 6 publications and co-authors

See who Dr. Ogilvie researches with

Physician Network Discovery turns co-authorship, shared hospitals and shared groups into a map of who Dr. Ogilvie works with, so you can find a warm path to the right pediatric orthopaedic surgery physicians.

How network discovery works

Sources: PubMed (National Library of Medicine); and Dmand AI Research Linkage

Dr. James W. Ogilvie received $2,746,148 in industry payments from 2016 to 2025

CMS Open Payments shows 119 general payments to Dr. Ogilvie from 4 drug and device companies from 2016 to 2025. Royalties and licenses make up the largest share, 100% of the total. Medtronic USA, Inc. paid the most, $2,041,155.

General payments to Dr. Ogilvie by program year, 2016 to 2025

General payments to Dr. Ogilvie by kind, 2016 to 2025

$2.7Min total
  • Royalties and licenses$2,746,135100%
  • Food and beverage$130%

Companies that paid Dr. Ogilvie the most, 2016 to 2025

Share is of all general payments to this clinician.

See all payments to Dr. Ogilvie

Source: Open Payments (CMS), 2025 data, released July 7, 2026

Sources for Dr. James W. Ogilvie'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
Part D prescribingMedicare Part D Prescribers - by Provider (CMS) (opens in a new tab)
Publications, topics and co-authorsPubMed (National Library of Medicine) (opens in a new tab)Dmand AI Research Linkage
Industry paymentsOpen Payments (CMS) (opens in a new tab)
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 Dr. James W. Ogilvie

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

What is Dr. James W. Ogilvie's NPI number?

Dr. James W. Ogilvie's NPI number is 1154497006. It was assigned on November 24, 2006, and it is active in the NPI Registry.

What kind of doctor is Dr. James W. Ogilvie?

Dr. James W. Ogilvie is a pediatric orthopaedic surgery physician in Salt Lake City, Utah. The primary specialty in the NPI Registry is Pediatric Orthopaedic Surgery Physician (taxonomy code 207XP3100X).

Where does Dr. James W. Ogilvie practice?

Dr. Ogilvie practices at 5848 S Fashion Blvd, Salt Lake City, UT 84107.

What is Dr. James W. Ogilvie's office phone number?

The practice phone on file for Dr. Ogilvie is (801) 536-3600.

What is Dr. James W. Ogilvie's medical license number?

Dr. Ogilvie holds Utah license 150764-1205.

Has Dr. James W. Ogilvie received payments from drug or device companies?

CMS Open Payments shows $2,746,148 in general payments to Dr. Ogilvie from 4 companies from 2016 to 2025. The largest total came from Medtronic USA, Inc.

How long has Dr. James W. Ogilvie been practicing?

Dr. Ogilvie's NPI was assigned in 2006.

Does Dr. James W. Ogilvie do research?

Dmand AI links 6 publications to Dr. Ogilvie, published from 2010 to 2015.

Who does Dr. James W. Ogilvie publish with?

Dr. Ogilvie's most frequent co-authors are David W. Polly, MD (1 shared paper) and Kenneth Ward, MD (1 shared paper).

Selling to pediatric orthopaedic surgery practices?

See pediatric orthopaedic surgery physicians 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)