PRISTINE SENIOR LIVING OF OXFORD, LLC
NPI 1467837435
Skilled Nursing Facility in Oxford, OH
About Pristine Senior Living Of Oxford, Llc NPPES
Official registry information on file with the National Plan and Provider Enumeration System.
PRISTINE SENIOR LIVING OF OXFORD, LLC (NPI 1467837435) is a healthcare organization registered as a skilled nursing facility in Oxford, Ohio and active in the NPI registry since July 2015. The organization lists Christopher T Cook, Chief Executive Officer, as its authorized official.
NPPES Registry Identity
Specialties & Licenses
Other Identifiers 2
Accepted Insurance
Other Providers at the Same Location NPPES 10
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 Pristine Senior Living Of Oxford, LLC's NPI number?
The NPI number for Pristine Senior Living Of Oxford, LLC is 1467837435. It was assigned to this organization in the NPPES registry on July 20, 2015.
Where is Pristine Senior Living Of Oxford, LLC located?
Pristine Senior Living Of Oxford, LLC is located at 6099 Fairfield Rd, Oxford, OH 45056. The listed phone number is (513) 523-6353.
What is Pristine Senior Living Of Oxford, LLC's specialty?
The primary specialty registered for this NPI is Skilled Nursing Facility with taxonomy code 314000000X.
What insurance does Pristine Senior Living Of Oxford, LLC accept?
Health plans from Anthem Blue Cross and Blue Shield list Pristine Senior Living Of Oxford, LLC as in-network in at least one marketplace plan. Coverage varies by plan and year; verify with the insurer or the provider before a visit.
When was this NPI record last updated?
The NPPES record for Pristine Senior Living Of Oxford, LLC was last updated on July 20, 2015. NPI Profile syncs weekly with the NPPES registry data releases published by CMS. This NPI record was last updated 11 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.