RAJESH B SHAH
NPI 1619688769
Driver in Mason, OH

Active since December 09, 2022
3806 SLAZENGER CT, MASON, OH 45040(513) 200-7906 Get Directions Write a Review

NPPES record last updated: December 9, 2022. Verified against the NPPES registry weekly; last sync: August 16, 2026.

About Rajesh B Shah NPPES

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

RAJESH B SHAH (NPI 1619688769) is an individual driver provider in Mason, Ohio and active in the NPI registry since December 2022.

NPPES Registry Identity

NPI1619688769
Entity TypeIndividualMale
Primary Taxonomy172A00000X
Provider Legal NameRAJESH B SHAH
Location Address3806 SLAZENGER CTMason, OH 45040-4737
Mailing Address3806 Slazenger CtMason, OH 45040-4737 · (513) 200-7906
Sole ProprietorNo
Enumeration DateDecember 9, 2022
NPPES CertifiedDecember 9, 2022
NPI 1619688769 is a valid, active identifier and passes the ISO check-digit test.

Specialties & Licenses 2

Primary SpecialtyDriverOther Service Providers
Taxonomy Code172A00000X
Definition
A person employed to operate a motor vehicle as a carrier of persons or property.
Also ListedTechnician · Personal Care AttendantTaxonomy 3747P1801X
3806 SLAZENGER CT, Mason, OH 45040

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 Rajesh Shah's NPI number?

The NPI number for Rajesh Shah is 1619688769. It was assigned to this individual provider in the NPPES registry on December 9, 2022.

Where is Rajesh Shah located?

Rajesh Shah practices at 3806 Slazenger Ct, Mason, OH 45040. The listed phone number is (513) 200-7906.

What is Rajesh Shah's specialty?

The primary specialty registered for this NPI is Driver with taxonomy code 172A00000X.

When was this NPI record last updated?

The NPPES record for Rajesh Shah was last updated on December 9, 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.