HYUN JAE SEO
NPI 1366070393
Anesthesiology in Torrance, CA
About Hyun Jae Seo NPPES
Official registry information on file with the National Plan and Provider Enumeration System.
HYUN JAE SEO (NPI 1366070393) is an individual anesthesiology provider in Torrance, California, licensed in California (A186540) and active in the NPI registry since March 2020. He is enrolled in Medicare PECOS, maintains a secondary practice location in Torrance, and is a graduate of University Of Southern California Keck School Of Medicine (2020).
NPPES Registry Identity
Specialties & Licenses 2
Secondary Practice Location 1
Medicare Participation & PECOS CMS
Medicare enrollment, assignment, and ordering and referring status from the CMS PECOS system.
Medicare Enrollment Status
Enrolled in Medicare and accepts Medicare assignment
Hyun Jae Seo is registered in PECOS and agrees to accept the Medicare-approved amount as full payment. Medicare patients are not billed beyond the standard deductible and coinsurance.
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 Hyun Jae Seo's NPI number?
The NPI number for Hyun Jae Seo is 1366070393. It was assigned to this individual provider in the NPPES registry on March 27, 2020.
Where is Hyun Jae Seo located?
Hyun Jae Seo practices at 3330 Lomita Blvd Central Tower Or, Torrance, CA 90509. The listed phone number is (310) 517-4759.
What is Hyun Jae Seo's specialty?
The primary specialty registered for this NPI is Anesthesiology with taxonomy code 207L00000X.
Is Hyun Jae Seo enrolled in Medicare?
Yes. Hyun Jae Seo is registered in the Medicare PECOS system and accepts Medicare assignment, which means accepting the Medicare-approved amount as payment in full for covered services.
When was this NPI record last updated?
The NPPES record for Hyun Jae Seo was last updated on July 3, 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.