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-87. Overview of Development and Testing. The development and unit test task diagram providesa “cue card” to quickly understand the key concepts.Rules Testing. During the iterative testing cycle, Team Noridian will perform Rules testing whichfocuses on the verification of the Rules or Edits Logic of all the different business process areas populatedin the eCAMS rules engine. Test cases will be created to test and validate the rules and edits logicpopulated either through table driven approach or rules engine driven approach.8 | 150
RFP MED-12-001 | Technical ProposalIowa Medicaid Enterprise System Service Procurement | MMIS and Core MMIS OperationsThe table driven approach is primarily used for Reference Rates and Limits. For example, Rates havedates associated with them defining the period of time that the rate is effective. Each rate may be tied toone or more service codes. Making these tables viewable and editable to authorized users, as well asthrough interfaces and uploads, provides considerable flexibility to the system and allows for makingchanges without a long development and testing process. It also simplifies testing as a verifying one ratefor one procedure code for an effective period, validates that all other procedure codes for the same timeframe and rate are also correct.Rules-driven approach is implemented using the rules engine. Rules are developed for each businessprocess area. These rules may be anything from simple validation edits to complex processing flows thatmust route decisions down different streams of code based on decisions points. For this testing, multipletests will be required to test each branch of the decision tree and the code associated with it.Rules testing can begin as early as unit testing and will continue through Integration testing. UserAcceptance testing and ORT will also, by definition continue to test rules through the claims adjudicationtesting.Module Testing. During the iterative testing cycle, unit testing has been performed where many of therequirements has been verified and tested in a limited fashion though user stories. Module testing expandson this testing by testing the business functionality within and across the entirety of the module expandingthe scope of test cases. This will include limited integration with other business areas through the use ofcommon data base tables and procedures. During Modules testing, interface testing will be limited totesting the ability to create outbound interface files, and process manufactured inbound interface files.The processes used to complete module testing are documented as part of the Modules Test plan,reviewed and approved by the Department prior to each module test phase. Prior to the start of Moduletesting, a test readiness review is completed to ensure that all the processes leading up to testing haveoccurred and that all necessary materials needed to complete testing have been developed by TeamNoridian and approved by the Department. Team Noridian will validate and track the requirements whichhave been successfully tested and passed and provide a final test results at the completion of each Moduletest for review and approval by the Department.Integration Testing. Following our central tenet of testing early and often, significant portions of thesystem will have completed testing through module testing. As progress is made through each layer of thetest program, the scope of testing becomes more focused on specific objectives. No longer focusing at themodule component level, which was completed as part of module testing, Integration testing willconcentrate on testing the system as a whole, End-2-End functionalities, crossing component boundariesthrough the exercise of business processes using a combination of created and converted business data.Integration testing will begin when module testing is completed in accordance with the agreed uponmodule test exit criteria for a business area. Many of the business areas and associated modules willcomplete testing in a staggered fashion. Integration test will encompass testing within an individualmodule (end-to-end within the module) and then expand to cover across modules and, finally, expand tothe breadth of the system including external interfaces. Team Noridian will establish an Integration testplan that logically groups business areas and associated modules so that integration testing can begin totest meaningful integration points while other functionality, such as Program Management, are stillcompleting module testing.Prior to conducting integration testing, the environment must be prepared by the new MMISinfrastructure team, which includes system and database administration staff, data conversion staff, andconfiguration management specialists. Having prepared the environment and prior to the start of testexecution development and test team members will perform an environment readiness review to ensurethe environment has been properly installed, configured, and populated with valid testing data.8 | 151
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: RFP MED-12-001 | Technical Proposal
Page 209: RFP MED-12-001 | Technical Proposal
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?