MITA Update - How To Voluntarily Pre-Certify MMIS Modules

Tuesday, October 4, 2016

Here’s an excerpt from the recently released CMS RFI on Pre-certification of MMIS Modules:

“Voluntary precertification of Vendor Modules.  During its recent rule-making, CMS received several comments regarding plans for pre-certification of MMIS modules. CMS is now seeking suggestions for how to structure the pre-certification process. Pre-certification would streamline certification of those modules once they are integrated into an MMIS. Per regulations, certification for MMIS occurs per state and applies to a specific operational instance of an MMIS. The end-to-end MMIS certification process would still include the evaluation of pre-certified modules with respect to how they perform once integrated into the MMIS in production. However, the use of pre-certification may expedite overall MMIS certification because pre-certified modules would have already been evaluated against a relevant subset of certification criteria. The voluntary precertification of modules may also accelerate the adoption of vendor products by state Medicaid agencies.

The first step in this pre-certification process is a comprehensive Vendor Self-Assessment (VS-A). This assessment mimics the State Self-Assessment (SS-A) and is designed to allow vendors to compare their offerings to the new MITA/MECT/MECL requirements and develop a comprehensive cross-walk between MITA 3.0 and the solution being offered.

Here are the steps to complete a Vendor Self-Assessment (VS-A):

1. Assemble the VSA Team, this includes Technical, Information and Business SMEs. The VSA start-up requires senior management VSA direction.
2. Identify and select the appropriate Business Areas and associated MECT requirements. Define Goals and Objectives.
3. Collect documentation and artifacts necessary to assess MITA maturity. Review recent solution or module CMS Certification projects and documentation.
4. Assess architectures and describe your As-Is status. Identify components.
5. Assess and document the capability matrices. Review and document the applicable MECT requirements and attached artifact substantiation.
6. Identify and document solution GAPS. GAPS, or MITA requirements that the solution does not meet, should be documented and placed on the roadmap as “future enhancements” (version control for COTS products).
7. Complete the solution or module roadmap for improving MITA maturity.
8. Maintain and update the V-SA with solution or module improvement and/or enhancements.

While this may look like a monumental task, it’s really quite easy. That’s assuming you have a MITA Tracking Tool that prompts you through the questions, provides searchable CMS MITA regulations, produces your scorecards, and creates a development path using the roadmap feature. If not, you can expect to spend millions on a MITA consulting firm to get your documentation squared away. At EHR, we have a solution.

ReadyCert is the only MITA Tracking Tool in use by both State Medicaid Agencies and solution vendors who currently participate in the Medicaid Solution market. States use ReadyCert to produce the SS-A, maintain the SS-A, produce APD and RFP material, score vendor proposals, track solution deployment (PMO), perform IV/V activities by MECL requirement, and gain certification. Vendors use ReadyCert to document their solution, compare the solution against MITA, determine GAPS, track deployment of new features, write proposals, and everything MITA

Written by:
Wayne Cooper

Leave a comment

Comments are shared with EHR only. They are not posted publicly.

Thank you! Your submission has been received!

Oops! Something went wrong while submitting the form