Program_Memos / 2001 / AB-01-07

Why This Topic Matters

The memorandum helps organizations involved in Medicare system releases understand their testing roles and documentation expectations so releases can be evaluated consistently before implementation. It is useful for teams responsible for maintaining, hosting, or using Medicare processing systems.

Article Sections

1. Subject and Purpose

   Introduces the memorandum and its purpose within Medicare fee-for-service systems release testing. Summarizes the overall goal of coordinated testing and the intended timing for implementation.

2. Standard System and CWF Maintainer Testing

   Describes the responsibilities of maintainers for quarterly and non-quarterly releases. Covers broad testing categories, reporting expectations, and general coordination requirements.

3. Standard System Beta Testing

   Outlines the role of selected user beta sites in reviewing and testing standard system releases. Addresses general testing activities, timing, and reporting relationships.

4. CWF Host Beta Testing

   Summarizes the testing responsibilities assigned to designated CWF hosts for quarterly releases. Includes general expectations for collaboration, release coverage, and testing coordination.

5. Contractor (User) Testing

   Covers the testing responsibilities of Medicare contractors using standard system releases. Describes the broad areas of testing, reporting, and optional participation in improving release test coverage.

6. CWF Host Testing

   Explains the responsibilities of CWF hosts for making test software available and confirming satellite participation. Focuses on release preparation and communication duties.

7. Documentation

   Describes recordkeeping and testing-log expectations for all participating organizations. Summarizes the general information that must be retained and maintained during the testing period.

8. Definitions

   Provides general definitions for the testing terms used in the memorandum. These definitions support consistent understanding of the testing categories referenced throughout the document.