Frequently Asked Questions

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

Yes. The certification checklist defines a set of business and technical requirements that a particular Medicaid function must meet. The checklists and criteria are agnostic as to whether the requirements are met by a system built within the Medicaid Agency, a Software-as-a-Service model, a cloud-hosted model, or an ASO model.

FAQ ID:94461

Yes, our milestone review process is fully aligned with MITA. During each milestone review, CMS will verify that the state has considered MITA maturity during system definition, and whether the state is actively moving toward higher MITA maturity as defined in the state's latest MITA State Self-Assessment. Please see 42 CFR 433.112 (b)(11).

FAQ ID:94476

CMS is looking for new innovators in the Medicaid IT space. Please direct inquiries to: mmis_mes_certification@cms.hhs.gov.

FAQ ID:94416

Please work with your state representatives, so that they can contact CMS regional offices for quick assistance with your questions. In addition, please review other FAQs related to this topic.

FAQ ID:94431

Milestone reviews have proven to reduce risk by having earlier discussions where CMS can identify opportunities for efficiencies, facilitate collaboration with other states, and share other ideas that can save time, money, and effort. Identifying issues and opportunities earlier in the process will allow for a much greater impact than was experienced under the old process.

FAQ ID:93976

CMS encourages the use of COTS solutions where possible, and the milestone review process supports certification of COTS products. The review criteria are intended to be tailorable to support different solutions, including COTS. In this case, the technical criteria in the checklists that do not apply to COTS may be marked ""Not Applicable"" with an explanation as to why they do not apply.

FAQ ID:93986

It depends. We consider various factors. If a state is developing a complete MMIS solution with one release date, then there will be three reviews: Project Initiation Review, Operational Milestone Review, and MMIS Certification Final Review. If a state has multiple release dates with a modular or agile approach, the state would have one set of three certification reviews with CMS for each module the state would like CMS to certify. Each state will start its certification effort by having an initial consultation with CMS to determine how CMS can schedule milestone reviews that fit with the state's plan.

FAQ ID:94011

CMS has developed a milestone review process that is flexible enough to be placed over several development methodologies. CMS wants to ensure that the milestone reviews benefit and do not burden the state. CMS works with each state individually to ensure that the timing of the milestones fit within the state's internal development timeline.

FAQ ID:94001

Within the parameters set by State Medicaid Director (SMD) Letter #11-004 and SMD Letter #10-016, states may request 90/10 HITECH administrative funding for a wide range of HIE activities that support meaningful use.

States may request this funding for two broad categories of their administrative activities related to HIEs: (1) on-boarding, and (2) design, development, and implementation (DDI) of infrastructure. In this context, on-boarding refers to the state's or HIE's activities related to connecting a provider to an HIE so that the provider is able to successfully exchange data and use the HIE's services; this funding cannot cover costs incurred by the provider or the vendor. For more information, please see the later FAQ that specifically discusses on-boarding. With respect to infrastructure DDI, CMS is able to provide matching funds for a variety of state activities that will enable providers who are eligible for the Medicaid EHR Incentive Program to meet meaningful use. If the requirements of SMD Letters #10-016 and #11-004 are met, CMS will provide funding for state administrative activities related to core HIE services (for example, designing and developing a provider directory, privacy and security applications, and/or data warehouses), public health infrastructure, and electronic Clinical Quality Measurement (eCQM) infrastructure.

CMS recognizes that there are multiple types of HIE models emerging among the states, and will review each proposal individually. SMD Letter #11-004 outlines some of the characteristics that CMS encourages, but a state may provide justification for why an alternate model is more appropriate given the unique circumstances in that state. CMS encourages interested states to reach out to their CMS regional HITECH contacts to discuss any proposed HIE funding requests prior to submitting an Implementation Advance Planning Document Update (IAPD-U) for HIE funding. Please note that cost allocation and fair share principles are critical requirements outlined in SMD Letter #11-004, and so the state must ensure that its funding request complies with the principles outlined in the SMD letter.

Supplemental Links:

• This FAQ was released as part of a larger set. View the full set. (PDF, 288.05 KB)

FAQ ID:92526