(General Information, Eligibility, and Entitlement Manual)

2. A/B, DME MACs shall complete a limited end -to-end operational test that incorporates the shared sy stem release, integrated with their other claims processing components. These components include the front -end for claims receipt, translators, the CWF, the financials, and back -end EDI and report generation.  The test must ensure that processing is contig uous from claims entry, to claims adjudication, and ultimately remittance and Medicare Summary Notice generation.  Through contiguous processing, the interfaces between all key claims processing components must be exercised.  The banking system interfaces such as National Clearing House (NCH) transfers need not be exercised.  The test is limited in the number of test cases that are required, since shared system maintainers and the STC are testing the base functionality of the shared system.   A. A/B, DME MAC s shall ensure that the integrated systems software can complete cycles without system abends and produce the expected output.  The A/B, DME Medicare Contractor shall ensure their operational test:    Exercises all claims entry points not fully incorporated in the base system such as paper and EMC front -end components;    Includes all allowable standard electronic formats and versions;    Includes a variety of claims types; and    Includes all components that support their claims workload and interfaces to the shared system.   B. The operational test shall include the most recent shared system release received prior to the initiation of the test.  A/B, DME MACs shall initiate the test as required to ensure its completion and the reporting of any problem prior to production implementation.  3. CMS strongly encourages the shared system user community to promote:    Standardizing their system nationally,    Centralizing any table maintenance that implements national Medicare policy at the system maintainer level, and    Minimizing local variations.   4. A/B, DME MACs may perform additional testing on the shared system or duplicate Beta testing tasks as time permits.  At the discretion of their Regional Offices, the A/B, DME MACs may be required to separately document any testin g they perform in addition to their mandated testing.   5. A/B, DME MACs shall test any business rule or event with future dates that they code or set -up in their Auto Adjudication Software (AAS), prior to implementing the rule or event into production. Examples of AAS include but are not limited to ECPS, SCF, the Shack, and the Mill.   a. A/B MACS shall submit their date simulation recommendations to the FISS FWG in advance and participate in discussions at the FWG calls, as required to reach consensus on a date simulation schedule.   b. A/B MACS shall submit their date simulation recommendations to the MCS FWG in advance and participate in discussions at the FWG calls, as required to reach consensus on a date simulation schedule.   c. DME MACS shall submit their date simulation recommendations to the DMOP TAG or the CFMTAG in advance and participate in discussions at the TAG calls, as required to reach consensus on a date simulation schedule.   d. The FISS FWG, MCS FWG, and DMOP/CFM TAG shall use the system date request  process to provide the VDC(s) their latest run- date simulation schedule for their FISS, MCS, and VMS UAT environments.  e. The FWG or DMOP TAG shall maintain their run -date simulation schedule for a minimum of 14 calendars days in advance.  Here is an e xample of a run -date simulation schedule:   Calendar Date  System Run Date  Calendar Date  System Run Date  Calendar Date  System Run Date  10/8/2015 10/5/2015 10/17/2015 10/14/2015 10/26/2015 10/23/2015 10/9/2015 10/6/2015 10/18/2015 10/15/2015 10/27/2015 10/24/2015 10/10/2015 10/7/2015 10/19/2015 10/16/2015 10/28/2015 10/25/2015 10/11/2015 10/8/2015 10/20/2015 10/17/2015 10/29/2015 10/26/2015 10/12/2015 10/9/2015 10/21/2015 10/18/2015 10/30/2015 10/27/2015 10/13/2015 10/10/2015 10/22/2015 10/19/2015 10/31/2015 10/28/2015 10/14/2015 10/11/2015 10/23/2015 10/20/2015 10/1/2015 10/29/2015 10/15/2015 10/12/2015 10/24/2015 10/21/2015 10/2/2015 10/30/2015 10/16/2015 10/13/2015 10/25/2015 10/22/2015 10/3/2015 10/1/2015  f. The FISS FWG, MCS FWG, and DMOP/CFM  TAG shall provide a copy of their run-date simulation schedule to their CWF test host.   g. The FISS FWG and MCS FWG shall provide a copy of their run -date simulation schedule to the HIGLAS test site as required to accommodate their HIGLAS enabled contractors.   40.3.6 - Testing Requirements Applicable to all CWF Data Centers (Hosts)  (Rev. 97, Issued: 01- 15-16, Effective: 09- 21-15, Implementation: 09- 21-15)  Each CWF data center or CWF sector host shall:    Forward all satellite software and documentation to the satellites (contractors) to which they serve as the primary production host;    Install the CWF quarterly release software in a designated test region;    Make the designated test region available their satellites (users) for testing;    Coordinate test data , such as beneficiary data, with the user testers;    Process all satellite files submitted by the users and return all corresponding reply files generated for users;    Report release problems to the CWF Maintainer and CMS;    Verify with CMS that each of its satellites submitted at least one test file during user testing; and    The CWF Host shall support future date testing by the MACs.    The CWF Host shall review date simulation schedule submitted by the FISS FWG, MCS FWG, and DMOP TAG.   40.3.7 - Timeframe Requ irements for all Testing Entities  (Rev. 97, Issued: 01- 15-16, Effective: 09- 21-15, Implementation: 09- 21-15)  The SSMs, STC, and MAC shall operate under the testing timeframes shown below for each quarterly release:   Timeframe Requirements for Testing Enti ties   1. The Medicare A/B, DME MAC  or User testing period shall begin four weeks prior to production implementation.  2. The Beta  testing period shall begin eight weeks prior to production implementation.  The CWF and standard system Beta testers shall have an exclusive four -week testing timeframe prior to the initiation of user testing.    The Beta tester shall complete a functional System Test and Regression Test before the shared system is released to the User community.    Beta testing must also continue through the User testing period.  The Beta tester may initiate performance testing during the user testing period.   3. Exclusive CW FM and SSM testing shall continue until Beta testing is initiated eight weeks prior to production implementation.  The SSM and CWFM shall complete a Unit Test (on all components), Integration Test, System Test, and Regression Test prior to distributing the  shared system release to the designated Beta tester.  For all integration, system, and regression testing, the SSM shall use the most recent version of any third party or CMS provided software components (e.g., Pricer, OCE, MCE, Grouper) they are provided.  The SSM shall continue testing beyond the exclusive maintainer -testing window due to the late receipt of some third party or CMS provided software components such as the Pricers and OCE.   40.3.8 - Testing Documentation Requirements (Rev. 97, Issued: 01- 15-16, Effective: 09- 21-15, Implementation: 09- 21-15)  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.