US · guidance

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

Testing Standards Applicable to all Beta Testers

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

1. Each shared system maintainer and each beta tester shall complete integrated testing with the

CWF Beta tester, using coordinated beneficiary data, in the execution of their test cases. All

test cases involving CWF functionality (related to claims adjudication) must be executed in

an integrated test with the CWF. This requires full data exchanges between testing entities

including:

• Satellite files being sent from the shared systems to the CWF Beta tester; and

• Response files being sent from the CWF to the shared system Beta testers.

2. Each Beta tester shall:

• Utilize the standard CMS Test Management tool and repository to documents all test

cases and results.

• Follow the procedures outlined in the Quarterly Release Test Management User Guide in

order to complete the documentation of test runs and results.

3. Each STC/beta tester shall review all Shared System Maintainer release documentation for

completeness, accuracy, and usability. Any questions, problems, or issues with the

documentation shall be forwarded to both the Shared System Maintainer and CMS.

4. Each STC/beta tester shall conduct performance testing to reasonably assure that the system

provides acceptable response times, throughput rates, and processing windows and can

accommodate production workloads.

5. The CMS testing requirements outlined in section 40.3 may require the STC/beta tester to

test a specific type of bill, specialty, or claim situation for which they do not possess the

required level of expertise. In these instances, the STC/beta tester must partner with a

Medicare A/B, DME MAC that possesses both the expertise and capabilities to test the

specialty or claim type. As an example, should the STC/beta tester not have the operational

capability or expertise to process Home Health claims, they are expected to partner with an

A/B MAC (HHH) to complete the required HHA testing. Ultimately, the STC/beta tester is

responsible for ensuring all test cases are exercised. Any partnerships that are established to

complete the testing requirements shall be arranged and managed by the STC/beta tester.

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: 3df135eab362e31f9af1652d1165488a6f8eb18f977e07aba3c1f3d093114fd9

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