HENDERSON COUNTY COMMUNITY HOSPITAL
NPI 1073584751
Medicare Defined Swing Bed Unit in Lexington, TN
About Henderson County Community Hospital NPPES
Official registry information on file with the National Plan and Provider Enumeration System.
HENDERSON COUNTY COMMUNITY HOSPITAL (NPI 1073584751) is a healthcare organization registered as a medicare defined swing bed unit in Lexington, Tennessee and active in the NPI registry since January 2006. The organization lists Larry Henson, Rcd, as its authorized official.
NPPES Registry Identity
Specialties & Licenses
Other Names 1
Other Identifiers 3
Accepted Insurance
Other Providers at the Same Location NPPES 20
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 Lexington Hospital Corporation's NPI number?
The NPI number for Lexington Hospital Corporation is 1073584751. It was assigned to this organization in the NPPES registry on January 30, 2006. The provider is doing business as Henderson County Community Hospital.
Where is Lexington Hospital Corporation located?
Lexington Hospital Corporation is located at 200 W Church St, Lexington, TN 38351. The listed phone number is (731) 968-3646.
What is Lexington Hospital Corporation's specialty?
The primary specialty registered for this NPI is Medicare Defined Swing Bed Unit with taxonomy code 275N00000X.
What insurance does Lexington Hospital Corporation accept?
Health plans from UnitedHealthcare list Lexington Hospital Corporation 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 Lexington Hospital Corporation was last updated on May 19, 2021. NPI Profile syncs weekly with the NPPES registry data releases published by CMS. This NPI record was last updated 5 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.