Bindinglaw

US · guidance

CMS Pub. 100-04, ch. 1, § 140.2

Systematic Validation of Claims Information Using Patient

activein force · 2026-08-25 – presentas-observed

Assessments

(Rev. 3001, Issued: 08-01-14, Effective: 10-01-12, Implementation: 01-05-15)

The case-mix groups used to determine payments under several Medicare prospective

payment systems (PPS) are based on clinical assessments of the beneficiary. Each

payment system uses a different patient assessment tool:

Payment System Assessment Used

Skilled Nursing Facility – SNF PPS Minimum Data Set

Home Health – HH PPS Outcomes and Assessment Information

Set

Inpatient Rehabilitation Facility – IRF PPS IRF Patient Assessment Instrument

In all three payment systems, the assessments are entered into software at the provider

site that encodes the data into a standard transmission format and transmits the

assessments to quality improvement systems. In addition, the software runs the data from

the assessments through grouping software that generates a case-mix group to be used on

Medicare PPS claims. These case mix groups are reported on claims using a Health

Insurance PPS (HIPPS) code.

CMS provides free grouping software to perform this function, but many providers create

their own software due to their need to integrate these data entry and grouping functions

with their own administrative systems. In some cases, this results in HIPPS codes

reported on claims that differ from the HIPPS code calculated by the assessment system.

In the interest of payment accuracy, Medicare claims processing systems may

temporarily hold Medicare PPS claims paid under these payment systems (Medicare

Advantage claims are excluded), in order to validate the claim information against the

assessment record. If the information found in the assessment system differs from the

claim information, the assessment information will be used to pay the claim. This

process will occur within the payment floor period.

This process may be used for various purposes, including:

• Validating the provider-submitted HIPPS code

• Ensuring timely assessment submission requirements are met

• Ensuring conditions of payment are met.

History

(Rev. 3001, Issued: 08-01-14, Effective: 10-01-12, Implementation: 01-05-15)

Provenance

Source
cms.gov
Retrieved
2026-08-25
Edition
iom-2026-08-25
Content hash
917fd499632e4d0ac9a6ae5faac9bac218234809af0693335d4f6498585d982c
View the official source →

The link goes to the issuing authority’s own document — the one we read to produce this record. Where a source publishes whole titles rather than sections, your browser may need a moment to jump to the provision.

Unofficial copy of government-published law, reproduced from official sources with full provenance. Not an official publication; verify against official sources before relying on it in a filing. Records in the 'guidance' corpus, and only that corpus, are sub-regulatory (interpretive guidelines, survey procedures) and are not binding law. Validity bounds follow each jurisdiction's declared temporalBasis.

Coverage · API docs

Bindinglaw

Point-in-time US law with the receipt attached. Source URL, retrieval time, content hash, and validity dates on every answer.

curl api.binding.law/v1/law/coverage

© 2026 binding.law · a Jubal, Inc. productAttorneys and firms never pay. Ever.
CMS Pub. 100-04, ch. 1, § 140.2 — Systematic Validati… · binding.law