Nursing documentation supports MDS coding only when it names what happened, how much assistance was given, how often it happened, and how the resident responded. MDS, the Minimum Data Set, is the standardized assessment used by CMS (the Centers for Medicare and Medicaid Services) to set a skilled nursing facility’s (SNF’s) Medicare Part A payment rate for each resident. A nursing note that only proves care occurred does not automatically prove the specific MDS code a coder needs to select.
Most guidance on this topic stops at Section GG, the functional ability section. Sections H, N, and O carry just as much coding weight, and almost nothing published maps nursing charting language to them directly. This post does that mapping, section by section, starting with the three gaps nothing else covers.
Quick Summary
Nursing notes support MDS coding when they document the specific act, amount, frequency, and resident response, not just that care was given. Section H needs continence type, frequency, and intervention. Section N needs the clinical reason behind each coded medication, not just proof it was administered. Section O needs treatment notes tied to dates and times inside the assessment’s look-back window. Vague entries like “assisted with ADLs” or “IV running” fail every one of these sections even when the note is signed and dated.
Table of Contents
Why Section H, N, and O Are the Documentation Gaps Nobody Maps
Most articles on nursing documentation and MDS coding stop at Section GG. That section gets audited first because it drives a large share of the nursing case-mix score under PDPM, the Patient Driven Payment Model CMS uses to set SNF payment rates.
That focus leaves Sections H, N, and O undocumented in most training and most published guidance. These sections are coded from the same nursing notes as GG, using the same standard: what was observed, how much assistance was given, and how often it happened during the look-back period.
A nursing note can be complete and still fail to support these codes. Complete means signed, dated, and present in the chart. Codable means the note contains the specific facts a coder needs to select the right answer, and those are two different bars.
Documenting for Section H: Bladder and Bowel
Section H captures a resident’s continence status: bladder and bowel patterns, catheter use, ostomy care, and any related nursing interventions. MDS coding under this section depends on what happened during the specific observation period the assessment covers, not a general impression of the resident’s continence.
Writing “resident incontinent” once per shift does not support Section H coding. The coder needs frequency, type, and the intervention provided for each occurrence.
A specific version reads: “Urinary incontinence noted during two of three toileting checks this shift. Staff provided brief change and perineal care each occurrence.” That level of detail is what Section H coding requires.
Section H’s assistance and frequency coding is not a summary judgment. It is closer to arithmetic performed on documented events. If the events themselves are not counted in the nursing note, the code has nothing to average, and the coder is left guessing at a number that determines part of the nursing component score.
Documenting for Section N: Medications
Section N reflects the medications a resident received during the observation period, including injections, anticoagulant management, and other high-acuity administration that affects the nursing component of PDPM scoring. The Medication Administration Record, or MAR, is the primary source nursing staff use to log what was given and when.
A MAR entry proves a medication was administered. It does not by itself prove the clinical reason for that medication was active and monitored during the same window, and that clinical link is what Section N coding actually needs.
A complete MAR is not the same as a complete Section N chart. If the anticoagulant order is documented but the monitoring, response, or adverse-effect observation tied to it is missing from the nursing notes, the coder has proof of administration and no proof of the clinical picture the code is supposed to represent.
Documenting for Section O: Special Treatments and Programs
Section O covers special treatments, procedures, and programs: IV medications, suctioning, tracheostomy care, ventilator or respirator management, and isolation protocols. Each of these needs a nursing treatment note with a date, a time, and a clinician signature, not a single checkbox on the MDS itself.
Section O codes are tied to whether a treatment was received during a specific observation period, not whether it was ever performed. A note that describes the treatment but not when it happened cannot confirm the code covers the right window.
|
Treatment
|
What the Note Must Show
|
|---|---|
|
IV medication
|
Date, time, drug, and site assessment for each administration
|
|
Tracheostomy care
|
Date and time of each care episode, not a daily summary
|
|
Isolation protocol
|
Start date, precaution type, and any change in status
|
A treatment note that says a service was provided without saying when tells a coder the task happened at some point, not that it happened inside the look-back period the assessment covers. That gap is what turns a real, delivered service into an unsupportable code.
GG, K, and M in Brief
Section GG, Section K, and Section M follow the same documentation logic covered above, and a full section-by-section breakdown of how CMS reconciles your MDS coding against the chart already exists on this site.
For Section GG, “assisted with ADLs” (activities of daily living) fails because it does not name which of the five CMS assistance levels, independent, supervision, limited, extensive, or total dependence, actually applied to the task. Section K depends on intake and output documentation specific enough to show volume and frequency, not a shift note that simply says the resident ate well.
Section M, skin conditions, needs wound location, stage, dimensions, and treatment frequency documented at each assessment, matching whatever is coded on the MDS.
The Specificity Problem
The same failure pattern repeats across every section. “Resident ate well” does not document percentage of meal consumed.
“Skin intact” is not a structured wound assessment. “IV running” does not capture fluid type, rate, volume, or site assessment.
A nurse who charts “assisted with ADLs” has recorded that something happened. She has not recorded what MDS coding needs, which is how much of the task she performed versus how much the resident performed, and that distinction is the entire code.
Keeping the Care Plan, MDS, and Nursing Notes Aligned
Initial plans of care and every care plan update need a signature and a date from the clinician who completed them. In most SNFs the care plan is nursing-driven, and it has to align with both the MDS coding and the nursing notes underneath it.
A care plan listing a skilled nursing intervention that never appears in the nursing notes, or the reverse, is a documentation inconsistency reviewers are trained to flag. The same standard that defines what counts as a daily skilled service under Medicare Part A applies to whether that intervention belongs in the notes at all.
If the MAR proves a medication was given and nothing else in the chart proves why, the coder is choosing between two options, and only one of them survives an audit. Under-coding a resident’s needs is the safer of the two, which means incomplete documentation costs the facility money it actually earned.
For the complete list of what a reviewer expects to find in the chart during a Part A review, see the full chart-completeness checklist for a Part A review. For the broader documentation standard across surveys and billing, see the complete SNF documentation compliance resource.
Who This Is For
This breakdown is written for DONs, charge nurses, and MDS coordinators who need nursing notes that hold up under both clinical review and MDS coding review. It applies whether your facility already tracks documentation gaps manually or is looking for a more structured process.
Frequently Asked Questions
MDS coding is the process of translating a resident’s clinical documentation into the standardized Minimum Data Set assessment CMS uses to set the facility’s Medicare Part A payment rate and guide care planning.
Section GG needs nursing and therapy notes that name the specific CMS assistance level, independent, supervision, limited, extensive, or total dependence, for each functional task, not a general note that assistance was provided.
Section H needs the frequency and type of any incontinence episodes and the specific intervention provided each time, not a single per-shift note that the resident was incontinent.
Section N needs MAR entries plus nursing notes that connect each coded medication to an active clinical reason and any monitoring or response during the same period.
Section O needs a dated, timed, and signed nursing note for each special treatment or procedure, tied to the specific observation period the assessment covers.
Vague documentation describes that care happened without capturing the amount, frequency, or clinical reason a coder needs, so the coder either under-codes the resident’s needs or codes from an assumption that will not hold up under review.
