DR. LEESA SIMANTON BOOTH DNP
NPI 1043899099
Nurse Practitioner - Adult Health in Rancho Mirage, CA
About Dr. Leesa Simanton Booth Dnp NPPES
Official registry information on file with the National Plan and Provider Enumeration System.
DR. LEESA SIMANTON BOOTH DNP (NPI 1043899099) is an individual adult health provider in Rancho Mirage, California, licensed in California (NP95014445) and active in the NPI registry since April 2021. She is enrolled in Medicare PECOS.
NPPES Registry Identity
Specialties & Licenses 2
Other Identifiers 1
Medicare Participation & PECOS CMS
Medicare enrollment, assignment, and ordering and referring status from the CMS PECOS system.
Medicare Enrollment Status
Enrolled in Medicare (PECOS)
Dr. Leesa Simanton Booth Dnp is registered in the CMS Provider Enrollment, Chain and Ownership System (PECOS).
Physician Visit Costs CMS claims · ZIP area
Typical Medicare office-visit costs in the 92270 ZIP code area, from fee-for-service claims. These are area statistics, not this provider’s prices; actual charges vary by service and coverage.
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 Leesa Booth's NPI number?
The NPI number for Leesa Booth is 1043899099. It was assigned to this individual provider in the NPPES registry on April 6, 2021.
Where is Leesa Booth located?
Leesa Booth practices at 119 Calle De Las Rosas, Rancho Mirage, CA 92270. The listed phone number is (760) 578-3601.
What is Leesa Booth's specialty?
The primary specialty registered for this NPI is Nurse Practitioner, specializing in Adult Health, with taxonomy code 363LA2200X.
Is Leesa Booth enrolled in Medicare?
Yes. Leesa Booth is registered in the Medicare PECOS enrollment system.
When was this NPI record last updated?
The NPPES record for Leesa Booth was last updated on April 6, 2021. NPI Profile syncs weekly with the NPPES registry data releases published by CMS. This NPI record was last updated 5 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.