DR. NIKITA GOLOVACHEV MD
NPI 1790670297
Student in an Organized Health Care Education/Training Program in Orlando, FL
About Dr. Nikita Golovachev Md NPPES
Official registry information on file with the National Plan and Provider Enumeration System.
DR. NIKITA GOLOVACHEV MD (NPI 1790670297) is an individual student in an organized health care education/training program in Orlando, Florida, licensed in Florida (43223) and active in the NPI registry since June 2025. 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. Nikita Golovachev 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.
ORLANDO, FL 32803
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 Nikita Golovachev's NPI number?
The NPI number for Nikita Golovachev is 1790670297. It was assigned to this individual provider in the NPPES registry on June 12, 2025.
Where is Nikita Golovachev located?
Nikita Golovachev practices at 601 E Rollins St, Orlando, FL 32803. The listed phone number is (407) 303-7133.
What is Nikita Golovachev's specialty?
The primary specialty registered for this NPI is Student in an Organized Health Care Education/Training Program with taxonomy code 390200000X.
Is Nikita Golovachev enrolled in Medicare?
Yes. Nikita Golovachev is registered in the Medicare PECOS enrollment system.
When was this NPI record last updated?
The NPPES record for Nikita Golovachev was last updated on June 12, 2025. NPI Profile syncs weekly with the NPPES registry data releases published by CMS. This NPI record was last updated 15 months 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.