JINSUNG YUK – NPI #1497690424
Radiologic Technologist

A radiologic technologist who specializes in sonography and is appropriately educated and trained, consistent with nationally recognized standards, state statute, and facility policy in performance of ultrasounds, exam techniques, equipment protocols, radiation safety, and patient care.

JINSUNG YUK is a radiologic technologist located in BRENTWOOD, TN. NPPES recently assigned the NPI number 1497690424 to JINSUNG YUK on April 23, 2026. It is a Type-1 NPI, indicating this NPI number is associated with an individual. The primary taxonomy selected by this provider is 2471S1302X from the Health Care Provider Taxonomy code set, which is classified as Radiologic Technologist, specializing in Sonography Radiologic Technologist

Use the NPI data found here to bill health insurance companies, identify providers enrolled in Medicare and Medicaid services or other HIPAA compliant transactions. See the complete NPI profile for JINSUNG YUK below.

NPI Profile for
JINSUNG YUK

NPI Number
1497690424
Enumeration Date

(about 6 weeks ago)
Entity Type
Type-1  Individual (Male)
Legal Name
JINSUNG YUK
Primary location
1527 BOREAL CT
BRENTWOOD, TN 37027-2616
Phone: (323) 208-1817 Fax:
Mailing address
Same as primary location
Sole Proprietor
No
Updated
Certification Date
Apr 23, 2026

Note: NPPES allows providers to attest to the accuracy of their NPI data. When a provider request any change to the NPI record, they will be able to attest to their changed NPI data, resulting in an updated certification date.

Taxonomy Code(s)

A taxonomy code is a code that describes the health care service provider's type, classification, and the area of specialization. The primary specialty for this provider is indicated as (Primary) below.

Taxonomy Classification / Specialization State License
2471S1302X
- Radiologic Technologist / Sonography Radiologic Technologist (Primary)
TN 348155

The taxonomy codes are selected by the provider at the time of NPI registration. Selection of a taxonomy code does not replace any credentialing or validation process that the provider requesting the code should complete.