Part 4 - Iowa Medicaid Enterprise

RFP MED-12-001 | Technical ProposalIowa Medicaid Enterprise System Service Procurement | MMIS and Core MMIS OperationsTool Type Definition ToolsetDefect Trackingcorrect version of the code, resources share accessto the same code, and code is baselined at theappropriate stages of the project.Logging, managing, and reporting of defects foundduring conversion testing is performed using anindustry standard defect tracking tool that iscommon across the DDI phase of the project.Figure 8-64. Data Conversion Toolset. The tools selected by Team Noridian for the new MMISconversion are industry-leading products that Team Noridian has used successfully on past MMISconversion efforts in Washington, Michigan, and Maine.Data Conversion Execution and TestingThe Team Noridian data conversion team will work closely with the test team and the Department todevelop a detailed Data Conversion Test Plan that clearly describes our approach to data conversion,execution, and testing. The test plan will include our approach to iterative and repeated execution and testingof conversion processes, and the approach to ensure that errors are detected, corrected, and retested.The repeated execution and testing of data conversion processes includes multiple iterations of datatransformation, target loading, and data conversion verification. The data transformation step includes theprocesses for transforming the data, identifying data quality gaps and problems, and generating targetloading exception reports.The target-loading step encompasses subsystem independent conversion, a mechanism to re-convert andapply patches, historical data conversion, and business process area integration. The data conversionverification step includes internal data verification, documentation of queries used and results, dataverification performed by the test team, and documented results by the test team.Execution of data conversion will aim for the following:• Repeatable conversion. Automatically clear the data created by the previous conversion instance forthe specific business process area. This approach enables Team Noridian to conduct independentbusiness area conversions and later integrate with the larger system.• Scalable conversion. Accommodate current needs and at the same time manage the scope to allowflexibility for rule changes.• Exception handling. Quantify errors in terms of input and output record statistics. Statistics for thenumber of records converted, number of errors, and new system inserts will be provided to theDepartment for each test execution and the production execution.• Capturing and documenting the errors. Develop potential solutions, business rules, fixes, and retest.The exceptions for each iteration will be documented and will be available for later retrieval for anyfuture research.• Integrating with configuration and test management. Defects identified during testing will be loggedin Bugzilla and assigned to the conversion team for resolution. These defects will follow the sameprocess for analysis, correction, retest, and regression testing, as outlined in the System Test Plan.• Identifying data elements that are not required by the target system as they are either obsolete or werederivative fields in the legacy MMIS.Testing the converted data is an important activity of data conversion. Manual and automated converteddata will be tested. During data conversion testing, Team Noridian will validate that:• The entire set of mapping rules defined in the mapping specifications document are incorporated• The converted data follows the data structure model of the new MMIS• All the fields mapped from the current MMIS are converted correctly in the new MMIS• All the constraints of the new MMIS are fulfilledBugzilla8 | 111