DR. BORIS GALKIN M.D.
NPI 1093269565
Student in an Organized Health Care Education/Training Program in Winter Park, FL
About Dr. Boris Galkin M.d. NPPES
Official registry information on file with the National Plan and Provider Enumeration System.
DR. BORIS GALKIN M.D. (NPI 1093269565) is an individual student in an organized health care education/training program in Winter Park, Florida, licensed in Florida (TRN22578) and active in the NPI registry since August 2016. 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. Boris Galkin M.d. 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.
WINTER PARK, FL 32792
WINTER PARK, FL 32792
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 Boris Galkin's NPI number?
The NPI number for Boris Galkin is 1093269565. It was assigned to this individual provider in the NPPES registry on August 12, 2016.
Where is Boris Galkin located?
Boris Galkin practices at 133 Benmore Dr Suite 201, Winter Park, FL 32792. The listed phone number is (407) 646-7757.
What is Boris Galkin's specialty?
The primary specialty registered for this NPI is Student in an Organized Health Care Education/Training Program with taxonomy code 390200000X.
Is Boris Galkin enrolled in Medicare?
Yes. Boris Galkin is registered in the Medicare PECOS enrollment system.
When was this NPI record last updated?
The NPPES record for Boris Galkin was last updated on August 12, 2016. NPI Profile syncs weekly with the NPPES registry data releases published by CMS. This NPI record was last updated 9 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.