13.07.2015 Views

Part 4 - Iowa Medicaid Enterprise

Part 4 - Iowa Medicaid Enterprise

Part 4 - Iowa Medicaid Enterprise

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

RFP MED-12-001 | Technical Proposal<strong>Iowa</strong> <strong>Medicaid</strong> <strong>Enterprise</strong> System Service Procurement | MMIS and Core MMIS Operationsability to create interfaces and publish them as services, monitor performance, provide alerts andnotifications, and when appropriate, automate error handling and exception resolution, are out-of-the-boxcapabilities of EXACT and will simplify the development, implementation, and testing of the interfacesduring the start-up and implementation phase.EXACT automatically produces a full audit trail of all service activities for an interface. This information,including error logs, transfer speed information, exception resolution status, and success or failure of anyparticular transfer is pushed to the eCAMS HealthBeat Dashboard. This provides the Department with thebenefit of having a single point of access to not only access important information relating to eCAMS butto monitor and generate reports relating to interface activity and performance as well.As discussed in Section 8.3.2.3, Testing Tasks, integration testing of the interfaces will begin whenmodule testing is completed in accordance with the agreed upon module test exit criteria for a businessarea. Many of the business areas and associated modules will complete testing in a staggered fashion.Integration test will encompass testing within an individual module (end-to-end within the module) andthen expand to cover across modules and, finally, expand to the breadth of the system including externalinterfaces. Team Noridian will establish an integration test plan that logically groups business areas andassociated modules so that integration testing can begin to test meaningful integration points while otherfunctionality are still completing module testing. In this fashion, interfaces are tested continuouslythroughout the entire start-up and implementation phase and performance measurements are reviewed andhoned on an iterative basis as needed.The user acceptance test further exercises each of the defined interfaces and provides assurance that thenew MMIS is operational and functions according to Department’s requirements and that manual andautomated functions and interfaces are in place and functioning properly. UAT is designed to ensure thatall MMIS functions are tested by users, including but not limited to, proper functioning of edits, audits,and business rules; the accuracy of claim records payment and file maintenance; and the format andcontent of all system outputs, including outputs from reporting functions. UAT also offers the opportunityto test user manuals, forms, procedures and business processes. At the conclusion of the UAT for eachimplementation release, all interfaces will have been fully tested and adjusted, as needed to meet allperformance requirements. As noted above, we conduct a final verification of these interfaces through theimplementation checklist.8.4.1.2.7 Repeat TestingRFP Section 6.4.1.2, Requirement nORT will be focused on the ability of Team Noridian to establish readiness for operations. The plan willoutline the processes and the implementation checklists which will be used to record the successfulcompletion of each readiness activity. During ORT operations test personnel will verify the ability of theoperations staff to perform day to day activities of processing claims, claims payment, workflow,providing customer service through phone and fax, imaging, prior authorization, daily operational reports,and all other business functions. Daily activities will include exercising the production job schedulesincluding claims loading, adjudication, and payment cycles using production claims volumes. At thecompletion of operational readiness test, all production capabilities will have been exercised and all testand implementation checklists completed. Any discrepancies uncovered during testing would bedocumented, reviewed and a plan of action determined approved by the Department prior to consideringthe testing completed. Team Noridian will repeat portions of the ORT if requested by the Department toverify system and business functions throughout the ORT and transition to operations tasks.8.4.1.2.8 Begin OperationsRFP Section 6.4.1.2, Requirements m, o, and pThe Transition to Operations Plan and implementation checklist includes all activities needed to beverified for the start up of operational activities. As described above, the ORT activities provide the8 | 187

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!