Frequently Asked Questions are used to provide additional information and/or statutory guidance not found in State Medicaid Director Letters, State Health Official Letters, or CMCS Informational Bulletins. The different sets of FAQs as originally released can be accessed below.
Frequently Asked Questions
The regulation requires states to submit a pilot planning document to CMS by November 1 of the year in which each state’s PERM review year ends. The pilot planning document must describe how states will conduct their active and negative case reviews and must be approved by CMS before the MEQC pilots can begin. In addition, the regulation requires states to submit case-level reports and corrective action plans to CMS by August 1 of the year after the MEQC review period ends. The specifications for the MEQC pilot planning documents are provided in the MEQC sub-regulatory guidance effective August 29, 2018. More details on the specifications of the case-level reports and corrective action plans are included in a second round of guidance, MEQC sub-regulatory guidance effective October 22, 2018.
The PERM/MEQC dates/cycles are as follows:
| PERM Cycle* | PERM Review Period | MEQC Planning Document Due to CMS | MEQC Review Period | MEQC Case-Level Report on Findings and CAP Due to CMS |
|---|---|---|---|---|
| Cycle 1 | July 1, 2017 – June 30, 2018 | November 1, 2018 | January 1 – December 1, 2019 | August 1, 2020 |
| Cycle 2 | July 1, 2018 – June 30, 2019 | November 1, 2019 | January 1 – December 1, 2020 | August 1, 2021 |
| Cycle 3 | July 1, 2019 – June 30, 2020 | November 1, 2020 | January 1 – December 1, 2021 | August 1, 2022 |
*??
CMS = Centers for Medicare & Medicaid Services
CAP = ??
As reconfigured under the final regulation of July 5, 2017, MEQC will work in conjunction with the Payment Error Rate Measurement (PERM) program. In those years when states undergo their triennial PERM reviews, the states will not conduct MEQC pilots. The latter will only be required in the two off-years between PERM review years. CMS has restructured the MEQC program so that it more effectively complements the PERM program and provides states with the necessary flexibility and opportunity to target specific problems or high-interest areas during the two off-years of the PERM cycle.
In accordance with Medicare cost reporting, the state must use 12 months of cost data reported by each facility. With regard to payment data, the state should use actual amounts, to the extent available, then calculate a claims completion factor based on historic utilization. The state’s UPL submission must include an explanation of its methodology to estimate payments. The use of a claims completion factor provides a reasonable estimate of the amount that Medicare would pay for these services, consistent with the UPL as defined at 42 CFR 447.272.
Yes. Mapping data, through V-Look-ups, for example, is a much easier and consistent process for current and future UPL submissions. However, a state may choose to type information and data into unlocked fields in the UPL templates. When a state chooses to input data directly (not through a V-Look-up) into the template, it still must provide the supporting documentation with the source data. Additionally, the state should explain how it mapped data from the supporting documentation into the template. The Centers for Medicare & Medicaid Services utilizes the supporting information to confirm that the information in the templates is correct.
Effective state fiscal year 2020, each state must submit a complete data set of payments to Medicaid providers, including providers paid at cost, as well as critical access hospitals. This would require states to submit cost and payment data to CMS that previously was not requested.
Annually, CMS will request a list of covered durable medical equipment HCPCS codes from the Medicare Pricing, Data Analysis and Coding Contractor. Once the list is received, CMS will distribute the list through the CMS Regional Office Associate Regional Administrator.
To address claims run-out and ensure compliance with the FFP limit, we recommend states with these concerns conduct interim FFP limit demonstrations for DME no later than three months after the end of the calendar year for the previous calendar year (that is, January 1-December 31). The interim DME FFP limit demonstration will be due by March 31 of each calendar year and will contain data for the period of January 1 to December 31 of the preceding year. The final demonstration would be due one year later on March 31 and include all claims received during the run-out period dates of service within the interim demonstration period. The interim demonstration process should provide states with an understanding of potential violations of the FFP to make any necessary budgeting and rate changes. This method is being used to allow provide for a reasonable claims run out period as allowed under 42 CFR 424.44, which states that claims must be filed no later than one calendar year after the date of service.
Generally, information from the Federal data services hub will only be sent in direct response to a call from the requesting entity. However, in the case of verifications conducted by DHS, there can be up to three steps to a verification, the second and third of which will not be in real time. If the step 1 query fails, the Federal data services hub will automatically invoke step 2, and the response may take up to several days. If step 2 fails, the Federal data services hub will notify the requesting entity which will need to submit additional documentation from the applicant for step 3. The step 3 response can take weeks. During this time, the Federal data services hub will regularly poll DHS to see if the response has come back.
Supplemental Links:
The Centers for Medicare & Medicaid Services expects states receiving Federal Financial Participation to share with other states project artifacts, documents and other related materials, and systems components and code for leverage and reuse.
Read the state Medicaid director letter (SMD #18-005) on reuse. Reuse can be accomplished through sharing or acquiring:
- An entire set of business services or systems, including shared hosting of a system or shared acquisition and management of a turnkey service
- A complete business service or a stand-alone system module
- Subcomponents such as code segments, rule bases, configurations, customizations, and other parts of a system or module that are designed for reuse