DR. JUAN JOSE GUERRA LONDONO MD
NPI 1548013261
Student in an Organized Health Care Education/Training Program in Detroit, MI
About Dr. Juan Jose Guerra Londono Md NPPES
Official registry information on file with the National Plan and Provider Enumeration System.
DR. JUAN JOSE GUERRA LONDONO MD (NPI 1548013261) is an individual student in an organized health care education/training program in Detroit, Michigan and active in the NPI registry since April 2024. 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)
Dr. Juan Jose Guerra Londono Md is registered in the CMS Provider Enrollment, Chain and Ownership System (PECOS).
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.
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 Guerra Londono's NPI number?
The NPI number for Juan Guerra Londono is 1548013261. It was assigned to this individual provider in the NPPES registry on April 10, 2024.
Where is Juan Guerra Londono located?
Juan Guerra Londono practices at 2799 W Grand Blvd, Detroit, MI 48202. The listed phone number is (313) 916-8445.
What is Juan Guerra Londono'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 Guerra Londono enrolled in Medicare?
Yes. Juan Guerra Londono is registered in the Medicare PECOS enrollment system.
When was this NPI record last updated?
The NPPES record for Juan Guerra Londono was last updated on April 10, 2024. NPI Profile syncs weekly with the NPPES registry data releases published by CMS. This NPI record was last updated 2 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.
