Part 4 - Iowa Medicaid Enterprise

RFP MED-12-001 | Technical ProposalIowa Medicaid Enterprise System Service Procurement | MMIS and Core MMIS Operations• The nomenclature used in the overview must correspond to nomenclature used in moduledocumentation. All modules must be referenced and documentation must be consistent from theoverview to the specific modules and between modules.• Includes module level documentation for each module which contain:• Module name and numeric identification• Module narrative• Module flow, identifying each program, input, output and file• Process flows within each module, identifying programs, inputs and outputs, control, processflow, operating procedures and error and recovery procedures• Name and description of input documents, example of documents and description of fields or dataelements on the document• Listing of the edits and audits applied to each input item and the corresponding error messages• Narrative and process specifications for each program or module• Screen layouts, report layouts and other output definitions, including examples andcontent definitions• A list and description of all control reports• File descriptions and record layouts with reference to data element numbers for all files, includingintermediate and work files• A list of all files by identifying name, showing input and output with cross-reference to programidentifications• Facsimiles or reproductions of all reports generated by the modules• Instructions for requesting reports must be presented with samples of input documentsand/or screens• Narrative descriptions of each of the reports and an explanation of their use must be presented• Definition of all fields in reports, including a detailed explanation of all report item calculations• Documentation of all rules in the rules engine. The rules engine solution must meet the same federalstandards established by CMS related to Medicaid eligibility rules engine to ensure federal enhancedmatched rates. This includes both a technical definition of the rule and a business definition of therule. Additionally, our preference is for a rules engine where it links to policy, state law, and federallaw can be established and maintained within the rules engine solution. Each rule has a definition anda documentation tab. Both these can be printed and/or made available through an online viewer. Thedocumentation tab allows links to policy documents and for attaching rules (e.g., policy guidelines,notifications, etc.)• Desk level procedures. Please see Section 8.4.2.2 below for additional information on desklevel procedures.• List of post office boxes, telephone numbers, facsimile numbers, and any other Department-approvedmethod of accessing the contractor(s) to receive information, including but not limited to, MMISforms, data, and inquires; and a description of the purpose of each method listed above.• Team Noridian will maintain a master list of all MMIS manuals on the Project Portal with a hyperlinkto the actual manual.• Program documentation, to include, at a minimum:• Program narratives, including process specifications for each, the purpose of each and therelationships between the programs and modules• A list of input and output files and reports, including retention• File layouts• File names and dispositions• Specifics of all updates and manipulations• Program source listing8 | 200