Part 4 - Iowa Medicaid Enterprise

RFP MED-12-001 | Technical ProposalIowa Medicaid Enterprise System Service Procurement | MMIS and Core MMIS Operationsvalidated requirement. Team Noridian will use the RFP requirements and existing documentation as theinput to requirements validation. As part of our proposal effort, we conducted a detailed analysis of theRFP requirements and provided a response to each requirement and the degree to which the proposedsolution meets those requirements. We will use this analysis as a starting point for RV. Team Noridianwill conduct planning activities to prepare for the JAD sessions, including:• Review existing system and IME documentation to understand the functional requirements of thesystem and the IME programs• Prepare the requirements database with pre-loaded RFP requirements and associatedproposal responses• Establish an installation of our proposed solution• Present the RV approach to Department staff• Coordinate with Department team counterparts to schedule system demonstrations and JAD sessionsTeam Noridian will conduct RV using teams that are aligned by business area similar to the MITA businessareas and sub-areas. Each business process area will complete a series of focused JAD sessions. TeamNoridian will produce the JAD session agendas for approval by the department prior to the JAD sessions.Team Noridian uses a process that integrates real-time use of the requirements database and the eCAMSsolution within the actual JAD sessions. Together, Team Noridian and the Department will review each RFPrequirement, review the proposal response to the requirement, and, if needed, enter the proposedmodification of the requirement directly in the requirements database during the session. The eCAMSsolution will be used to convey how the existing eCAMS solution functionality either meets or partiallymeets the requirements, where applicable. During the sessions, Team Noridian will document and report theaction items to the Project Portal. Our business analysts will also be prepared to ask questions regarding theIME programs, as-is processes, and to-be processes based on the documentation reviews conducted duringthe RV preparation activities. Our approach allows Team Noridian and the Department to reach a consensuson the meaning of each requirement during the sessions. After each requirement validation session, TeamNoridian will produce the session minutes for approval by the Department.Requirements validation is tightly coupled with the analysis activities for data conversion. In parallel withrequirements validation, the conversion team will be conducting data analysis on the source data files.Members from the business area teams will be asked, when required, to attend the conversion analysissessions, and specific conversion team members will be asked to attend the JAD session to ensure therequirements and business rules between the new MMIS and data conversion are in synchronization.As each JAD session is completed for each business area, the dedicated team for that business area willbegin the iterative development of the RSD for that specific business area. Separate RSDs will be developedand delivered for each business process area, each of which includes their validated requirements.Our requirements database application is not only used to capture the requirements and the outcome of theJAD sessions, but is also used to trace requirements to their associated work products in design,development, and testing. During RV, we will establish the Requirements Traceability Matrix (RTM) inthe requirements database. This will be used throughout DDI to trace requirements to their associatedwork products. The requirements database has the capability to generate numerous RTM reports based onthe needs of Team Noridian and the Department.As discussed earlier, Team Noridian's methodology and approach is based on having the proposed solutionand COTS applications available for demonstrations during requirements validation and detailed designsessions. We refer to the proposed solution during our requirements validation and design sessions to helpDepartment staff visualize how a requirement is currently implemented in the eCAMS solution. By doingso, we are able to more rapidly achieve agreement on how requirements will be realized in the new systemand identify if any gaps exist between the requirements and the eCAMS solution, or if any gaps existbetween our proposed response to a requirement and the Department’s intent for the requirement.8 | 55