Part 4 - Iowa Medicaid Enterprise

RFP MED-12-001 | Technical ProposalIowa Medicaid Enterprise System Service Procurement | MMIS and Core MMIS OperationsWe understand that the reports for the state fiscal year ending in June must be provided by October 15 ofeach contract year, and have built those tasks into our operational project work plan. The Department willpublish the annual measurements by the following February 15.7.5 General DocumentationRFP Section 5.5Team Noridian will provide visibility into the new MMIS functions through thorough documentationand reports that we will provide to the Department and maintain throughout the entire contract period.Our concept for document management is based on delivering high-quality documents to theDepartment that meet all its standards and acceptance criteria as initially defined in the DXD for eachtype of documentation, and then updating all documentation in a timely fashion using theDepartment's defined standards.Team Noridian uses industry best practices, standards, and tools to streamline document development,delivery, maintenance, and updates, as well as to streamline document acceptance by the Department. Inorder to maintain the cohesive, customer friendly environment that we have created with the Department,we will continue to provide all Core MMIS operational reports as well as up-to-date and accurate systemand user documentation and operational procedures on the processes we maintain. Team Noridian has afull set of proven documentation, standards, and templates from previous MMIS projects that we hope toleverage, with Department approval, and tailor for the new MMIS in accordance with the Department’sstandards. This baseline set will significantly reduce documentation development time during the start-upand implementation period, and will aide in the maintenance and updating of processes anddocumentation throughout operations.7.5.1 Documentation Creation and MaintenanceRFP Section 5.5, Requirements a and eTeam Noridian understands the need to developand maintain proper and full documentation toenable users—whether they are from theDepartment, external sources, the IMEprofessional contractors, or the Team Noridiantechnical and operations staff—to effectively use, maintain, and operate the system. This includes internaldocumentation as well as web-published materials that assist the providers with using the Web Portal. Forthose reasons we use a repeatable documentation process which emphasizes obtaining advance approvalof the format, content, and acceptance criteria for each type of documentation. This gives both TeamNoridian and the Department a clear and timely understanding of expectations for the documents,encourages involvement of the Department throughout the documentation development process, andensures that all documents are developed and updated in the state-prescribed formats. We adapt thisprocess to meet the needs of each of our projects, but the element of customer participation throughout theprocess is fundamental for all projects. Team Noridian's system and user documentation developmentprocesses are fully described in Section 8.4.2 Post Implementation Activities the subsections below focuson the specific requirements of RFP Section 5.5.The prime contractor, Noridian, has developed processes using OnBase, the current change managementrequest (CMR) system, to control documentation changes. As shown in Figure 7-5, all change requestsare sent to a queue where they are reviewed to determine if documentation updates are needed. Changerequest workflows track each change to ensure that the appropriate documentation is developed orupdated for the change. Keywords provide the ability to link and track all of the components that mayneed updates because of a change.7 | 31