Bindinglaw

US · guidance

CMS Pub. 100-05, ch. 5, § 50.1.4

Executing and Testing MSPPAY Software

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

A/B MACs (Part B) and DME MACs receive the MSP software through their standard

system along with the Medicare Secondary Payment Technical Manual documenting, and

describing the execution of the MSPPAY Module(s). The input data elements and output

data elements required are referenced in these manuals. The Medicare Integrated Systems

Testing (MIST) contractor is responsible for testing and verifying the accuracy of the

MSPPAY software when updates are implemented. A/B MACs (Part B) and DME MACs

also test the MSPPAY software independently and review the results.

History

(Rev. 11550; Issued: 08-12-22; Effective: 10-13-22; Implementation:10-13-22)

Provenance

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