Part 4 - Iowa Medicaid Enterprise

More documents

Recommendations

Info

RFP MED-12-001 | Technical ProposalIowa Medicaid Enterprise System Service Procurement | MMIS and Core MMIS Operationsand marked up in real time during the sessions. The report layout specification will include calculationson each report, where applicable. In addition to the DSD, this information will be included in the usermanual to provide the information to help the user understand the report. Report field definitions andexplanation of calculations will be documented in the same sections of the DSD and user manuals notedabove. We will also include a copy of one page of each report and the number of pages for each report.The DSD and the user manual section for each business process area will include instructions forrequesting a report with samples of input documents or screens. Some of the canned reports will begenerated by the user through the Report Access Portal using prompt screens to define the reportparameters, such as "Begin Date" and "End Date". Other reports will be automatically generated on ascheduled basis. Team Noridian will define these reports and will provide the prompt screen in the DSDand user manual where inputs through screen prompts are required.Descriptions of online error messages for fields incurring edits will be presented with the correspondingresolution of the edit for each business process area. These are currently included in the followingsections of the user manual:• Section 2.3: Navigation, Screens, Functions, Tables, Error Messages for [specific sub-area]• Section 3: Screen Definitions for [business process area]Team Noridian’s user manuals show step-by-step activities for updating information using narrativeinstructions, screen illustrations, and dialog boxes. While describing the update process in a specificbusiness functional area, the user manuals will contain information on the edits associated with the updateprocess and how to correct them. System error messages handled by eCAMS are presented in commonlyused terminology and are configurable so that they can be tailored to the Department's needs and standards.All functions in the MMIS are logically grouped by business functional area. Data updates and codingvalue maintenance for each logical business process area are also consolidated by business process areaand presented separately within each business area. Team Noridian will organize the user documentationfor the new MMIS to follow the same business functional area approach as the system (e.g., member,provider, and operations). We will consolidate all functions and supporting material by businessfunctional area and produce our user documentation accordingly. This organization will be included in thefollowing user manual sections:• Section 2.2: Navigation and Flow Charts for [specific business process areas]• Section 2.3: Navigation, Screens, Functions (including file level maintenance), Tables, ErrorMessages for [specific sub-area]We will coordinate the planning, development, and organization of the user documentation withthe Department, so that the documentation will meet both the set of requirements and theDepartment’s expectations.The user manuals will include code values and data element numbers when describing screens forreference to the DED. This information will be included in the following section of the user manuals foreach business process area:• Section 3: Screen Definitions for [business process area]The DED is provided in both hard format as a part of the system documentation, and in electronic/onlineformat via the MMIS functionality. The same code values displayed and data element number provided inthe DED will map directly to the code values and data element numbers in the user manuals. Instructionsfor entering online updates for each business process area are included in the previously describedSections 2.2 and 2.3 of the user manual.Team Noridian’s user manuals show step-by-step activities for updating information using narrativeinstructions, screen illustrations, and dialog boxes and clearly depict which data and files are being8 | 210
RFP MED-12-001 | Technical ProposalIowa Medicaid Enterprise System Service Procurement | MMIS and Core MMIS Operationschanged. Each screen and dialog box in the MMIS is uniquely named for easy identification. Forexample, the provider list page is called “pgProviderList” and the provider address update dialog box iscalled “dlgProviderAddressDetails.” These same names that appear at the bottom of the associated screenwhen viewing the screen in MMIS will be referenced with the screenshot in the user manual.8.4.2.2.4 Desktop GuideRFP Section 6.4.2.2, Requirement vTeam Noridian will develop guides as a subset of the user documentation to be available to users at theirdesktop. The existing MMIS procedures provide a guide for the ongoing management and operation ofthe MMIS and team Noridian currently produces and maintains them as part of our core contractorresponsibilities in Iowa. Team Noridian will update these procedures to allow users to take maximumadvantage of functionality in the new MMIS. The user manual documents provide the system usersinstructions needed to use the MMIS.Team Noridian will deliver an operational procedure for each business process area impacted by the newMMIS with multiple volumes focused on each of the sub-areas and user type. These procedures willaddress how the business area can obtain maximum benefit from the new system. Team Noridianrecognizes that for some business area, other contractors maintain their own procedures. For those areas,Team Noridian recognizes that the other contractor will most likely use the new MMIS userdocumentation to update business procedures. Each operating procedure describes the business functionsand sub-functions (if applicable) of the business process area, and the business processes within eachfunction or sub-function. It also identifies the tasks within each business process and lists associatedmaterials, such as user manuals and training class narratives.As with any new MMIS, there will be changes in the way things are performed. Team Noridian willdemonstrate the normal day-to-day activities for new MMIS processing to the Department and IMEcontractor staff. Team Noridian, working together with the Department and other IME contractors,will provide the needed documentation to create operational procedures to take full advantage of theMMIS potential.8.4.2.3 State ResponsibilitiesRFP Section 6.4.2.3, Requirements a through cTeam Noridian acknowledges that the system documentation requirements extend past implementationand continue through the life of the project until the system is eventually retired. The complexity of anMMIS implementation necessitates a strong partnership between the Department and Team Noridian forthe implementation to be successful. Team Noridian will work closely with the Department'simplementation team to transition the new MMIS and all documents listed as deliverables in the RFP thatare needed to support new MMIS operations from implementation to operations. During the transition,Team Noridian anticipates that the Department would review and accept any changes made to systemdocumentation since the start of UAT. This acceptance of these changes or the originally accepteddocumentation if there are no changes to a specific document during UAT will establish thedocumentation baseline for operations.During operations, Team Noridian will review deficiencies identified by the Department's implementationteam. When required by the Department, a corrective action plan (CAP) will be submitted by TeamNoridian for Department approval. As documentation updates are made during operations, and newdeliveries occur, the Department will review the delivery for compliance with the DXD. The standardDepartment review time for these reviews is 10 days.8 | 211
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:
Page 209 and 210:
Page 211 and 212:
Page 213 and 214:
Page 215 and 216:
Page 217 and 218:
Page 219 and 220: RFP MED-12-001 | Technical Proposal
Page 269: RFP MED-12-001 | Technical Proposal
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?