HEE KIM
NPI 1699606582
Nurse Practitioner - Family in Plain City, OH

Active since May 28, 2026
8350 CHICKASAW WAY, PLAIN CITY, OH 43064(614) 339-9468 Get Directions Write a Review

NPPES record last updated: May 28, 2026. Verified against the NPPES registry weekly; last sync: August 02, 2026.

About Hee Kim NPPES

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

HEE KIM (NPI 1699606582) is an individual family provider in Plain City, Ohio, licensed in Ohio (CNP.0042109) and active in the NPI registry since May 2026.

NPPES Registry Identity

NPI1699606582
Entity TypeIndividual
Primary Taxonomy363LF0000X
Provider Legal NameHEE KIM
Location Address8350 CHICKASAW WAYPlain City, OH 43064-2633
Mailing Address8350 Chickasaw WayPlain City, OH 43064-2633 · (614) 339-9468
Sole ProprietorNo
Enumeration DateMay 28, 2026
NPPES CertifiedMay 28, 2026
NPI 1699606582 is a valid, active identifier and passes the ISO check-digit test.

Specialties & Licenses

Primary SpecialtyNurse Practitioner · FamilyPhysician Assistants & Advanced Practice Nursing Providers
Taxonomy Code363LF0000X
License Licensed in OH · CNP.0042109
8350 CHICKASAW WAY, Plain City, OH 43064

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

The NPI number for Hee Kim is 1699606582. It was assigned to this individual provider in the NPPES registry on May 28, 2026.

Where is Hee Kim located?

Hee Kim practices at 8350 Chickasaw Way, Plain City, OH 43064. The listed phone number is (614) 339-9468.

What is Hee Kim's specialty?

The primary specialty registered for this NPI is Nurse Practitioner, specializing in Family, with taxonomy code 363LF0000X.

When was this NPI record last updated?

The NPPES record for Hee Kim was last updated on May 28, 2026. NPI Profile syncs weekly with the NPPES registry data releases published by CMS. This NPI record was last updated 2 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.