Part 4 - Iowa Medicaid Enterprise

More documents

Recommendations

Info

RFP MED-12-001 | Technical ProposalIowa Medicaid Enterprise 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).• Participate 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
RFP MED-12-001 | Technical ProposalIowa Medicaid Enterprise System Service Procurement | MMIS and Core MMIS OperationsTeam Noridian will submit the documents for the Department implementation team in accordance withthe specified 10 business days of review period and is accounted for in Team Noridian's project WBSand the schedule. Since conversion will be an integral part of the project from the beginning, theconversion team will be able to submit early drafts of conversion requirements to aid in defining theconversion effort.8.3.2.1.2 Contractor ResponsibilitiesRFP Section 6.3.2.1.2, Requirements a through hTeam Noridian understands that data conversion is a key success factor for successful implementation ofnew MMIS. Team Noridian's data conversion approach will accurately convert all required data elementsfrom legacy MMIS to new MMIS. Our approach includes the following major activities:• Plan and Manage Conversion. Team Noridian will develop the detailed Conversion Plan, whichestablishes the processes, roles, responsibilities, verification mechanisms and expected outcomes forconversion. Throughout the conversion period, Team Noridian's conversion task manager willcoordinate between the functional, development, test, incumbent, and Department teams to ensure acomplete and accurate data conversion.• Identify and Analyze Data and Sources. Team Noridian will develop and review the legacy feedlist and review the legacy data dictionary and layouts. In addition, Team Noridian will participate inrequirements verification sessions and review the SFP requirements to identify the data needed tosupport the new MMIS and the source of record for this data.• Stage Data. Data feeds will be staged in the staging area for further processing. Staging exceptionsand staging profiling analysis results will be produced and analyzed to determine the resolution forthe exception.• Verify Data. Basic checks will be performed to ensure that the source files are structurally correctand complete. Team Noridian will then identify data cleansing and any data correction activities thatneed to be performed manually.• Data Mapping. Data will be mapped field-by-field from the legacy source to the new MMIS. Datamapping activities will result in the Data Conversion Specifications and Mapping Document.• Data Cleansing and Correction. Team Noridian will document the data cleansing and datacorrection rules as we perform data mapping.• Data Transformation. Team Noridian will transform the data based on the specifications andproduce exception reports. The above steps will be conducted iteratively until all of the businessdomains are converted. Team Noridian expects that transactional data, such as claims and serviceauthorizations, will be partially transformed in data sets, while some business domains will betransformed completely in one pass.• Testing and Verification. The verification process is an iterative one. As a value-add in theiVision360 approach, Team Noridian converts and tests data during Development and System Test. Inaddition, preliminary converted data is loaded for parallel testing and full conversion data for UAT.• Final Target Loading. Final target loading is the process that will be started from scratch on aproduction schema with proven data conversion procedures. Target audit statistics will be collectedand verified against source data statistics and expectations.Team Noridian understands the business need to capture the information that is captured on paper, andthrough its proposed solution, automates various aspects of the current paper processes. Our conversionapproach includes not only the current electronic data but also includes the data sources such as imageddocuments and the meta /index data that identifies the scanned images. eCAMS will associate theimaged paper information to the electronic data records such as claims, providers, members, cases, andprior authorizations.As part of Team Noridian's data source identification described in the Conversion Plan above, TeamNoridian will review all data sources and define the list of data elements from each source that will8 | 115
Page 1 and 2:
RFP MED-12-001 | Technical Proposal
Page 3 and 4:
Page 5 and 6:
Page 7 and 8:
Page 9 and 10:
Page 11 and 12:
Page 13 and 14:
Page 15 and 16:
Page 17 and 18:
Page 19 and 20:
Page 21 and 22:
Page 23 and 24:
Page 25 and 26:
Page 27 and 28:
Page 29 and 30:
Page 31 and 32:
Page 33 and 34:
Page 35 and 36:
Page 37 and 38:
Page 39 and 40:
Page 41 and 42:
Page 43 and 44:
Page 45 and 46:
Page 47 and 48:
Page 49 and 50:
Page 51 and 52:
Page 53 and 54:
Page 55 and 56:
Page 57 and 58:
Page 59 and 60:
Page 61 and 62:
Page 63 and 64:
Page 65 and 66:
Page 67 and 68:
Page 69 and 70:
Page 71 and 72:
Page 73 and 74:
Page 75 and 76:
Page 77 and 78:
Page 79 and 80:
Page 81 and 82:
Page 83 and 84:
Page 85 and 86:
Page 87 and 88:
Page 89 and 90:
Page 91 and 92:
Page 93 and 94:
Page 95 and 96:
Page 97 and 98:
Page 99 and 100:
Page 101 and 102:
Page 103 and 104:
Page 105 and 106:
Page 107 and 108:
Page 109 and 110:
Page 111 and 112:
Page 113 and 114:
Page 115 and 116:
Page 117 and 118:
Page 119 and 120:
Page 121 and 122:
Page 123 and 124: RFP MED-12-001 | Technical Proposal
Page 173: RFP MED-12-001 | Technical Proposal
Page 225 and 226:
Page 227 and 228:
Page 229 and 230:
Page 231 and 232:
Page 233 and 234:
Page 235 and 236:
Page 237 and 238:
Page 239 and 240:
Page 241 and 242:
Page 243 and 244:
Page 245 and 246:
Page 247 and 248:
Page 249 and 250:
Page 251 and 252:
Page 253 and 254:
Page 255 and 256:
Page 257 and 258:
Page 259 and 260:
Page 261 and 262:
Page 263 and 264:
Page 265 and 266:
Page 267 and 268:
Page 269 and 270:
Page 271 and 272:
Page 273 and 274:
Page 275 and 276:
Page 277 and 278:
Page 279 and 280:
Page 281 and 282:
Page 283 and 284:
Page 285 and 286:
Page 287 and 288:
Page 289 and 290:
Page 291 and 292:
Page 293 and 294:
Page 295 and 296:
Page 297 and 298:
Page 299 and 300:
Page 301 and 302:
Page 303 and 304:
Page 305 and 306:
Page 307 and 308:
Page 309 and 310:
Page 311 and 312:
Page 313 and 314:
Page 315 and 316:
Page 317 and 318:
Page 319 and 320:
Page 321 and 322:
Page 323 and 324:
Page 325 and 326:
Page 327 and 328:
Page 329 and 330:
Page 331 and 332:
Page 333 and 334:
Page 335 and 336:
Page 337 and 338:
Page 339 and 340:
Page 341 and 342:
Page 343 and 344:
Page 345 and 346:
Page 347 and 348:
Page 349 and 350:
Page 351 and 352:
Page 353 and 354:
Page 355 and 356:
Page 357 and 358:
Page 359 and 360:
Page 361 and 362:
Page 363 and 364:
Page 365 and 366:
Page 367 and 368:
Page 369 and 370:
Page 371 and 372:
Page 373 and 374:
Page 375 and 376:
Page 377 and 378:
Page 379 and 380:
Page 381 and 382:
Page 383 and 384:
Page 385 and 386:
Page 387 and 388:
Page 389 and 390:
Page 391 and 392:
Page 393 and 394:
Page 395 and 396:
Page 397 and 398:
Page 399 and 400:
Page 401 and 402:
Page 403 and 404:
Page 405 and 406:
Page 407 and 408:
Page 409 and 410:
Page 411 and 412:
Page 413 and 414:
Page 415 and 416:
Page 417 and 418:
Page 419 and 420:
Page 421 and 422:
Page 423 and 424:
Page 425 and 426:
Page 427 and 428:
Page 429 and 430:
Page 431 and 432:
Page 433 and 434:
Page 435 and 436:
Page 437 and 438:
Page 439 and 440:
Page 441 and 442:
Page 443 and 444:
Page 445 and 446:
Page 447 and 448:
Page 449 and 450:
Page 451 and 452:
Page 453 and 454:
Page 455 and 456:
Page 457 and 458:
Page 459 and 460:
Page 461 and 462:
Page 463 and 464:
Page 465 and 466:
Page 467 and 468:
Page 469 and 470:
Page 471 and 472:
Page 473 and 474:
Page 475 and 476:
Page 477 and 478:
Page 479 and 480:
Page 481 and 482:
Page 483 and 484:
Page 485 and 486:
Page 487 and 488:
Page 489 and 490:
Page 491 and 492:
Page 493 and 494:
Page 495 and 496:
Page 497 and 498:
Page 499 and 500:
show all

Part 4 - Iowa Medicaid Enterprise

Create successful ePaper yourself

Delete template?

Save as template?