JING XUE
NPI 1821306960
Dentist - General Practice in Ocala, FL
About Jing Xue NPPES
Official registry information on file with the National Plan and Provider Enumeration System.
JING XUE (NPI 1821306960) is an individual general practice provider in Ocala, Florida, licensed in Florida (DN-19161) and active in the NPI registry since September 2010. She is enrolled in Medicare PECOS.
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 (PECOS)
Jing Xue 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 34471 ZIP code area, from fee-for-service claims. These are area statistics, not this provider’s prices; actual charges vary by service and coverage.
Other Providers at the Same Location NPPES 2
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 Jing Xue's NPI number?
The NPI number for Jing Xue is 1821306960. It was assigned to this individual provider in the NPPES registry on September 23, 2010.
Where is Jing Xue located?
Jing Xue practices at 2206 SE 17th St, Ocala, FL 34471. The listed phone number is (352) 672-1176.
What is Jing Xue's specialty?
The primary specialty registered for this NPI is Dentist, specializing in General Practice, with taxonomy code 1223G0001X.
Is Jing Xue enrolled in Medicare?
Yes. Jing Xue is registered in the Medicare PECOS enrollment system.
When was this NPI record last updated?
The NPPES record for Jing Xue was last updated on September 23, 2010. NPI Profile syncs weekly with the NPPES registry data releases published by CMS. This NPI record was last updated 16 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.