Part 4 - Iowa Medicaid Enterprise

RFP MED-12-001 | Technical ProposalIowa Medicaid Enterprise System Service Procurement | MMIS and Core MMIS OperationsAfter the completion of the conversion, a final report will be issued which will detail all counts,exceptions, and validations by module.Team Noridian's data conversion task will ensure that:• Data conversion does not pose a risk to the implementation.• Converted data does not impede application functionality or performance.• Conversion is an integral part of the project from the beginning.• Conversion data is available to support application testing as it will yield more valuable testing withrealistic data.• Management has complete visibility of the progress of conversion and any issues.• Conversion is complete meaning that 100 percent of all required data is converted and accounted for.• Conversion is accurate meaning that 100 percent of all required data meets the business rules of thenew system and relates correctly to other data within the system.Team Noridian's data conversion approach has evolved over several decades and the lessons learnedthrough multiple implementations. This approach will bring a great value to the Department in ensuringthat the objectives of the Department are met; thereby successfully implementing the system. Figure 8-63below provides a quick overview of the major tasks within the overall data conversion strategy identifiedfor IME.Data Conversion ApproachThe Conversion Plan process will be used to fully scope the conversion effort.The conversion mapping process will identify the transformations from the legacy system to the newsystem and will define how the data fits in the new system and how it relates to other data.Team Noridian's conversion exception reporting process ensures that all conversion exceptions areidentified and tracked to closureTeam Noridian's conversion validation process compares the actual results to the expected results andidentifies any discrepancies.Team Noridian's conversion process is iterative by design, which means preliminary conversion can easilybe run for testing purposes.Our past experience with MMIS conversions has allowed us to develop a successful conversion strategy.Team Noridian has experience with multiple MMIS conversions and understands the need to integrateconversion into the project as a key function from the beginning.Team Noridian's conversion testing process will validate conversion results against the conversionmappings and transformations. Any discrepancies will be reported.A combination of weekly status reporting including a summary of all conversion count and exceptionreports for any conversion runs in the current week and a list of all outstanding issues.Team Noridian's conversion counts and exceptions reporting process ensures that all conversion countsare captured and all exceptions are identified and tracked to closure. Team Noridian's conversion testingprocess will validate conversion results against the conversion mappings and transformations. Anydiscrepancies will be reported. The conversion manager will provide an analysis of the test resultsincluding any associated impacts and action plans.Team Noridian's conversion testing process will validate conversion results against the conversionmappings and transformations. Any discrepancies will be reported. The conversion manager will providean analysis of the test results including any associated impacts and action plans. This testing process isdesigned to be iterative and can be started from early on. It can be repeated as part of unit testing, systemtesting, and UAT, and is scalable from the smallest unit of conversion up to the full conversion.Key Factors and OutcomesConversion scope will be identified early in theproject and risks will be minimized.The conversion mapping will clearly identify how thedata will fit into the system.Users and management will have visibility of theconversion exceptions and will be able to takecorrective action.Corrective action can be taken if discrepancies in theconversion results are found.The quality of testing the conversion and theapplication will both be improved.Conversion risks to the implementation will beminimized.Corrective action can be taken if discrepancies in theconversion results are found.Management will be aware of the status and issuesin conversion.Users and management will have visibility of theconversion exceptions and validation issues and willbe able to take corrective action.Corrective action can be taken if discrepancies in theconversion results are found.Figure 8-63. Data Conversion Strategy. The various tasks and expected outcomes of Team Noridian'sapproach to data conversion.8 | 106