Part 4 - Iowa Medicaid Enterprise

More documents

Recommendations

Info

RFP MED-12-001 | Technical ProposalIowa Medicaid Enterprise System Service Procurement | MMIS and Core MMIS Operationsinvolve the candidates and gain their acceptance into the beta program. Beta testing schedules will beobjectives driven meaning the schedules will be designed to focus on achieving the desired goals frombeta testing (i.e., verify usability, test specific complex interactions, etc). Beta tests will not have theformality of test cases. Instead, beta test users will be asked to focus on particular functional areas. TeamNoridian will provide web-based orientation and training for the system under test and provide a webportal to collect feedback from beta test users.Disaster Recovery and Business Continuity Test. Disaster Recovery and Business continuity planninginvolves the development of interim measures designed to recover and sustain the critical informationtechnology (IT) services during an emergency, as well as reconstitute the pre-emergency system as soonas practicable. The goal is to ensure that critical and sensitive systems needed to support mission essentialfunctions continue to be operational in the event of major or minor interruptions, or a large-scale disaster.Team Noridian will implement a Disaster Recovery Business Continuity Plan (DRBCP) to ensure thatvital services can be recovered and reconstituted in the event that a major event occurs that renders itsresources unavailable. In order to accomplish this undertaking, it is necessary the Department identifyessential functions (as defined in Federal Preparedness Circular 65) that rely on the new MMIS. Since thenew MMIS supports Medicaid, a Federally-identified essential function, it is necessary to examine allessential function components that would adversely impact the Departments Medicaid mission in theevent the new MMIS were rendered unavailable for a significant period of time. The ORT Test plan willdocument how the process and procedures outlined in the DRBCP are verified to be implementedcorrectly and is operational. Plan testing is a critical element of a viable disaster recovery capability.Testing enables DRBCP plan deficiencies to be identified and addressed. Testing also helps evaluate theability of the recovery staff to implement the plan quickly and effectively. Testing will engage the MMISoperations disaster recovery team and would be limited to Classroom Exercises conducted in accordancewith team member training. Participants in classroom exercises, often called tabletop, walk through theprocedures without any actual recovery operations occurring. Classroom exercises are the most basic andleast costly of the two types of exercises and should be conducted before performing a functionalexercise. The tabletop exercise will take place prior to production implementation as part of the ORTTesting Period. Test results, lessons learned, and improvements based on test results will be documentedand reviewed by test participants and other personnel as appropriate and the DRBCP will be updated toreflect changes to procedures based on lessons learned.Operational Readiness Test Report. Operational Readiness Test will be focused on the ability of thecontractor to establish readiness for operations. The plan will outline the processes and the checklistswhich will be used to record the successful completion of each readiness activity. During ORT operationstest personnel will verify the ability of the operations staff to perform day to day activities of processingclaims, claims payment, drug rebate, workflow, providing customer service through phone and fax,imaging, prior authorization, daily operational reports, etc. Daily activities will include exercising theproduction job schedules including claims loading, adjudication, and payment cycles using productionclaims volumes. At the completion of operational readiness test, all production capabilities will have beenexercised and all test checklists completed. Any discrepancies uncovered during testing would bedocumented, reviewed and a plan of action determined approved by the Department prior to consideringthe testing completed.At the completion of all ORT Test activities, Team Noridian will submit a final test report that details theresults of all operations readiness testing and assessments, with a statement certifying the new MMIS, inits entirety of software, staffing, support personnel, IT and office facilities and infrastructure (e.g.,phones, power, office equipment, etc.), is in place and ready for operations. All measures, provided by theDepartment and IV&V and QA Services vendors, and documented in the approved ORT Plan will alsohave been met and documented in the Final test report.8 | 156
RFP MED-12-001 | Technical ProposalIowa Medicaid Enterprise System Service Procurement | MMIS and Core MMIS Operations8.3.2.3.3 DeliverablesRFP Section 6.3.2.3.3The list of deliverables generated by the test team during the various test processes is shown below. Thesedeliverables are sent to the Department during various stages of the testing. Artifacts are internal documentsused to accomplish the planned tasks and may be made available to the Department staff as needed. TeamNoridian will develop the deliverables listed in Figure 8-89 for operational readiness testing.Deliverable Agree to Meet? Section in ResponseUnit Test Plan Yes Section 8.3.2.3 Testing TasksRules Test Plan Yes Section 8.3.2.3 Testing TasksModule Test Plan Yes Section 8.3.2.3 Testing TasksIntegration Test Plan Yes Section 8.3.2.3 Testing TasksUAT Test Plan Yes Section 8.3.2.3 Testing TasksORT Test Plan Yes Section 8.3.2.3 Testing TasksUnit Test Cases and Scripts Yes Section 8.3.2.3 Testing TasksRules Test Cases and Scripts Yes Section 8.3.2.3 Testing TasksModule Test Cases and Scripts Yes Section 8.3.2.3 Testing TasksIntegration Test Cases and Scripts Yes Section 8.3.2.3 Testing TasksUAT Test Cases and Scripts Yes Section 8.3.2.3 Testing TasksORT Test Cases and Scripts Yes Section 8.3.2.3 Testing TasksUnit Test Results Yes Section 8.3.2.3 Testing TasksRules Test Results Yes Section 8.3.2.3 Testing TasksModule Test Results Yes Section 8.3.2.3 Testing TasksIntegration Test Results Yes Section 8.3.2.3 Testing TasksUAT Test Results Yes Section 8.3.2.3 Testing TasksORT Test Results Yes Section 8.3.2.3 Testing TasksTest Tracking (Execution and Defect Tracking) Yes Section 8.3.2.3 Testing TasksPerformance Tuning Document Yes Section 8.3.2.3 Testing TasksLetter Certifying UAT data has been provided Yes Section 8.3.2.3 Testing TasksFinal Testing Reports Yes Section 8.3.2.3 Testing TasksOperational Readiness Test Report Yes Section 8.3.2.3 Testing TasksUpdate of RTM Yes Section 8.3.2.3 Testing TasksFigure 8-89. Operational Readiness Testing Deliverables. Team Noridian develops all deliverables usingits documented deliverable creation and review standards and procedures and will deliver them inaccordance with our detailed project work plan.8.3.2.3.4 Performance StandardsRFP Section 6.3.2.3.3.1, Requirements a through cThe following performance standards will be used to measure Team Noridian's success with thefollowing deliverables:• Testing schedules will be updated and maintained in the Project Work Plan as a part of our timemanagement processes.• All test plans will follow the Institute of Electrical and Electronics Engineers (IEEE) Standard forSoftware Test Documentation Standard 829-1998• All project management plans will follow the Institute of Electrical and Electronics Engineers (IEEE)Standard for Software Project Management Plans 1058-19988 | 157
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:
Page 125 and 126:
Page 127 and 128:
Page 129 and 130:
Page 131 and 132:
Page 133 and 134:
Page 135 and 136:
Page 137 and 138:
Page 139 and 140:
Page 141 and 142:
Page 143 and 144:
Page 145 and 146:
Page 147 and 148:
Page 149 and 150:
Page 151 and 152:
Page 153 and 154:
Page 155 and 156:
Page 157 and 158:
Page 159 and 160:
Page 161 and 162:
Page 163 and 164:
Page 165 and 166: RFP MED-12-001 | Technical Proposal
Page 215: RFP MED-12-001 | Technical Proposal
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

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

Delete template?

Save as template?