Part 4 - Iowa Medicaid Enterprise

RFP MED-12-001 | Technical ProposalIowa Medicaid Enterprise System Service Procurement | MMIS and Core MMIS OperationsTeam Noridian will conduct the following conversion planning activities:• Establish conversion processes including associated stages, tasks, activities, ownership, and deliverableswith interdependencies with other development methodology processes for the overall system• Develop conversion procedures describing how each task and activity will be performed and verified• Establish conversion tools leveraging experience on similar conversion efforts in other states• Develop descriptions for creating and maintaining the master list of legacy data files, which willidentify data in the legacy source environments and will contain important information such as:• Source of the data (e.g., legacy feed, legacy program data, external data source, future data entry,or manual data conversion)• Flow of the data• Data format and storage (i.e., flat positional data, structured extract, and unstructured extract)• Establish conversion plans for manual data including a strategy and detailed process for how thismanual data will be converted• Establish the migration strategy for documents, images, and other files to be converted into TeamNoridian’s OnBase solution, where historical images are stored during conversion• Establish the conversion execution plan describing how the tasks and activities will be carried out• Develop the conversion test strategy• Establish and publish the proposed conversion production timeline including day-by-daycutover activitiesConversion planning will occur early in the project and continue throughout the entire project life cycle.During requirements verification, the conversion team will update the Conversion Plan and submit this tothe state for approval within 10 days of completion of requirements verification.The order of conversion is critical, which is why planning for conversion will require consideration as towhat data will serve as a foundation to convert other data. At a high level, conversion will beimplemented in three phases or tiers:• Reference data set conversion. This layer represents the reference data that stores all codes andsetups used in the master and transaction layers. Examples include the data dictionary lookup codesand descriptions.• Master data set conversion. This layer represents the master data that enables transaction processing.Examples include procedure codes, diagnosis codes, or drug codes.• Non-transactional data sets conversion. This layer represents data sets that are required to supporttransaction, such as claims and service authorizations. Examples include provider and enrollees.• Transactional data set conversion. This layer represents the transaction data that drives the newMMIS. Examples include claims and service authorizations.Data Conversion Specifications and MappingThe data conversion specifications and mapping activity must begin with a thorough analysis of the dataconversion requirements. This analysis will be conducted in parallel and integrated with the new MMISbusiness area requirements validation sessions. This data conversion analysis will begin with dataidentification. Data identification shall include the development of a list of input and output files, thedevelopment and collaborative review of the legacy feed list, and a review of the legacy data dictionaryand layouts. Once data identification is completed for each business area, Team Noridian’s dataconversion team will develop the data staging model and analysis, including the following:• Development of data modeling staging schemas• Preparation of staging data and staging exception reports• Identification of all data requirements and source data• Assessment of staged data8 | 108