EMILY ELIZABETH GARDNER
NPI 1063112738
Counselor - School in Sterling, VA

Active since March 09, 2023
47553 ANCHORAGE CIR, STERLING, VA 20165(571) 449-1003 Get Directions Write a Review

NPPES record last updated: March 9, 2023. Verified against the NPPES registry weekly; last sync: August 16, 2026.

About Emily Elizabeth Gardner NPPES

Official registry information on file with the National Plan and Provider Enumeration System.

EMILY ELIZABETH GARDNER (NPI 1063112738) is an individual school provider in Sterling, Virginia and active in the NPI registry since March 2023.

NPPES Registry Identity

NPI1063112738
Entity TypeIndividualFemale
Primary Taxonomy101YS0200X
Provider Legal NameEMILY ELIZABETH GARDNER
Location Address47553 ANCHORAGE CIRSterling, VA 20165-4716
Mailing Address47553 Anchorage CirSterling, VA 20165-4716 · (571) 449-1003
Sole ProprietorNo
Enumeration DateMarch 9, 2023
NPPES CertifiedMarch 1, 2023
NPI 1063112738 is a valid, active identifier and passes the ISO check-digit test.

Specialties & Licenses

Primary SpecialtyCounselor · SchoolBehavioral Health & Social Service Providers
Taxonomy Code101YS0200X
47553 ANCHORAGE CIR, Sterling, VA 20165

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 Emily Gardner's NPI number?

The NPI number for Emily Gardner is 1063112738. It was assigned to this individual provider in the NPPES registry on March 9, 2023.

Where is Emily Gardner located?

Emily Gardner practices at 47553 Anchorage Cir, Sterling, VA 20165. The listed phone number is (571) 449-1003.

What is Emily Gardner's specialty?

The primary specialty registered for this NPI is Counselor, specializing in School, with taxonomy code 101YS0200X.

When was this NPI record last updated?

The NPPES record for Emily Gardner was last updated on March 9, 2023. NPI Profile syncs weekly with the NPPES registry data releases published by CMS. This NPI record was last updated 3 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.