ROHAT BHAGWAN BHIMANI MD
NPI 1497272629
Orthopaedic Surgery in Alexandria, VA
About Rohat Bhagwan Bhimani Md NPPES
Official registry information on file with the National Plan and Provider Enumeration System.
ROHAT BHAGWAN BHIMANI MD (NPI 1497272629) is an individual orthopaedic surgery provider in Alexandria, Virginia, licensed in Virginia (0101289020) and active in the NPI registry since August 2017. He is enrolled in Medicare PECOS.
NPPES Registry Identity
Specialties & Licenses 2
Other Names 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)
Rohat Bhagwan Bhimani Md is registered in the CMS Provider Enrollment, Chain and Ownership System (PECOS).
Physician Visit Costs CMS claims · ZIP area
Typical Medicare office-visit costs in the 22306 ZIP code area, from fee-for-service claims. These are area statistics, not this provider’s prices; actual charges vary by service and coverage.
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 Rohat Bhimani's NPI number?
The NPI number for Rohat Bhimani is 1497272629. It was assigned to this individual provider in the NPPES registry on August 28, 2017. The provider is also known as Rahool Bhagwan Bhimani.
Where is Rohat Bhimani located?
Rohat Bhimani practices at 2501 Parkers Ln Ste 201, Alexandria, VA 22306. The listed phone number is (703) 892-6500.
What is Rohat Bhimani's specialty?
The primary specialty registered for this NPI is Orthopaedic Surgery with taxonomy code 207X00000X.
Is Rohat Bhimani enrolled in Medicare?
Yes. Rohat Bhimani is registered in the Medicare PECOS enrollment system.
When was this NPI record last updated?
The NPPES record for Rohat Bhimani was last updated on July 25, 2026. NPI Profile syncs weekly with the NPPES registry data releases published by CMS. This NPI record was last updated 35 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.