Part 4 - Iowa Medicaid Enterprise

RFP MED-12-001 | Technical ProposalIowa Medicaid Enterprise System Service Procurement | MMIS and Core MMIS Operationsentire test case. It is possible for a test case to be completed with minor issues detected at one or morepoints of validation and still obtain an overall assessment of pass.The testers follow the defect tracking process if the results of the test validation indicate that a correctionin the code or requirement is needed. This defect tracking process is documented in the defectmanagement plan. Defects may be opened directly in Bugzilla by the tester.Additional test cases, scripts, and evidence which may be collected separately (e.g., batch results), willalso be manually checked into Subversion along with all other test artifacts.Sometimes a pass or fail condition cannot be readily determined. The guidelines in Figure 8-88 areprovided to assist all parties involved in each test phase to determine pass or fail for each test case.GuidelinesPass (P)Pass with constraints (P1)Fail (F#)The results of the action comply with the expected resultsThe results do not completely comply with the expected results but the results are a user inconvenience or other minorinconvenience. A Severity 4 or 5 classification defect report is created. Refer to the Defect Management Plan for severitydefinitions.F3: The function has failed but there is a workaround such that testing of that business area can continue. A Severity 3 defect iscreatedF2: The function has failed and there is no workaround. A Severity 2 defect is createdF1: The action results in a system crash or results in damage to data (e.g., wrong results or a loss of data). A Severity 1 defect iscreated.Refer to the Defect Management Plan for severity definitionsFigure 8-88. Pass or Fail Guidelines. Provides all stakeholders easily determination of pass or failureresults for each test case.Operational Readiness Testing (ORT)RFP Section 6.3.2.3.2.1.8, Requirements a through eThe Operational Readiness Test (ORT) is the final step to ensuring the new MMIS is ready to assumeproduction operations. Testing completed up to this point has established the new MMIS has met thedocumented requirements and design as approved by the Department. This next step is designed to ensurethat the system can assume operations successfully, processing production volumes of claims and payingaccordingly without loss of service to clients or providers. ORT is also designed to assess the readiness ofthe operational IME staff to ensure they are able to perform manual operations task as well as automatedtasks utilizing the MMIS systems. This includes functions such as customer service, correspondencemanagement, financial operations, operations workflow, electronic documents management, manualclaims resolutions, and disaster recovery.The ORT test plan will be divided into sections, each dedicated to specific goals. These sections will bedivided as follows:• Parallel Test process, procedures and results delivery• Load and Stress test process, procedures and results delivery• Operational Readiness test process, procedures and results delivery• Disaster Recovery and Business Continuity testing process, procedures and results delivery• In developing the ORT Plan, Team Noridian will solicit input from the Department as well as theIV&A and Quality Assurance vendors, for specific measures and metrics which should becaptured as part of the Operational Readiness Test activities. These measures will be included inthe test plans and results captured in the Final ORT results report.Parallel Test. The parallel test will be conducted by running selected subset of production claims throughboth the new MMIS and legacy systems to ensure the new MMIS is producing the appropriatelycomparable results. This testing is a highly structured process using a controlled set of claim transactions8 | 154