DR. TERRILYN BATTLE LCMHC-A, LCAS-A, CRC
NPI 1972126480
Counselor in Greensboro, NC
About Dr. Terrilyn Battle Lcmhc-a, Lcas-a, Crc NPPES
Official registry information on file with the National Plan and Provider Enumeration System.
DR. TERRILYN BATTLE LCMHC-A, LCAS-A, CRC (NPI 1972126480) is an individual counselor in Greensboro, North Carolina, licensed in (CRC-00116794) and active in the NPI registry since May 2020. She maintains a secondary practice location in Roanoke Rapids.
NPPES Registry Identity
Specialties & Licenses 4
Other Names 1
Secondary Practice Location 1
Accepted Insurance
Other Providers at the Same Location NPPES 5
Providers registered at the same practice address, or within the immediate area, according to the NPPES registry.
GREENSBORO, NC 27401
Frequently Asked Questions NPPES & CMS
Common questions about this NPI record, answered from the official NPPES registry and CMS datasets shown on this page.
What is Terrilyn Battle's NPI number?
The NPI number for Terrilyn Battle is 1972126480. It was assigned to this individual provider in the NPPES registry on May 19, 2020. The provider is also known as Dr. Terrilyn Battle Lcmhc-A, Lcas-A, Crc.
Where is Terrilyn Battle located?
Terrilyn Battle practices at 411 Parkway St Ste I, Greensboro, NC 27401. The listed phone number is (336) 301-9247.
What is Terrilyn Battle's specialty?
The primary specialty registered for this NPI is Counselor with taxonomy code 101Y00000X.
What insurance does Terrilyn Battle accept?
Health plans from Blue Cross and Blue Shield of NC and UnitedHealthcare list Terrilyn Battle as in-network in at least one marketplace plan. Coverage varies by plan and year; verify with the insurer or the provider before a visit.
When was this NPI record last updated?
The NPPES record for Terrilyn Battle was last updated on July 25, 2022. NPI Profile syncs weekly with the NPPES registry data releases published by CMS. This NPI record was last updated 4 years ago. If this record has changed at CMS more recently, you can request an on-demand re-check against the live CMS registry, directly from this page.