MS. LOGAN BETH GALANSKY
NPI 1205469343
Student in an Organized Health Care Education/Training Program in Baltimore, MD
About Ms. Logan Beth Galansky NPPES
Official registry information on file with the National Plan and Provider Enumeration System.
MS. LOGAN BETH GALANSKY (NPI 1205469343) is an individual student in an organized health care education/training program in Baltimore, Maryland and active in the NPI registry since February 2020. She 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)
Ms. Logan Beth Galansky 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.
BALTIMORE, MD 21287
BALTIMORE, MD 21287
BALTIMORE, MD 21287
BALTIMORE, MD 21287
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 Logan Galansky's NPI number?
The NPI number for Logan Galansky is 1205469343. It was assigned to this individual provider in the NPPES registry on February 18, 2020.
Where is Logan Galansky located?
Logan Galansky practices at 600 N Wolfe St, Baltimore, MD 21287. The listed phone number is (303) 552-7654.
What is Logan Galansky's specialty?
The primary specialty registered for this NPI is Student in an Organized Health Care Education/Training Program with taxonomy code 390200000X.
Is Logan Galansky enrolled in Medicare?
Yes. Logan Galansky is registered in the Medicare PECOS enrollment system.
When was this NPI record last updated?
The NPPES record for Logan Galansky was last updated on February 18, 2020. NPI Profile syncs weekly with the NPPES registry data releases published by CMS. This NPI record was last updated 6 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.