13.07.2015 Views

Part 4 - Iowa Medicaid Enterprise

Part 4 - Iowa Medicaid Enterprise

Part 4 - Iowa Medicaid Enterprise

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

RFP MED-12-001 | Technical Proposal<strong>Iowa</strong> <strong>Medicaid</strong> <strong>Enterprise</strong> System Service Procurement | MMIS and Core MMIS OperationsFor this new Core MMIS operations contract,Team Noridian will enhance its documentationmaintenance processes and the use of the CMRworkflows to improve control over the updates,reviews, and acceptance of documentationupdates. Team Noridian will implement the useof reusable objects developed as part of otherMMIS implementations and use those inconjunction with the CMR workflows. Theseobjects are maintained in a content database orcontent vault that contains the objects and acatalog of where the objects are used in thedocumentation. This approach allows us todevelop an object, make it available for use inthe entire project, or use objects from otherprojects as applicable, and when the objectchanges, whether in response to a CMR orcorrection of a defect, to expeditiously makechanges to documentation impacted by thechange. This use of the content vault to quicklyidentify which documents or deliverables need tochange because of a change to a system orcorrection 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. Updates to system documentation, user documentation, and artifacts suchas system design documentation and data dictionaries are controlled using these processes. All updateswill be made within 10 business days of the implementation of a change.7.5.2 Corrective Action PlansFigure 7-5. Documentation Review. The CMRworkflow contains a documentation review queuewhich is used to check if updates todocumentation are needed as a result of a CMR.RFP Section 5.5, Requirements b and cAs discussed previously in Section 7.3 Contract Management, Team Noridian will develop andimplement a CAP to address any deficiencies, problems, or performance improvement opportunitiesfound through any means including regular workload monitoring, internal QA reviews, performancemeasurement reports, or Department reviews and audits. We will develop the CAP, along with anestimated schedule, and deliver it to the Department for review and approval within 10 business days ofdiscovery of a problem. Once reviewed and approved, the CAP is updated and fully documented alongwith all supporting information. The CAP is tracked through to completion, and if system updates arenecessary they will be designed, developed, tested, and implemented using the procedures and processesof our ISDM through our normal change management routine. We track progress and report on the CAPthrough regular status reporting, schedule updates (if applicable), and take corrective action if theestimated completion date appears to be in jeopardy. Once the CAP is complete, we providedocumentation, such as test results or a change in an operations manual, to the Department to ensure itmeets requirements.All records, including information on any CAP, are maintained in accordance with the Team NoridianRecords Control and Retention procedure and policy. The foundation of this procedure is the RecordRetention Policy, which outlines and prescribes the contract requirements for record retention where theyexist. Where no contract requirements exist, Team Noridian has adopted policies that comply with relevantlegal requirements and managerial considerations. Records may include, but are not limited to, employee7 | 32

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!