Part 4 - Iowa Medicaid Enterprise

More documents

Recommendations

Info

RFP MED-12-001 | Technical ProposalIowa Medicaid Enterprise System Service Procurement | MMIS and Core MMIS OperationsFigure 8.57. Team Noridian's Data Conversion Task Overview. The data conversion diagram provides a“cue card” to understand the key data conversion concepts quickly.Team Noridian understands that data conversion is a critical activity and an integral part of theconstruction process. To ensure that conversion activities are integrated and consistent with the overall8 | 92
RFP MED-12-001 | Technical ProposalIowa Medicaid Enterprise System Service Procurement | MMIS and Core MMIS Operationsapproach, the conversion team will be integrated with the business area teams and will jointly attendrequirements validation sessions and collaborative design sessions to ensure a common understanding andclear identification of conversion requirements. All data conversion activities will be conducted in parallelwith the IME business area teams.Team Noridian will follow iVision360 approach which will allow any data issues to be identified veryearly and will allow for backup plan development if necessary. Data conversion is one of the firstactivities to be started during a DDI project and the only dependency to beginning work is theestablishment of the overall project work plan.Conversion 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 fifteen (15) days of completion of requirements verification.Team Noridian will conduct the following conversion planning activities:• Establish conversion processes, including associated stages, tasks, activities, ownership, anddeliverables with interdependencies with other development methodology processes for theoverall 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, ormanual 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 activitiesTeam Noridian will develop a detailed Conversion Plan. Team Noridian will work with the Department todevelop and deliver a Conversion Plan that will include the following:• Conversion processes, including associated stages, tasks, activities, ownership, and deliverables withinterdependencies with other development methodology processes for the rest of the system.• Conversion procedures describing how each task and activity will be performed.• The use of conversion tools. Team Noridian will leverage our experience and tools based on similarconversion efforts in other states.• A description of how the master list of legacy data files is created and maintained. This master listwill identify data in the legacy source environment, which contains important information such as:• Source of data (e.g., legacy feed, legacy program data, non-legacy external data source, futuredata entry, or manual data conversion)• Flow of data• Format (i.e., flat positional data, structured extract, and unstructured extract) and storage.• Manual conversion plans with a strategy and detailed process on how manual data will be converted.• Data conversion execution strategy describing how the tasks and activities will be carried out.8 | 93
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: RFP MED-12-001 | Technical Proposal
Page 151: RFP MED-12-001 | Technical Proposal
Page 203 and 204:
Page 205 and 206:
Page 207 and 208:
Page 209 and 210:
Page 211 and 212:
Page 213 and 214:
Page 215 and 216:
Page 217 and 218:
Page 219 and 220:
Page 221 and 222:
Page 223 and 224:
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?