Part 4 - Iowa Medicaid Enterprise

RFP MED-12-001 | Technical ProposalIowa Medicaid Enterprise System Service Procurement | MMIS and Core MMIS OperationsThe requirements traceability matrix will be updated within a short period after each JAD session. The biweeklysessions keeps the focus on design and helps the management to identify potential delays incompleting design in a timely fashion and allows for contingency plans and risk mitigation plans to meetagreed upon schedules with a high quality product.Must meet measurement accuracy of 99 PercentTeam Noridian’s Quality Monitoring and Control unit will measure defects against analysis and designdeliverables and produce reports for PMO reporting. Our team will achieve 99 percent accuracy of thesedeliverables. Accuracy will be measured using checklists similar to the one provided in Figure 8-62.Team Noridian’s RVD Attribute ChecklistAttributeDefinitionFeatures: The total set of product features and quality characteristics that meet the Department’s needs under the environment forFitness for Usewhich the product is to be used.Freedom from defects: The degree to which the product is free from deficiencies that prevent the product from operating as specified.Individual requirement: Each requirement is an accurate and precise description of a feature or process of the product. For eachoutput, the range of acceptable input values will be defined.CorrectRequirements Validation Document: For an RVD to be correct it should accurately and precisely identify the individual conditions andlimitations of situations that the desired capability will encounter and it must also define the capability's proper response to thosesituations.Individual requirement: Every requirement has only one interpretation. As a minimum, this requires that each characteristic of thefinal product be described using a single unique term.Requirements Validation Document: The RVD should be unambiguous both to those who create it and to those who use it. However,Unambiguous (clear)these groups often do not have the same background and therefore do not tend to describe requirements the same way.Representations that improve the requirements specification for the developer may be counterproductive in that they diminishunderstanding to the user and vice versa.Individual requirement: The stated requirement is complete and does not need further amplification.Requirements Validation Document: An RVD is complete if, and only if, it includes the following elements:CompleteAll significant requirements, whether relating to functionality, performance, design constraints, attributes, or external interfaces. Inparticular any external requirements imposed should be acknowledged and treated.Full labels and references to all figures, tables, and diagrams in the RVD and definition of all terms and units of measure.Figure 8-62. Example Partial Checklist for Requirements Validation Document. Team Noridian’s qualitymanagement processes provides for the measurement and analysis of metrics such as deliverable accuracy.8.3.2 Development ActivitiesRFP Section 6.3.2Team Noridian has proven experience running data conversions for multiple state MMIS projects. Wehave developed techniques for discovering sources of legacy data, mapping the legacy data to the newMMIS, and handling data gaps and quality issues. Team Noridian combines functional knowledgewith technical expertise to achieve the most complete and accurate MMIS data conversion.We understand that conversion is a highly iterative process. We have built processes and tools tomanage the process of analyzing and cleaning legacy data. We also realize that the Department mayhave significant knowledge of legacy data – both documented and undocumented. Team Noridian willalso leverage current experience gained from working with the IME.Team Noridian understands that data conversion is a critical activity and an integral part of the systemimplementation process. While it is a separate and important task, Team Noridian integrates data conversionactivities with other tasks in the Team Noridian iVision360 approach. The data conversion team will workclosely with the business process area teams, and will attend requirements validation and collaborativedesign sessions to ensure a common understanding and thoroughly capture the data conversionrequirements. All data conversion activities will be conducted in parallel with the new MMIS businessprocess area teams. The data conversion effort will run in parallel with design, development, and testing.Details of how Team Noridian ensures interdependencies between the efforts are addressed further in ourapproach and in the draft Detailed Project Work Plan.8 | 104