ASHLEY PREE
NPI 1396276937
Nurse Practitioner - Family in Dallas, TX
About Ashley Pree NPPES
Official registry information on file with the National Plan and Provider Enumeration System.
ASHLEY PREE (NPI 1396276937) is an individual family provider in Dallas, Texas, licensed in Texas (NOT ISSUED YET) and active in the NPI registry since March 2017. She maintains a secondary practice location in Grand Prairie.
NPPES Registry Identity
Specialties & Licenses
Secondary Practice Location 1
Accepted Insurance
Other Providers at the Same Location NPPES 20
Providers registered at the same practice address, or within the immediate area, according to the NPPES registry.
DALLAS, TX 75231
DALLAS, TX 75231
DALLAS, TX 75231
DALLAS, TX 75231
DALLAS, TX 75231
DALLAS, TX 75231
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 Ashley Pree's NPI number?
The NPI number for Ashley Pree is 1396276937. It was assigned to this individual provider in the NPPES registry on March 24, 2017.
Where is Ashley Pree located?
Ashley Pree practices at 7424 Greenville Ave, Dallas, TX 75231. The listed phone number is (214) 363-2004.
What is Ashley Pree's specialty?
The primary specialty registered for this NPI is Nurse Practitioner, specializing in Family, with taxonomy code 363LF0000X.
What insurance does Ashley Pree accept?
Health plans from Ambetter Health, Ambetter from Arizona Complete Health, Ambetter from Arkansas Health & Wellness, Ambetter from Louisiana Healthcare Connections and Ambetter from Superior HealthPlan and 5 other insurers list Ashley Pree 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 Ashley Pree was last updated on September 27, 2018. NPI Profile syncs weekly with the NPPES registry data releases published by CMS. This NPI record was last updated 7 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.
