MIRUTSE TEKLU AMSSALU
NPI 1093502221
Student in an Organized Health Care Education/Training Program in Seattle, WA
About Mirutse Teklu Amssalu NPPES
Official registry information on file with the National Plan and Provider Enumeration System.
MIRUTSE TEKLU AMSSALU (NPI 1093502221) is an individual student in an organized health care education/training program in Seattle, Washington and active in the NPI registry since April 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)
Mirutse Teklu Amssalu 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.
SEATTLE, WA 98101
SEATTLE, WA 98101
SEATTLE, WA 98101
SEATTLE, WA 98101
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 Mirutse Amssalu's NPI number?
The NPI number for Mirutse Amssalu is 1093502221. It was assigned to this individual provider in the NPPES registry on April 22, 2025.
Where is Mirutse Amssalu located?
Mirutse Amssalu practices at 925 Seneca St, Seattle, WA 98101. The listed phone number is (253) 838-2400.
What is Mirutse Amssalu's specialty?
The primary specialty registered for this NPI is Student in an Organized Health Care Education/Training Program with taxonomy code 390200000X.
Is Mirutse Amssalu enrolled in Medicare?
Yes. Mirutse Amssalu is registered in the Medicare PECOS enrollment system.
When was this NPI record last updated?
The NPPES record for Mirutse Amssalu was last updated on April 22, 2025. NPI Profile syncs weekly with the NPPES registry data releases published by CMS. This NPI record was last updated 16 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.