Bindinglaw

US · guidance

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

Shared System Testing Requirements for Shared System Maintainers,

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

Single Testing Contractor (STC), and DME MACs

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

Review subsection 40.3.9, Definitions, for a description of key testing terminology.

1. Maintainers of a Shared System shall plan and execute all the essential levels of testing. At a

minimum this includes Unit testing, Integration testing, System testing, and Regression

testing. Shared System Maintainers are also responsible for performing Interface Testing.

2. Beta testers may initiate testing at the integration level, but are primarily dedicated to testing

at the system level, including regression testing. Beta testers are also responsible for

performing Interface Testing, which includes full data exchanges between the shared system

maintainers, and other systems.

3. Shared System Maintainers and Beta testers shall maintain a test environment that enables

system-testing activities to replicate the production environment, as closely as required to

effectively test. CMS provided all Beta testers with a date simulation tool to facilitate executing

test cases with future dates (e.g., service dates, admission dates) without turning off edits or

altering effective dates in the test environment.

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
f5fdc1bd74b5786fc75484ebf310fda4248ee5505443e6f6cfee4a93f64aa1ff
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.