13.07.2015 Views

Part 4 - Iowa Medicaid Enterprise

Part 4 - Iowa Medicaid Enterprise

Part 4 - Iowa Medicaid Enterprise

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

RFP MED-12-001 | Technical Proposal<strong>Iowa</strong> <strong>Medicaid</strong> <strong>Enterprise</strong> System Service Procurement | MMIS and Core MMIS OperationsTeam Noridian will also rely on the Department to act as a liaison with the incumbent and externalpartners that will provide data or documentation required for the conversion effort.Data cleansing and correction is an area where the Department will need to be actively engaged withTeam Noridian to ensure that data is converted correctly and that the production system can correctlydetermine eligibility, calculate payments, and report data to internal and external entities.Team Noridian defines data cleansing and data correction responsibilities as follows. Data cleansing isperformed where a rule-based solution can be documented and developed to convert the data into the newMMIS. In addition, the rule-based solution cannot have the potential to create privacy issues or may resultin incorrect payment, access to care, or mandated reporting. Where a data cleansing solution is available,Team Noridian, often with input from the Department, will document the rule-based solution andappropriate validation rules. The Department will provide feedback and approval on data cleansing rules.Data correction generally involves data that is missing, corrupted, or tracked inconsistently in a legacysystem, and cannot be derived based on rules or from other available data. Data correction is requiredwhen there is no rule-based solution that can be defined or any rule-based solution has the potential tocreate privacy issues or incorrect payments, access to care, or mandated reporting.Because data correction cannot be performed in a rules-based manner without affecting services toproviders, enrollees, or external entities, it is necessary for the data to be corrected by a responsible partywho has accurate information with which to correct the problem. When data correction activities arerequired, Team Noridian will document the need for data correction and expected format of the result, aswell as the critical timeline for resolution.A detailed explanation of the Department's responsibilities by stage of conversion is provided inFigure 8-66.SubtaskConversion PlanConversion DesignConversionDevelopment and TestParallel and UserAcceptance TestDepartment Responsibility• Provide knowledgeable staff to participate in data conversion activities (e.g., planning, design, documentation, or testing).• Provide existing system documentation and data dictionary for all data required to be converted.• Provide source data files to Team Noridian for mapping, development, testing and final conversion of all existing new MMIS data.• Respond to Team Noridian's inquiries related to the Department's policies and procedures within the work breakdown structure(WBS) schedule to avoid delay of the deliverables.• Review, provide feedback, and approve the Conversion Plan.• Review, provide feedback, and approve the Data Conversion Test Results.• Monitor Team Noridian performance.• Coordinate with the incumbent and external agencies where required.• Assist in identifying source(s) of data and determining the primary source or system of record• Provide, or assist in the process to provide, existing system documentation and data dictionary for data required to be converted.• Respond in a timely manner to Team Noridian's inquiries and requests for clarification related to data mapping and systemconversion requirements• Provide the layouts, field definitions, field range values, and definitions at the early stages of the project after providing initialdocumentation, if not previously provided or available from another source.• Help Team Noridian understand the primary key of the feed and the relationship to other feeds.• Review, provide feedback, and approve data mapping rules.• Assist in the identification, review, and approval of data cleansing and correction rules.• Resolve or coordinate resolution of data correction issues and missing referential values in a timely manner.• Provide legacy data from the incumbent within 60 days of the contract award.• Coordinate all communications and additional data gathering between Team Noridian and the current contractor(s).• <strong>Part</strong>icipate in testing.• Monitor the performance of Parallel and User Acceptance Testing.• Approve all routines for data conversion before final application to the production version of the system.• Report data conversion defects and issues in a timely manner as laid out in the Risk and Issue Management Plan and System TestPlan.• Review, provide feedback on, and approve Data Conversion Test Results.Figure 8-66. Department Responsibilities during Data Conversion. This table maps the specificresponsibilities of the Department to different conversion activities.8 | 114

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

Saved successfully!

Ooh no, something went wrong!