Frequently Asked Questions

All the criteria in the checklists (MITA, MMIS or Custom) are the same. The difference between checklists is the criteria organization within the checklists. If the services solution is innovative, unique, or an unconventional approach, then the custom checklist approach might be appropriate. The RO will work with the state and vendors to decide which checklist set is best suited for the state's certification. Both service and traditional-type solutions need to meet all certification criteria to ensure compliance with federal regulations.

FAQ ID:94901

Yes, CMS will support the costs for this kind of MMIS transition. We encourage states to ensure that both the current vendor's and new solutions provider's contracts account for this transition period and address a prorating of cost during this time. States should minimize the costs of transition by performing due diligence on the anticipated spending. The legacy system provider should be compensated for its role in ensuring a smooth transition, with a ramp-down of other operational costs. The new solutions provider should have deliverables in its contract that speak to the soft launch or phased launch approach, with an uptick in operational costs as the transition progresses.

FAQ ID:94906

State Medicaid agencies are required to have MMIS System Security Plan and Privacy Impact Assessment documents. State Medicaid agencies must perform regular routine security and privacy risk assessments to ensure the protection and safeguard of beneficiary data that is consistent with Health Insurance Portability and Accountability Act (HIPAA) privacy and security rules. Please refer to the MECT for more details: https://www.medicaid.gov/medicaid/data-and-systems/mect/index.html

FAQ ID:94911

Yes. While CMS envisions a discrete role for the System Integrator (SI) in each state, with specific focus on ensuring the integrity and interoperability of the Medicaid IT architecture and coherence of the various modules incorporated into the Medicaid system complex, it is permissible for an SI to provide modules as part of the overall solution. The target outcome for the SI in support of the state should be to foster best-in-breed solutions for Medicaid business requirements, with the SI responsible for the successful integration of the chosen solutions and infrastructure into a seamless functional system. The SI must ensure that all modules have open APIs and remain loosely coupled. More information on the SI role can be found in Section 1.7 of the Medicaid Enterprise Certification Life Cycle, part 01 of the MECT. States are encouraged to use an acquisition approach that limits the potential for conflict of interest an SI may have in choosing the modular solutions to be incorporated into the system. As described above, the goal is to avoid lock-in to a single vendor or an otherwise closed set of solutions.

FAQ ID:94916

CMS encourages the use of an SI outside the state agency, but states can consider themselves in that role if they can support that effort and if that decision is made with consultation and agreement from CMS. For more information about the role of the SI, see Section 1.7 in part 01 of MECT Medicaid Enterprise Certification Life Cycle. https://www.medicaid.gov/medicaid/data-and-systems/mect/index.html

FAQ ID:94921

FAQ ID:92871

The Review Tool Report is a feature CPOCs, SRTs, Senior Reviewers, Package Approvers, Package Disapprovers, and CMS Report Admins can utilize to see Package Reviewable Units, Reviewers, Reviewable Unit Assessment Values, and Notes.

Log in as CMS Point of Contact or Submission Review Team member. Under the "Records" tab, select "Submission Packages". Then select the link to the submission package. In the left panel, select "Review Tool Report". You may sort the reviews of all Review Team members by Package Reviewable Unit, Reviewer, Reviewable Unit Assessment Value, or Note/Assessments by utilizing the drop-down boxes. You also have the ability to export this report to Excel by selecting "Export to Excel."

FAQ ID:92876

Analyst Notes are a form of brief internal communication for the CMS Review Team. These notes are a part of the official record; however, State users are not able to see these notes. Analyst Notes are part of the Review Tool for each Reviewable Unit and the SRT or CPOC may view the notes from other Review Team members (depending on the type of note) within the Review Tool, and add his/her own notes.

The CMS Point of Contact or Submission Review Team members may add Analysts Notes through the Review Tool. The types of notes available are referenced in a table below. You will start by logging in as the CMS Point of Contact or Submission Review Team member, then going to the "Records" tab. Under the "Records" tab select "Submission Packages" and then select the link to the package. In the left panel select "Analyst Notes". You will then have the ability to search notes entered by Review Team Members.

FAQ ID:92881

If certain fields are misaligned you may need to adjust your compatibility settings. Click the Tools button in the upper right side of your screen, and then click Compatibility View settings. Next click the Add button. The website is added to your Compatibility View and the screen will realign. You can always remove the website by clicking on the website in the list and clicking the Remove button. If an issue persists, please email the MACPro Help Desk at MACPro_HelpDesk@cms.hhs.gov

FAQ ID:92886

A State may withdraw a submission package once it has been submitted to CMS. Withdrawing a submission package takes it out of contention and the submission package cannot be edited or resubmitted. Log in as State Point of Contact, and select the "Records" tab. Then select "Submission Packages" for your State. Next, select the link to the submission package you wish to withdraw. In the left panel, select "Related Actions". Next, select "Withdraw Submission Package". Then select the green button labeled "Withdraw Submission Package". A box will pop up, select "Yes". Once the submission package is withdrawn, you will be redirected to the Records screen. A yellow notification will appear briefly at the top of the page indicating "Action Completed Successfully".

FAQ ID:92891