SAMUEL KAREM
NPI 1982408506
Student in an Organized Health Care Education/Training Program in Cincinnati, OH
About Samuel Karem NPPES
Official registry information on file with the National Plan and Provider Enumeration System.
SAMUEL KAREM (NPI 1982408506) is an individual student in an organized health care education/training program in Cincinnati, Ohio and active in the NPI registry since April 2025. He is enrolled in Medicare PECOS and maintains a secondary practice location in Indianapolis.
NPPES Registry Identity
Specialties & Licenses
Secondary Practice Location 1
Group Practice 1
Medicare Participation & PECOS CMS
Medicare enrollment, assignment, and ordering and referring status from the CMS PECOS system.
Medicare Enrollment Status
Enrolled in Medicare (PECOS)
Samuel Karem 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.
CINCINNATI, OH 45236
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 Samuel Karem's NPI number?
The NPI number for Samuel Karem is 1982408506. It was assigned to this individual provider in the NPPES registry on April 2, 2025.
Where is Samuel Karem located?
Samuel Karem practices at 4777 E Galbraith Rd, Cincinnati, OH 45236. The listed phone number is (513) 686-5446.
What is Samuel Karem's specialty?
The primary specialty registered for this NPI is Student in an Organized Health Care Education/Training Program with taxonomy code 390200000X.
Is Samuel Karem enrolled in Medicare?
Yes. Samuel Karem is registered in the Medicare PECOS enrollment system.
When was this NPI record last updated?
The NPPES record for Samuel Karem was last updated on June 20, 2026. NPI Profile syncs weekly with the NPPES registry data releases published by CMS. This NPI record was last updated 48 days 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.