JUAN CARLOS ESPINOSA MD
NPI 1912648684
Student in an Organized Health Care Education/Training Program in Torrance, CA
About Juan Carlos Espinosa Md NPPES
Official registry information on file with the National Plan and Provider Enumeration System.
JUAN CARLOS ESPINOSA MD (NPI 1912648684) is an individual student in an organized health care education/training program in Torrance, California and active in the NPI registry since April 2022. He is enrolled in Medicare PECOS.
NPPES Registry Identity
Specialties & Licenses
Medicare Participation & PECOS CMS
Medicare enrollment, assignment, and ordering and referring status from the CMS PECOS system.
Medicare Enrollment Status
Enrolled in Medicare (PECOS)
Juan Carlos Espinosa Md is registered in the CMS Provider Enrollment, Chain and Ownership System (PECOS).
Other Providers at the Same Location NPPES
Providers registered at the same practice address, or within the immediate area, according to the NPPES registry.
TORRANCE, CA 90502
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 Juan Carlos Espinosa's NPI number?
The NPI number for Juan Carlos Espinosa is 1912648684. It was assigned to this individual provider in the NPPES registry on April 5, 2022.
Where is Juan Carlos Espinosa located?
Juan Carlos Espinosa practices at 1000 W Carson St # 492, Torrance, CA 90502. The listed phone number is (424) 306-7659.
What is Juan Carlos Espinosa's specialty?
The primary specialty registered for this NPI is Student in an Organized Health Care Education/Training Program with taxonomy code 390200000X.
Is Juan Carlos Espinosa enrolled in Medicare?
Yes. Juan Carlos Espinosa is registered in the Medicare PECOS enrollment system.
When was this NPI record last updated?
The NPPES record for Juan Carlos Espinosa was last updated on April 5, 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.