DR. CHASE R GIMA DC
NPI 1619430592
Chiropractor in Florence, KY
About Dr. Chase R Gima Dc NPPES
Official registry information on file with the National Plan and Provider Enumeration System.
DR. CHASE R GIMA DC (NPI 1619430592) is an individual chiropractor in Florence, Kentucky, licensed in Kentucky (5602) and active in the NPI registry since April 2019. He is a graduate of Life Chiropractic College (2019).
NPPES Registry Identity
Specialties & Licenses
Medicare Participation & PECOS CMS
Medicare enrollment, assignment, and ordering and referring status from the CMS PECOS system.
Medicare Enrollment Status
Enrolled in Medicare and accepts Medicare assignment
Dr. Chase R Gima Dc is registered in PECOS and agrees to accept the Medicare-approved amount as full payment. Medicare patients are not billed beyond the standard deductible and coinsurance.
Other Providers at the Same Location NPPES
Providers registered at the same practice address, or within the immediate area, according to the NPPES registry.
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 Chase Gima's NPI number?
The NPI number for Chase Gima is 1619430592. It was assigned to this individual provider in the NPPES registry on April 9, 2019.
Where is Chase Gima located?
Chase Gima practices at 7201 Dixie Hwy, Florence, KY 41042. The listed phone number is (859) 727-6888.
What is Chase Gima's specialty?
The primary specialty registered for this NPI is Chiropractor with taxonomy code 111N00000X.
Is Chase Gima enrolled in Medicare?
Yes. Chase Gima is registered in the Medicare PECOS system and accepts Medicare assignment, which means accepting the Medicare-approved amount as payment in full for covered services.
When was this NPI record last updated?
The NPPES record for Chase Gima was last updated on April 9, 2019. NPI Profile syncs weekly with the NPPES registry data releases published by CMS. This NPI record was last updated 7 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.
