Stay Ahead of Compliance with Monthly Citation Updates


In your State Survey window and need a snapshot of your risks?

Survey Preparedness Report

One Time Fee
$79
  • Last 12 months of citation data in one tailored report
  • Pinpoint the tags driving penalties in facilities like yours
  • Jump to regulations and pathways used by surveyors
  • Access to your report within 2 hours of purchase
  • Easily share it with your team - no registration needed
Get Your Report Now →

Monthly citation updates straight to your inbox for ongoing preparation?

Monthly Citation Reports

$18.90 per month
  • Latest citation updates delivered monthly to your email
  • Citations organized by compliance areas
  • Shared automatically with your team, by area
  • Customizable for your state(s) of interest
  • Direct links to CMS documentation relevant parts
Learn more →

Save Hours of Work with AI-Powered Plan of Correction Writer


One-Time Fee

$29 per Plan of Correction
Volume discounts available – save up to 20%
  • Quickly search for approved POC from other facilities
  • Instant access
  • Intuitive interface
  • No recurring fees
  • Save hours of work
F0600
D

Failure to Prevent Resident-on-Resident Physical Abuse

Stockton, California Survey Completed on 03-18-2026

Penalty

No penalty information released
tooltip icon
The penalty, as released by CMS, applies to the entire inspection this citation is part of, covering all citations and f-tags issued, not just this specific f-tag. For the complete original report, please refer to the 'Details' section.

Summary

The deficiency involves the facility’s failure to protect a resident from physical abuse by another resident. Resident 2, who had epilepsy, depression, muscle weakness, unsteadiness on feet, and a traumatic brain injury, and who was assessed with a BIMS score of 7 indicating severe cognitive impairment, was sharing a room with Resident 1. Staff were aware that Resident 1 could become easily agitated, upset, and rude, and that the two residents had a history of disagreements and arguments about lights and television volume at night. These prior conflicts were not documented or reported in the medical record, and no behavior concerns for Resident 1 were care planned or communicated to leadership. On the day of the incident, CNA 1 was preparing Resident 2 for a shower when Resident 1 began yelling at Resident 2. CNA 1 moved Resident 2 into the hallway to prevent escalation and notified Resident 1’s nurse that Resident 1 was upset and yelling, and that the residents should be separated. CNA 1 then escorted Resident 2 to the shower and returned with him about 15 minutes later. She positioned Resident 2 in his wheelchair in front of his bed toward the back of the room, with his back to the door and to Resident 1’s bed, while she stood along the back wall at Resident 2’s nightstand. While CNA 1 was at the nightstand, she observed Resident 1 get up from his bed, approach Resident 2 from behind, and hit him in the back of the head with a fist. CNA 1 called for help, and staff responded and separated the residents. LN 1 arrived and saw Resident 1 standing between the two beds; both residents were yelling, and Resident 2 reported he had been “sucker punched” in the back of the head and was upset. LN 2, the nurse assigned to both residents that day, later assessed Resident 2 for injuries; Resident 2 stated that Resident 1 came over and hit him in the back of the head and appeared surprised, scared, and startled. The DON and Social Services Director confirmed there was no documentation of prior disagreements or behavior issues in either resident’s record, despite staff knowledge of previous arguments and Resident 1’s tendency to become easily agitated.

Long-term care team reviewing survey readiness and plan of correction

We Help Long-Term Care Teams Stay Survey-Ready

We process and analyze inspection reports and plan of correction using AI to extract insights and trends so providers can improve care quality and stay ahead of compliance risks.

Discover our solutions:

An unhandled error has occurred. Reload 🗙