Kettering Heights Post Acute
Kettering, OH • 3.47 HPRD • 93 residents • For Profit • Entity: PACS GroupKettering, OH • 3.47 HPRD • 93 residentsFor Profit • PACS Group
Kettering Heights Post Acute reported 3.47 HPRD (≈ 6.9 residents per total staff) in Q3 2025. This level is below its case-mix (acuity) 4.96 HPRD and in the 40th percentile of nursing homes in Ohio (3.69 HPRD).
Put another way… On a typical 30-bed floor at Kettering Heights Post Acute you’d see about 4.3 staff, including 2.3 nurse aides. For the entire 93-resident facility, that’s about 13.4 total staff, including 7.0 nurse aides.
Case-mix is a CMS metric based on resident acuity.
Reported HPRD (3.47) is 70.0% of case-mix (4.96).
Direct staff excludes Admin/DON. State minimums via MACPAC (2022) may reflect calculated HPRD equivalents. Direct staff excludes Admin/DON. State minimums via MACPAC may reflect calculated HPRD equivalents.
Request custom PBJ analysis for litigation and investigative reporting.Request custom PBJ analysis.
Methodology
This dashboard uses CMS Payroll-Based Journal (PBJ) data (2017–2025), along with other public datasets (Provider Information, Affiliated Entity). State staffing standards via MACPAC (2022).
Metrics
- Hours Per Resident Day (HPRD): Total staff hours ÷ average residents. Example: 350 hours for 100 residents = 3.5 HPRD.
- Direct Care (excl. Admin, DON): Hours per resident day for direct care staff only (RN, LPN, CNA, NAtrn, MedAide), excluding administrative and supervisory roles.
- Contract Staff %: Share of hours provided by contract staff.
- Census: Average number of residents during the period.
Note: Some states set minimums (e.g., NJ, CA, NY at 3.5 HPRD); a federal 3.48 minimum was recently overturned (2025). A 2001 federal study linked 4.1 HPRD to better outcomes in that study. Staffing needs vary by resident acuity (case-mix), day, and shift. Estimates on PBJ Takeaway assume roughly 60% of staff are CNAs.
Data transparency
The PBJ Dashboard pulls directly from CMS data and is carefully vetted for accuracy. Still, sometimes a bug sneaks into the jelly. That could mean: a systemic CMS data reporting issue (e.g., Q2 2017 contract staffing, missing data in 2020 due to COVID) or there could be a coding error on our part. If you spot something that looks off, please let me know via the contact form so I can set things right.