Part 4 - Iowa Medicaid Enterprise

More documents

Recommendations

Info

RFP MED-12-001 | Technical ProposalIowa Medicaid Enterprise System Service Procurement | MMIS and Core MMIS OperationsThroughout the software development phase of the project, the Department is provided access to software sothat the Department can remain cognizant of the development of the actual software. In addition, thesoftware will be available to the Department during Joint Application Design (JAD) sessions for bothrequirements and detailed system design to ensure that requirements and designs are properly captured.Throughout the project life cycle, deliverables which were previously approved may require updates orrevisions in subsequent phases of the project (e.g., the DSDs are initially approved during the design,revised during the development and test, and may be updated during the UAT and operations phase).Revisions or updates to approved documents will follow a process similar to that shown in Figure 8-108.The DXD will be updated if needed to reflect content to be changed or if a DXD update is not needed, asin the case of an as-built design change, the deliverable process will begin at "Develop or UpdateDeliverable" step of the deliverable process.A key tenet of our documentation methodology is to establish and leverage standardized documentationfrom our other highly successful MMIS projects so that we can update it to reflect the new MMIS andreuse it, with Department approval. In Section 8.4.2.1, we provide more detail on this approach and theprocess we propose following to allow the Department to determine if the reuse of existingdocumentation, updated for the new MMIS, will meet Department business needs.We will bring the content, document templates, standards, and experience from our other MMISimplementations to the new MMIS project and tailor the documentation to meet the requirementsof the RFP and the MMIS Core contractor operations. This tailoring will begin in the analysis anddesign activities of the implementation phase where, in collaboration with the Department, its subjectmatter experts, and as requested by the Department, other IME services contractors, Team Noridianwill outline the objectives of each piece of documentation on the project so that as Team Noridiandevelops the documentation over the ISDM we are using consistent materials for associateddocumentation (e.g., screen shots from design documents are the same ones used for trainingmaterials related to the same topic).Team Noridian understands its responsibility for providing and maintaining accurate, complete, andtimely deliverables which provide the information needed by the Department and Team Noridian toconduct and manage both new MMIS start-up and implementation and operations. Our combinedexperience on other MMIS and health care projects working with the customer to identify the rightinformation for the right document and then working collaboratively with the customer to ensure thatinformation is delivered will be of direct benefit to the Department in the implementation and operation ofthe new MMIS.8.4.2.1 System DocumentationRFP Section 6.4.2.1As mentioned previously, Team Noridian's approach to system documentation is embedded in itsiVison360 methodology. While system documentation is considered a single deliverable by both theDepartment and Team Noridian, the reality is that post implementation system documentation iscomprised of the deliverables which will have already been developed and accepted during theimplementation phase (e.g., design documents, user manuals, business processes, knowledge transfermaterials), used during testing and then updated with modifications that are identified during UserAcceptance Testing and operations.A key piece of our documentation solution is the use of reusable objects developed as part of other MMISimplementations. These objects are maintained in a content database or content vault which contains theobjects and a catalog of where the objects are used in the documentation. This approach allows us todevelop an object, make it available for use in the entire project, or use objects from other projects asapplicable, and when the object changes, whether in response to a change management request (CMR) orcorrection of a defect, to expeditiously make changes to documentation impacted by the change.8 | 198
RFP MED-12-001 | Technical ProposalIowa Medicaid Enterprise System Service Procurement | MMIS and Core MMIS OperationsTeam Noridian acknowledges that the Department had included many types of methodologies in the RFP.The list is comprehensive and is aligned to ensuring that individuals using system documentation canunderstand the overall standards, network bandwidth needs, hardware capacity, software needs, andnetwork topology to transfer, operate, and maintain the current MMIS. Team Noridian's systemdocumentation fully supports this objective.8.4.2.1.1 COTS Systems DocumentationRFP Section 6.4.2.1For commercial off the shelf (COTS) products incorporated in the new MMIS, Team Noridian willprovide the following as they are available from the vendor.• Product Roadmap• Product Business Rules and Controls• Product Graphical User Interface (GUI), Features and Functions• Product Hardware (Optimal Performance) Specifications• Product Software Components/ Third-party Components• Product Training Curricula/Services• Product Technical Services• Product Support Services• Product Definition of Terms/Glossary• Product Desktop/Browser Specifications• Product Operating System Specifications• Product Crosswalk to Documentation Base8.4.2.1.2 Systems Documentation General RequirementsSection 6.4.2.1, Requirements a through iThe system documentation, beyond the COTS information listed above, are all deliverables from theimplementation phase. For this reason it is critical that the deliverable flow depicted in Figure 8-107 befollowed and it is important that the Department and Team Noridian put special emphasis on the DXD toidentify both the content and methodology to be used to present that content.Through the use of a stringent document release configuration management process that involves theTeam Noridian quality assurance monitoring and control unit, the new MMIS account manager, and theDepartment, Team Noridian will ensure that system documentation provided by Team Noridian meets thefollowing requirements of the RFP:• Is current and based on the latest version document approved by the Department• Is available and updated on electronic media storage and must be maintainable after turnover• Has all narrative created and maintained in Microsoft Word (compatible with Department version)and be provided to the Department on request on CD-ROM or other designated media• Has all narrative also maintained in .html or .htm format for online use• Is organized in a format which facilitates updating and any revisions must be clearly identified• Includes system, program and application narratives that are understandable by non-technical personnel• Contains an overview of the system including:• A narrative of the entire system• A description and flowcharts showing the flow of major processes in the system• Multiple sets of hierarchical, multi-level charts that give a high, medium and detail view of thesystems for both online and batch processes• A description of the operating environment8 | 199
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:
Page 167 and 168:
Page 169 and 170:
Page 171 and 172:
Page 173 and 174:
Page 175 and 176:
Page 177 and 178:
Page 179 and 180:
Page 181 and 182:
Page 183 and 184:
Page 185 and 186:
Page 187 and 188:
Page 189 and 190:
Page 191 and 192:
Page 193 and 194:
Page 195 and 196:
Page 197 and 198:
Page 199 and 200:
Page 201 and 202:
Page 203 and 204:
Page 205 and 206:
Page 207 and 208: RFP MED-12-001 | Technical Proposal
Page 257: RFP MED-12-001 | Technical Proposal
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?