LOGAN EGAN
NPI 1376399402
Student in an Organized Health Care Education/Training Program in Layton, UT

Active since April 29, 2024

NPPES record last updated: April 29, 2024. Verified against the NPPES registry weekly; last sync: August 16, 2026.

About Logan Egan NPPES

Official registry information on file with the National Plan and Provider Enumeration System.

LOGAN EGAN (NPI 1376399402) is an individual student in an organized health care education/training program in Layton, Utah and active in the NPI registry since April 2024.

NPPES Registry Identity

NPI1376399402
Entity TypeIndividualMale
Primary Taxonomy390200000X
Provider Legal NameLOGAN EGAN
Location Address147 E 900 SLayton, UT 84041-4151
Mailing Address147 E 900 SLayton, UT 84041-4151
Sole ProprietorNo
Enumeration DateApril 29, 2024
NPPES CertifiedApril 29, 2024
NPI 1376399402 is a valid, active identifier and passes the ISO check-digit test.

Specialties & Licenses

Taxonomy Code390200000X
Definition
An individual who is enrolled in an organized health care education/training program leading to a degree, certification, registration, and/or licensure to provide health care.
147 E 900 S, Layton, UT 84041

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 Egan's NPI number?

The NPI number for Logan Egan is 1376399402. It was assigned to this individual provider in the NPPES registry on April 29, 2024.

Where is Logan Egan located?

Logan Egan practices at 147 E 900 S, Layton, UT 84041. The listed phone number is (801) 634-7623.

What is Logan Egan's specialty?

The primary specialty registered for this NPI is Student in an Organized Health Care Education/Training Program with taxonomy code 390200000X.

When was this NPI record last updated?

The NPPES record for Logan Egan was last updated on April 29, 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.