16. Weak vs. strong documentation
The recurring failures (left), why each fails (center), and the corrected, defensible daily note (right).
Weak — does not survive | Why it fails | Strong — defensible |
|---|---|---|
“Resident stable, continues to need skilled care.” | A conclusion with no skilled service, no daily basis, and no evidence an assessment occurred; reads as custodial. | Name the day’s skilled service, the licensed-level reason, the quantified finding, and why the need was daily and SNF-level — e.g., the observation-&-assessment model note in §4.1. |
“IV antibiotic given.” | A bare task with no site/monitoring, no infection response, and no MDS support. | “1 g IV ceftriaxone via midline over 30 min per order; site clear, flushed; afebrile, urine clearing, WBC downtrending — daily covered skilled procedure requiring SNF-level delivery; supports Section N/O.” |
“Educated resident. Verbalized understanding.” | No topic, method, audience, or measured mastery. | Return-demo 9/9 + teach-back 100% on named content, with a reinforcement plan — the teaching model note in §4.3. |
“MD notified.” | No time, content, response, or representative notification — the loop is open. | “SBAR to NP 14:10 [data]; order received [details]; administered/verified; representative notified 14:30; reassess next shift.” |
“No progress in therapy; at plateau.” | Misstates the law — implies a plateau ends coverage. | Document the skill required to maintain function or slow decline (Jimmo): the restorative model note in §4.5. |
Identical note copied day to day. | Cloned language gives no trajectory and reads as not individually assessed — an ADR and survey trigger. | Re-document the actual findings and the change since the last value, with a fresh necessity sentence and outcome each day. |