Part 4 - Iowa Medicaid Enterprise

RFP MED-12-001 | Technical ProposalIowa Medicaid Enterprise System Service Procurement | MMIS and Core MMIS OperationsDocument CharacteristicEasy to UseAccuracyCompletenessTask OrientationEasy to UnderstandClarityConcretenessStyleEasy to FindOrganizationEase in SearchingVisual EffectivenessDescriptionFree of mistakes or errors; adherence to factsThe inclusion of all necessary parts – and only those partsA focus on helping users complete the tasks associated with a product in relation to their jobsFreedom from ambiguity or obscurityFreedom from abstraction; the inclusion of appropriate examples, scenarios, similes, and analogiesCorrectness and appropriateness of writing conventions and choices in words and phrasesA coherent arrangement of parts that make sense to the userPresentation of information in a way that enables users to find specific items quickly and easilyAttractiveness and enhanced meaning of information through use of layout, illustrations, color, type, icons, andother graphic devicesFigure 8-112. Document Characteristics. All Team Noridian documents will be evaluated against thesecharacteristics.Team Noridian routinely produces a table of contents and indices for all documentation, including hardcopy user manuals and online help. When delivering documents electronically as HyperText MarkupLanguage (HTML) files, the table of contents contains hyperlinks that allow the user to go directly to atopic in the table of contents by selecting the specific table of contents item. We will configure PortableDocument Format (PDF) and Microsoft Word files to allow the users to select specific topics in the tableof contents. Indices are provided for all hard copy document deliverables; however, Team Noridian uses asearch or find option for electronic and online documents.The content for new MMIS user information is procedure-driven and step-by-step “how-to” proceduresexplain how to use the system to support specific business processes to allow the Department to obtainmaximum benefit of new MMIS functionality. As Team Noridian is not responsible for businesstransformation associated with the new MMIS we will work with the Department and services contractorsto align our user documentation to business processes implemented through business transformationactivities by the Department and other vendors.Team Noridian has developed processes using OnBase, the change management request system, tocontrol documentation changes. All change requests are sent to a queue where they are reviewed to see ifdocumentation updates are needed. Change request workflows are used to track each change and toensure that the appropriate documentation is developed or updated for the change. Keywords provide theability to link and track all of the components that may need updates as a result of a change. Asmentioned previously we will have a content vault which will link the reusable objects to the deliverablesthat contain them. Using the content vault to identify which deliverables need to change when a reusableobject is updated because of a change to the system or correction of a defect will greatly expedite theprocess of documentation updates, while at the same time maintaining consistency of content across thedocuments that use the object. During the operations phase, Team Noridian will automatically notify theunits that are affected by the change through updates to the project portal and notify the provide thedocumentation to units that are affected by the change and in many cases will meet face to face with theunits to verbally discuss the changes that were made.During the start-up and implementation phase, draft and final user documentation will be used for UATand for knowledge transfer prior to the start of operations. Discrepancies or errors found as a result of thetesting or training will be corrected prior to the final implementation date.8 | 207