Single Testing Contractor (STC) Non-Testable Conditions and

40.3.11 - Single Testing Contractor (STC) Non-Testable Conditions and Potential Testing Impacts (Rev. 125; Issued: 07-05-19, Effective: 08-05-19, Implementation: 08-05-19) ID LOB STC Not Testable Conditions and Potential Testing Impacts 1 FISS, MCS, VMS Electronic Correspondence Referral System functionality (ECRS) - The STC does not interface with ECRS. 2 FISS, MCS, VMS Recovery Audit Contractor (RAC) and/or Recovery Audit Contractor Data Warehouse (RACDW) - The STC does not interface with the RAC or the RACDW. The STC does have the ability to test RAC related changes in the shared system applications. 3 FISS, MCS, VMS Non-Base Job System Processing. The STC does not test non-base jobs. 4 FISS ECPS events – The STC does not test MAC controlled ECPS events. 5 VMS Super Op events - The STC does not test MAC controlled Super Op events. 6 MCS SCF Logic - The STC does not test MAC controlled SCF Logic. 7 FISS, MCS, VMS Local Coverage Determinations (LCDs) - The STC does not test MAC LCD or medical policy. MACs conduct LCD and medical policy testing. 8 MCS Interactive Voice Response (IVR) - STC would not do end-to-end testing of MCS base system changes for the IVR. The STC does have the ability to test IVR related changes in the shared system. 9 MCS Automated Response Unit (ARU) - STC would not do end-to-end testing of MCS base system changes for the ARU. The STC does have the ability to test ARU related changes in the shared system. 10 FISS, MCS, VMS Optical Character Recognition (OCR) - The STC does not test changes to OCR functionality. 11 FISS, MCS, VMS, CWF Contractor ID specific logic – The STC is unable to conduct state or jurisdiction specific testing that requires a specific contractor number for processing. 12 FISS, MCS, VMS Printing – The STC does not have a print vendor and does not test backend print/mail functions. 13 FISS, MCS, VMS, CWF Testing that requires large volumes of data – The STC environment contains a limited number of claims. Thus, the STC may not be able to identify volume- related issues in its test environment. 14 FISS, MCS, VMS, CWF Runbooks are documentation artifacts maintained by the SSMs that provide instructions regarding how jobs are to be scheduled (daily, weekly, monthly, on request etc.) and predecessor/successor relationships for jobs that must precede or succeed, as well as containing comments on known abend return codes the job is programmed to return sometimes including instructions on how to rerun/restart each abend return code. As Runbooks are documentation in nature the STC does not test Runbooks. 15 CWF Enrollment Database (EDB) - The STC does not interface with the EDB system. 16 FISS, MCS, VMS, CWF Processes that are designed to only work in a test environment - Processes that are designed to only work in a test environment and will never be promoted or utilized in the production environments. This includes the internal testing facility (ITF), the CWF response generator, the HIGLAS response generator, and the MBI generator. 17 FISS, MCS, VMS Healthcare Integrated General Ledger Accounting System (HIGLAS) - The STC is not responsible for testing HIGLAS changes. The shared systems will continue to test HIGLAS. 18 FISS INFOMAN - The STC does not test CRs implemented by the FISS SSM that update the release identifier on the main CICS screen in the FISS application. 19 FISS, MCS, VMS, Electronic Funds Transfer (EFT) - The STC does not conduct testing with financial institutions, and is therefore unable to test the EFT transactions. The STC inspects the EFT files created from the shared systems and processes them. 20 FISS, MCS Payment File Development Contractor (PFDC) - The STC does not interface with the PFDC system. Changes to the file are tested by the STC by manually sending and receiving a file. The STC inspects the files created from the shared systems and processes them. 21 FISS, MCS, VMS, CWF Integrated Data Repository (IDR) - The STC can test IDR file changes as part of the shared system, but the files are not automatically sent to the IDR contractor. STC manually sends files to the IDR contractor twice during the release. The STC inspects the files for accuracy created from the shared systems and processes them. 22 FISS Quality Improvement Evaluation System (QIES) - The STC does not interface with QIES. The STC inspects the files for accuracy created from the shared systems and processes them. 23 FISS, MCS, VMS, CWF Provider Statistical and Reimbursement System (PS&R) - The STC does not interface with the PS&R system. The STC inspects the files for accuracy created from the shared systems and processes them. 24 FISS, MCS, VMS, CWF Production Performance Monitoring System (PULSE) - The STC does not interface with PULSE. The STC inspects the files for accuracy created from the shared systems and processes them. 25 MCS Provider Enrollment System (PES) - The STC does not have the PES application that is used exclusively by the Railroad Retirement Board Specialty MAC. The STC is unable to test the PES application. 26 FISS, MCS, VMS Provider Enrollment Chain and Ownership (PECOS) - The STC does not utilize the PECOS system to generate enrollments. STC manually creates a file when needed for testing. 27 FISS, MCS, VMS Electronic Submission of Medical Documentation (esMD) - The STC does not have connectivity with esMD. The STC does have the ability to test esMD related changes in the shared system. 28 CWF Affordable Care Organization (ACO) – The STC does not have connectivity with the ACO. The STC does have the ability to test ACO related changes in the shared system. 29 CWF CWF MBI (Medicare Beneficiary ID) XWALK - There are some connectivity tests that STC cannot execute since the XWALK in STC is set up differently compared to production. The XWALK in the STC environment is embedded in the CWF CICS region that houses all other STC CWF data whereas the XWALK in production is in a separate CICS region called Host K. The STC does not connect to Host K.