Phillip Jeffery Cook, NP

  • Tucson, AZ
  • Nurse practitioner
NPI1386041895PAC ID8325344807
Part D claims, 2024
6,263
Affiliated sites
3
Medical groups
2
State license
1
Year NPI issued
2014
Practice address
8050 East Lakeside Parkway, Tucson, AZ 85730
Practice phone
Call (520) 584-5820
Professional email
Get professional email
Personal email
Get personal email
Mobile number
Get mobile number
Social profiles

Primary practice

Lakeside Integrated Care Clinic

Outpatient Addiction Treatment · Tucson, Arizona

See all 5 affiliations

Find Phillip Cook'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

Phillip Jeffery Cook is a nurse practitioner in Tucson, Arizona

Phillip Cook practices at Lakeside Integrated Care Clinic in Tucson, Arizona.

Phillip Cook's NPI, 1386041895, was assigned on November 26, 2014. Phillip Cook holds Arizona license AP7480.

NPI and contact details
Medicare PAC ID
8325344807
NPI enumeration date
November 26, 2014
NPI status
Active
Accepts Medicare assignment
Yes
Practice phone
(520) 584-5820
Professional email
Get email
Personal email
Get email
Mobile number
Get number
Sex
Male
Estimated age
38
Medical school graduation
2014

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

Phillip Jeffery Cook practices at Lakeside Integrated Care Clinic in Tucson, Arizona

Phillip Cook's primary practice is Lakeside Integrated Care Clinic, at 8050 East Lakeside Parkway, Tucson, AZ 85730. The practice phone is (520) 584-5820.

  • Lakeside Integrated Care Clinic
    8050 East Lakeside Parkway, Tucson, AZ 85730Phone(520) 584-5820

Source: Dmand AI Affiliation Data

Phillip Jeffery Cook is affiliated with 3 sites of care and 2 medical groups

Phillip Cook's primary practice is Lakeside Integrated Care Clinic in Tucson, Arizona. The medical group on file is COPE Community Services, Inc. Dmand AI also links Phillip Cook to 2 more group practices and clinics and 1 medical group, each named with a free account. Phillip Cook's employer is on file too: a behavioral health center.

See all 5 affiliations for Phillip Cook

Sources: Dmand AI Affiliation Data; and Dmand AI Org Hierarchy Data

Dmand AI tracks the EHR system at Phillip Jeffery Cook's practice

Dmand AI tracks the electronic health record (EHR) system at each site where Phillip Cook practices, 3 sites in all. Vendor and product names are available with a free account.

EHR by site
SiteEHR vendor and product
Lakeside Integrated Care ClinicAvailable with a free account
+2 more sites and 1 medical groupAvailable with a free account

Source: Dmand AI Technology Install Data

For health IT teams

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

Phillip Jeffery Cook is one of 1,439 nurse practitioners in Arizona

Nurse practitioner is Phillip Cook's primary specialty in the NPI Registry, under taxonomy code 363L00000X. Phillip Cook is licensed in Arizona.

Specialties and state licenses

  • Nurse practitioner, ArizonaPrimaryLicense AP7480 · taxonomy 363L00000X

Nurse practitioners near Phillip Cook

Counts of nurse practitioners 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

Phillip Jeffery Cook's patients have a median age of 48

Across all payers, Dmand AI patient panel data puts Phillip Cook's median patient age at 48, with 48% women.

Phillip Cook's patients across all payers

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

Patient panel by age, all payers

Median age 48

Patient panel by sex, all payers

  • Women48%
  • Men51%

Source: Dmand AI Patient Panel Data

Phillip Jeffery Cook wrote 6,263 Medicare Part D claims in 2024

In 2024, Phillip Cook wrote 6,263 Medicare Part D claims for 147 patients. 88% of them were for generic drugs.

Part D claims, 20246,263
Part D patients147

Phillip Cook's Part D claims by kind of drug, 2024

  • Generic5,498 claims88%
  • Brand-name719 claims11%
  • Other46 claims1%

Drug classes CMS tracks in Phillip Cook's Part D claims, 2024

  • Opioids2%139 of 6,263 claims
  • Antibiotics2%109 of 6,263 claims
  • Antipsychotics, patients 65 and over5%332 of 6,263 claims

Share of all Part D claims for each drug class CMS reports on. Classes with no claims are left out.

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

How Phillip Jeffery Cook takes part in Medicare

Phillip Cook accepts Medicare assignment, so Medicare's approved amount is taken as full payment.

Accepts Medicare assignment
Yes

Source: Doctors and Clinicians National Downloadable File (CMS)

For MedTech and pharma teams

Find nurse practitioners like Phillip Cook 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.

Sources for Phillip Jeffery Cook'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 Data
Primary practice, affiliations and health systemDmand AI Affiliation DataDmand AI Org Hierarchy Data
Medicare patients and the all-payer patient panelDmand AI Patient Panel Data
Part D prescribingMedicare Part D Prescribers - by Provider (CMS) (opens in a new tab)
MIPS scores, telehealth, assignment and procedure percentilesDoctors and Clinicians National Downloadable File (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 Phillip Jeffery Cook

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

What is Phillip Jeffery Cook's NPI number?

Phillip Jeffery Cook's NPI number is 1386041895. It was assigned on November 26, 2014, and it is active in the NPI Registry.

What does Phillip Jeffery Cook specialize in?

Phillip Jeffery Cook is a nurse practitioner in Tucson, Arizona. The primary specialty in the NPI Registry is Nurse Practitioner (taxonomy code 363L00000X).

Where does Phillip Jeffery Cook practice?

Phillip Cook practices at 8050 East Lakeside Parkway, Tucson, AZ 85730. Phillip Cook's primary practice is Lakeside Integrated Care Clinic in Tucson, Arizona. Dmand AI also links Phillip Cook to 2 group practices and clinics and 1 medical group.

What is Phillip Jeffery Cook's office phone number?

The practice phone on file for Phillip Cook is (520) 584-5820.

What is Phillip Jeffery Cook's medical license number?

Phillip Cook holds Arizona license AP7480.

What medical group is Phillip Jeffery Cook part of?

Phillip Cook is linked to COPE Community Services, Inc. Dmand AI links Phillip Cook to 1 more medical group.

Does Phillip Jeffery Cook accept Medicare?

Yes. CMS lists Phillip Cook as accepting Medicare assignment.

How long has Phillip Jeffery Cook been practicing?

Phillip Cook graduated from medical school in 2014, 12 years ago.

Selling to nurse practitioner practices?

See nurse practitioners 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)