BALY JUAN SEO PARK
NPI 1790403137
Student in an Organized Health Care Education/Training Program in Farmington, CT
About Baly Juan Seo Park NPPES
Official registry information on file with the National Plan and Provider Enumeration System.
BALY JUAN SEO PARK (NPI 1790403137) is an individual student in an organized health care education/training program in Farmington, Connecticut, licensed in Connecticut (13568) and active in the NPI registry since August 2022. 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)
Baly Juan Seo Park 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.
FARMINGTON, CT 06030
FARMINGTON, CT 06030
FARMINGTON, CT 06030
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 Baly Seo Park's NPI number?
The NPI number for Baly Seo Park is 1790403137. It was assigned to this individual provider in the NPPES registry on August 22, 2022.
Where is Baly Seo Park located?
Baly Seo Park practices at 263 Farmington Ave, Farmington, CT 06030. The listed phone number is (679) 860-2000.
What is Baly Seo Park's specialty?
The primary specialty registered for this NPI is Student in an Organized Health Care Education/Training Program with taxonomy code 390200000X.
Is Baly Seo Park enrolled in Medicare?
Yes. Baly Seo Park is registered in the Medicare PECOS enrollment system.
When was this NPI record last updated?
The NPPES record for Baly Seo Park was last updated on September 6, 2022. NPI Profile syncs weekly with the NPPES registry data releases published by CMS. This NPI record was last updated 3 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.