MDS Section GG guide

MDS Section GG in SNF admissions: what to verify before saying yes.

Section GG can reveal functional-status, mobility, self-care, therapy, and PDPM planning signals. In admissions, those signals are useful only when staff can verify them against the referral packet, payer context, and facility capacity.

GG codes cheat sheet

Section GG scoring: the GG codes cheat sheet.

Section GG (Functional Abilities and Goals) records a resident's usual performance on self-care and mobility items using a six-level scale, plus four "activity was not attempted" codes. Use the table below as a quick reference, then confirm details against the current CMS RAI Manual.

MDS Section GG response codes and their meaning
GG code Meaning What it indicates
06 Independent Resident completes the activity with no helper assistance.
05 Setup or clean-up assistance Helper assists only before or after; resident does the activity.
04 Supervision or touching assistance Helper gives verbal cues or steadying / contact-guard help.
03 Partial / moderate assistance Helper does less than half the effort.
02 Substantial / maximal assistance Helper does more than half the effort.
01 Dependent Helper does all the effort, or two or more helpers are required.
07 Refused Resident refused to complete the activity.
09 Not applicable Activity not attempted and not expected to be performed.
10 Not attempted (environment) Environmental limitations prevented the activity.
88 Not attempted (medical / safety) A medical condition or safety concern prevented the activity.

The six performance levels (06 down to 01) describe how much help a resident needs; the 07, 09, 10, and 88 codes record why an activity was not attempted. In admissions, these GG codes help staff sanity-check whether a referral packet's functional story matches the therapy notes and the expected level of care, which also feeds PDPM classification planning and AI admissions analysis.

Admissions use case

Section GG is not just an MDS task. It is an admissions review signal.

SNF teams often receive incomplete or inconsistent referral packets. Section GG language, therapy notes, prior level of function, and payer requirements can point to questions that should be answered before a bed is held.

Self-care and mobility baseline

Compare the packet's functional-status story with therapy notes, hospital course, discharge goals, and expected assistance level.

Therapy documentation support

Check whether PT, OT, or nursing documentation supports the level of skilled need implied by the referral.

Inconsistent packet facts

Watch for mismatches between diagnoses, medication lists, nursing notes, functional status, and requested level of care.

PDPM planning context

Treat PDPM and functional-status details as planning context for administrators, not reimbursement guarantees or clinical acceptance rules.

Medicare Advantage follow-up

If payer authorization depends on skilled need, therapy goals, or functional decline, missing Section GG support should trigger clarification.

Facility fit questions

High assistance needs, wounds, isolation, medications, or staffing constraints should be reviewed with the operational team before the final decision.

Admissions review checklist Use with source-document verification
No PHI
  • Confirm the packet includes current therapy and nursing documentation.
  • Compare functional status against expected SNF level of care.
  • Ask whether payer authorization depends on missing skilled-need support.
  • Separate clinical fit from admin-only PDPM and margin planning context.
  • Document follow-up questions before acceptance, not after arrival.
Where AdmitScoreā„¢ fits

AdmitScore keeps MDS and PDPM signals inside admissions intelligence.

AdmitScoreā„¢ does not turn MDS into a standalone product. It uses MDS- and PDPM-related clues as part of AI admissions analysis for SNFs: referral packet review, authorization readiness, documentation gaps, care-fit questions, and admin-only financial planning context.

  • Financial-free review: staff verify before relying on output.
  • Admissions-level scope: no EHR replacement or broad SNF OS.
  • Operator language: questions are framed for admissions, clinical, and administrator review.
Source orientation

Use official guidance for MDS rules; use AdmitScore for admissions workflow.

MDS coding and PDPM rules should be checked against current CMS materials and your facility's policies. AdmitScore is a review-support tool for admissions teams, not a coding, compliance, legal, or reimbursement authority.

CMS RAI manual

Use CMS RAI manual materials for current MDS assessment and coding guidance. Admissions pages should not replace those instructions.

Open CMS RAI manual resources

PDPM resources

PDPM logic can affect planning context, but admission decisions still require staff judgment and payer verification.

Open CMS PDPM resources

AdmitScore pilot

Pilot AdmitScore with synthetic-first review, PHI-free public forms, and secure workflow scoping before any live referral packet process.

Request a pilot conversation
FAQ

Common Section GG admissions questions.

Why does MDS Section GG matter before a SNF admission?

Section GG can help staff understand functional status, mobility support, self-care needs, therapy documentation, and possible PDPM planning context. During admissions review, those items should be verified against the referral packet and facility capacity before the final decision.

Does Section GG determine whether a facility should accept a referral?

No. Section GG is one admissions signal. Facility staff still verify payer, authorization, clinical documentation, care needs, staffing fit, and operational readiness before deciding.

How does AdmitScore use MDS and PDPM signals?

AdmitScore treats MDS and PDPM-related information as admissions-level planning signals. It can surface missing documentation, possible functional-status questions, payer verification needs, and admin-only financial planning context for staff review.