Bindinglaw

US · guidance

CMS Pub. 100-01, ch. 7, § 40.3.8

Testing Documentation Requirements

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

1. The SSM, STC, and MAC shall maintain documentation that fully demonstrates the

requirements of this transmittal were met for each quarterly release. At a minimum the SSM,

Beta tester, and MAC shall maintain the following test documentation to demonstrate full

compliance:

• Test Requirement and Test Case repository with traceability;

• Test Log;

• Test Status for the execution (run) of each test case (i.e., Pass, Fail, Not Run);

• Actual Results for the run of each test case in which the actual results did not match the

expected results; and

• Documented proof of each test run, i.e., screen shots, scheduler job logs, etc.

2. The SSM, STC, and MAC shall:

• Maintain all test documentation for the four quarterly releases prior to the current release

under test. The documentation must be available for review by CMS (or its agent).

• Document all software defects (problems) within the CMS specified repository such as

INFOMAN.

3. The SSM shall communicate all confirmed software defects (problems) and fixes directly to

CMS in writing through their CMS Maintenance Lead/(GTL) or other designee as specified

by the CMS Project Officer.

4. A/B, DME MACs shall provide any testing documentation to their CMS regional office upon

request.

Additional requirements for selected shared system maintainers, STC, and CWF hosts may be

contained in these organizations' individual contracts. Electronic screen shots may be

incorporated/attached into the results of ALM has proof of online results. Test Log requirements

may be fulfilled by correctly using the ALM “run” feature as outlined in the Quarterly Release

Test Management User Guide.

History

(Rev. 97, Issued: 01-15-16, Effective: 09-21-15, Implementation: 09-21-15)

Provenance

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