Bindinglaw

US · guidance

CMS Pub. 100-11, ch. 10, § 30.2

Level One Reporting Requirements

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

Level One Reporting Requirements refers to those data elements for monitoring that are

regularly reported by PACE organizations via the Health Plan Management System

(HPMS) PACE monitoring module. These monitoring elements are detailed in the HPMS

PACE User’s Guide, Fall 2005

(https://www.cms.gov/PACE/Downloads/hpmsmanual.pdf) and include:

• Routine Immunizations;

• Grievances and Appeals;

• Enrollments;

• Disenrollments;

• Prospective Enrollees;

• Readmissions;

• Emergency (Unscheduled) Care;

• Unusual Incidents; and,

• Deaths.

The HPMS database is regularly monitored by staff in the CMS Regional Office (RO)

and State Administering Agency (SAA).

Data reported in response to the Level One Reporting Requirement are used by PACE

organizations to identify opportunities for quality improvement. For example, based on

their review of Level One data reported in HPMS, PACE organization’s may:

• Conduct a QAPI activity using a standardized methodology (e.g., Plan, Do,

Check, Act known as PDCA) if a policy or system problem is identified;

• Institute QAPI-driven change in policies, procedures, systems, or training as

appropriate;

• Evaluate the effectiveness of the intervention;

• Track and trend for sustainable improvement;

• Reevaluate until improvement is sustained;

• Document for review during CMS/State Administering Agency audit as

evidence of a performance improvement activity;

• Report findings at least annually to oversight committees including the PACE

organization’s governing board.

[HPMS PACE User’s Guide, Fall 2005; Level Two Guidance, October 2010]

History

(Rev. 2, Issued: 06-09-11; Effective: 06-03-11; Implementation: 06-03-11)

Provenance

Source
cms.gov
Retrieved
2026-08-25
Edition
iom-2026-08-25
Content hash
63c430188f18d1ba672234db0cea01070bf2997ff1c25a7bd50d19cb73b17cb2
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.