Log inBook a demoStart free trial
Log inStart free trial

Destiny Ayala, LCSW

  • Meriden, CT
  • Clinical social worker
NPI1598498552
Hospital affiliations
1
State license
1
Year NPI issued
2022
Practice address
435 Lewis Avenue, Meriden, CT 06450
Practice phone
Call (203) 694-8200
Professional email
Get professional email
Personal email
Get personal email
Mobile number
Get mobile number
Social profiles

Primary practice

MidState Medical Center

Hospital · Meriden, Connecticut

Find Destiny Ayala'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

Destiny Ayala is a clinical social worker in Meriden, Connecticut

Destiny Ayala practices at MidState Medical Center in Meriden, Connecticut, part of Hartford HealthCare.

Destiny Ayala's NPI, 1598498552, was assigned on July 7, 2022. Destiny Ayala holds Connecticut license 012154.

NPI and contact details
NPI
1598498552NPI Registry (opens in a new tab)
NPI enumeration date
July 7, 2022
NPI status
Active
Practice phone
(203) 694-8200
Professional email
Get email
Personal email
Get email
Mobile number
Get number
Sex
Female

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

Destiny Ayala practices at MidState Medical Center in Meriden, Connecticut

Destiny Ayala's primary practice is MidState Medical Center, at 435 Lewis Avenue, Meriden, CT 06450 in New Haven County. The practice phone is (203) 694-8200.

Source: Dmand AI Affiliation Data

Destiny Ayala is affiliated with 1 site of care

Destiny Ayala's primary practice is MidState Medical Center in Meriden, Connecticut, part of Hartford HealthCare.

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

Dmand AI tracks the EHR system at Destiny Ayala's practice

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

EHR by site
SiteEHR vendor and product
MidState Medical CenterAvailable with a free account

Source: Dmand AI Technology Install Data

For health IT teams

See the EHR and IT leaders at every hospital where Destiny Ayala practices

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

Try for freeBook a meeting

Destiny Ayala is one of 2,962 clinical social workers in Connecticut

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

Specialties and state licenses

  • Clinical social worker, ConnecticutPrimaryLicense 012154 · taxonomy 1041C0700X

Clinical social workers near Destiny Ayala

Counts of clinical social workers with a Dmand AI profile, by place and practice. Each opens the list.

2,962clinical social workers in Connecticut47clinical social workers in Meriden12clinical social workers at MidState Medical Center

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

Destiny Ayala's patients have a median age of 36

Across all payers, Dmand AI patient panel data puts Destiny Ayala's median patient age at 36, with 100% women.

Destiny Ayala's patients across all payers

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

Patient panel by age, all payers

Median age 36

Patient panel by sex, all payers

  • Women100%
  • Men0%

Source: Dmand AI Patient Panel Data

Sources for Destiny Ayala'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 Destiny Ayala

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

What is Destiny Ayala's NPI number?

Destiny Ayala's NPI number is 1598498552. It was assigned on July 7, 2022, and it is active in the NPI Registry.

What does Destiny Ayala specialize in?

Destiny Ayala is a clinical social worker in Meriden, Connecticut. The primary specialty in the NPI Registry is Clinical Social Worker (taxonomy code 1041C0700X).

Where does Destiny Ayala practice?

Destiny Ayala practices at 435 Lewis Avenue, Meriden, CT 06450. Destiny Ayala's primary practice is MidState Medical Center in Meriden, Connecticut, part of Hartford HealthCare.

What is Destiny Ayala's office phone number?

The practice phone on file for Destiny Ayala is (203) 694-8200.

What is Destiny Ayala's medical license number?

Destiny Ayala holds Connecticut license 012154.

Which hospitals is Destiny Ayala affiliated with?

Destiny Ayala practices at MidState Medical Center in Meriden, Connecticut.

How long has Destiny Ayala been practicing?

Destiny Ayala's NPI was assigned in 2022.

Selling to social worker practices?

See clinical social workers in Connecticut by site of care and group

Find the practices, groups and hospitals they work with, and the right people to contact at each.

Start free trialBook a demo
  • 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)
Read the Cookie Policy