Steven E. Cox, CRNP

  • Wetumpka, AL
  • Nurse practitioner
NPI1962434027
Hospital affiliations
1
Medical group
1
State license
1
Year NPI issued
2006
Practice address
500 Hospital Drive, Wetumpka, AL 36092
Practice phone
Call (334) 567-4311
Professional email
Get professional email
Personal email
Get personal email
Mobile number
Get mobile number
Social profiles

Primary practice

Elmore Community Hospital

Hospital · Wetumpka, Alabama

See all 3 affiliations

Find Steven Cox'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

Steven E. Cox is a nurse practitioner in Wetumpka, Alabama

Steven Cox practices at Elmore Community Hospital in Wetumpka, Alabama, part of Ivy Creek Healthcare.

Steven Cox's NPI, 1962434027, was assigned on July 7, 2006. Steven Cox holds Alabama license 1042662.

NPI and contact details
NPI enumeration date
July 7, 2006
NPI status
Active
Practice phone
(334) 567-4311
Professional email
Get email
Personal email
Get email
Mobile number
Get number
Sex
Male

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

Steven E. Cox practices at Elmore Community Hospital in Wetumpka, Alabama

Steven Cox's primary practice is Elmore Community Hospital, at 500 Hospital Drive, Wetumpka, AL 36092 in Elmore County. The practice phone is (334) 567-4311.

Source: Dmand AI Affiliation Data

Steven E. Cox is affiliated with 2 sites of care and 1 medical group

Steven Cox's primary practice is Elmore Community Hospital in Wetumpka, Alabama, part of Ivy Creek Healthcare. The medical group on file is Ivy Creek Family Care of Tallassee. Dmand AI also links Steven Cox to 1 more home health agency, named with a free account. Steven Cox's employer is on file too: a hospital.

See all 3 affiliations for Steven Cox

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

Dmand AI tracks the EHR system at Steven E. Cox's practice

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

EHR by site
SiteEHR vendor and product
Elmore Community HospitalAvailable 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 hospital where Steven Cox practices

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

Steven E. Cox is one of 1,110 nurse practitioners in Alabama

Nurse practitioner is Steven Cox's primary specialty in the NPI Registry, under taxonomy code 363L00000X. Steven Cox is licensed in Alabama.

Specialties and state licenses

  • Nurse practitioner, AlabamaPrimaryLicense 1042662 · taxonomy 363L00000X

Nurse practitioners near Steven Cox

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

Steven E. Cox's patients have a median age of 41

Across all payers, Dmand AI patient panel data puts Steven Cox's median patient age at 41, with 0% women.

Steven Cox's patients across all payers

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

Patient panel by age, all payers

Median age 41

Patient panel by sex, all payers

  • Women0%
  • Men100%

Source: Dmand AI Patient Panel Data

Sources for Steven E. Cox'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
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 Steven E. Cox

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

What is Steven E. Cox's NPI number?

Steven E. Cox's NPI number is 1962434027. It was assigned on July 7, 2006, and it is active in the NPI Registry.

What does Steven E. Cox specialize in?

Steven E. Cox is a nurse practitioner in Wetumpka, Alabama. The primary specialty in the NPI Registry is Nurse Practitioner (taxonomy code 363L00000X).

Where does Steven E. Cox practice?

Steven Cox practices at 500 Hospital Drive, Wetumpka, AL 36092. Steven Cox's primary practice is Elmore Community Hospital in Wetumpka, Alabama, part of Ivy Creek Healthcare. Dmand AI also links Steven Cox to 1 home health agency.

What is Steven E. Cox's office phone number?

The practice phone on file for Steven Cox is (334) 567-4311.

What is Steven E. Cox's medical license number?

Steven Cox holds Alabama license 1042662.

Which hospitals is Steven E. Cox affiliated with?

Steven Cox practices at Elmore Community Hospital in Wetumpka, Alabama.

What medical group is Steven E. Cox part of?

Steven Cox is linked to Ivy Creek Family Care of Tallassee.

How long has Steven E. Cox been practicing?

Steven Cox's NPI was assigned in 2006.

Selling to nurse practitioner practices?

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