Dr. Patrick J. O'Connor, MD

  • Tucson, AZ
  • Pediatrician
NPI1679507198
Medical group
1
State licenses
2
Year NPI issued
2006
Practice address
7490 S Camino De Oeste, Tucson, AZ 85746
Practice phone
Call (520) 295-2406
Professional email
Get professional email
Personal email
Get personal email
Mobile number
Get mobile number
Social profiles

Medical group

Tuba City Regional Health

Tuba City, Arizona

Find Dr. O'Connor'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. Patrick J. O'Connor is a pediatrician in Tucson, Arizona

Dr. O'Connor practices with Tuba City Regional Health, a medical group.

Dr. O'Connor's NPI, 1679507198, was assigned on July 10, 2006. Dr. O'Connor holds Arizona license 42989.

NPI and contact details
NPI enumeration date
July 10, 2006
NPI status
Active
Practice phone
(520) 295-2406
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. Patrick J. O'Connor's practice address is in Tucson, Arizona

Dr. O'Connor's practice address in the NPI Registry is 7490 S Camino De Oeste, Tucson, AZ 85746, in Pima County. The practice phone is (520) 295-2406.

  • NPI Registry address
    7490 S Camino De Oeste, Tucson, AZ 85746 · Pima CountyPhone(520) 295-2406

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

Dr. Patrick J. O'Connor is affiliated with 1 medical group

Dr. O'Connor is part of Tuba City Regional Health, a medical group in Tuba City, Arizona.

Source: Dmand AI Affiliation Data

Dmand AI tracks the EHR system at Dr. Patrick J. O'Connor's practice

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

EHR by site
SiteEHR vendor and product
Tuba City Regional HealthAvailable 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. O'Connor practices

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

Dr. Patrick J. O'Connor is one of 1,000 pediatricians in Arizona

Pediatrics is Dr. O'Connor's primary specialty in the NPI Registry, under taxonomy code 208000000X. Dmand AI has Dr. O'Connor's licenses on file in 2 states: Arizona and Wisconsin.

Specialties and state licenses

  • Pediatrics, ArizonaPrimaryLicense 42989 · taxonomy 208000000X
  • Wisconsin licenseLicense 28955

Pediatricians near Dr. O'Connor

Counts of pediatricians 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. Patrick J. O'Connor's patients have a median age of 42

Across all payers, Dmand AI patient panel data puts Dr. O'Connor's median patient age at 42, with 67% women.

Dr. O'Connor's patients across all payers

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

Patient panel by age, all payers

Median age 42

Patient panel by sex, all payers

  • Women67%
  • Men33%

Source: Dmand AI Patient Panel Data

Sources for Dr. Patrick J. O'Connor'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 systemDmand 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 Dr. Patrick J. O'Connor

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. Patrick J. O'Connor's NPI number?

Dr. Patrick J. O'Connor's NPI number is 1679507198. It was assigned on July 10, 2006, and it is active in the NPI Registry.

What kind of doctor is Dr. Patrick J. O'Connor?

Dr. Patrick J. O'Connor is a pediatrician in Tucson, Arizona. The primary specialty in the NPI Registry is Pediatrics Physician (taxonomy code 208000000X).

Where does Dr. Patrick J. O'Connor practice?

Dr. O'Connor practices at 7490 S Camino De Oeste, Tucson, AZ 85746. Dr. O'Connor's primary practice is Tuba City Regional Health, a medical group.

What is Dr. Patrick J. O'Connor's office phone number?

The practice phone on file for Dr. O'Connor is (520) 295-2406.

What is Dr. Patrick J. O'Connor's medical license number?

Dr. O'Connor holds Arizona license 42989, one of the licenses on file in 2 states.

Which states has Dr. Patrick J. O'Connor been licensed in?

Dmand AI has state licenses on file for Dr. O'Connor in Arizona and Wisconsin.

What medical group is Dr. Patrick J. O'Connor part of?

Dr. O'Connor is part of Tuba City Regional Health in Tuba City, Arizona.

How long has Dr. Patrick J. O'Connor been practicing?

Dr. O'Connor's NPI was assigned in 2006.

Selling to pediatrics practices?

See pediatricians in Arizona 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)