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 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
When a facility has been in operation for the dates of service covered by the Upper Payment Limit (UPL) demonstration, can a state demonstrate the UPL by using less than 12 months of data?
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.
Can a state type information and data into unlocked fields in the Upper Payment Limit (UPL) templates or must the data from state-developed UPL reports/workbooks be mapped through, for example, V-Look-ups into the UPL templates?
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.
What data should my state provide to the Centers for Medicare & Medicaid Services (CMS) for the annual Upper Payment Limit demonstrations?
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.
What is reuse?
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 (PDF, 70.77 KB). 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
How do states get started with reuse?
To get started with reuse, a state can:
- Review the state Medicaid director letter (SMD #18-005) on reuse (PDF, 70.77 KB)
- View the introductory video to get familiar with the concept and framework of reuse
- Contact the Medicaid Enterprise Systems (MES) at MES@cms.hhs.gov to request access to the MES Reuse Repository
What is the Reuse Repository, and how can states access it?
The Centers for Medicare & Medicaid Services (CMS) established the Medicaid Enterprise Systems (MES) Reuse Repository to support states’ ability to share and reuse project life cycle artifacts. The repository is available on the CMS zONE (Opportunity to Network and Engage). States must have a CMS Enterprise Identity Management login to access the Reuse Repository.
View complete instructions for accessing the Reuse Repository.
Contact MES at MES@cms.hhs.gov for additional assistance in accessing the repository.
Is training available for reuse concepts and tools?
The reuse webpage on Medicaid.gov features an introductory video and more information about reuse. The webpage also has policy guidance documents.
The Medicaid Enterprise Systems Reuse Repository has instructions on how to use its features. These include how to add artifacts, search for artifacts, use the discussion forum features, and more.
How do states share?
States can share reusable artifacts with others in several ways. States can participate in workgroups such as the Medicaid Management Information System Cohort, State Technical Advisory Group, and any other relevant state groups to facilitate knowledge sharing, partnerships, and collaboration. States with access to the Reuse Repository also may add their reusable artifacts directly to the repository.
View complete instructions for accessing the Medicaid Enterprise Systems (MES) Reuse Repository. Contact MES at MES@cms.hhs.gov for additional assistance in accessing the repository or participating in workgroups.
If a state is reusing a system or module already certified in another state, do they still need to go through certification review and decision?
Certification is required for any new implementation, whether it is a custom- developed module that is transferred from another state, or a commercial off-the-shelf module that is being configured and integrated. The certification process looks at the state’s implementation of the solution to ensure the state has met all federal requirements.
States may reuse system documentation and other supporting evidence from a previous state certification if it is available and applicable to their systems and has been reconfirmed by independent verification and validation.
What aspects of reuse do states need to be aware of when developing advance planning documents (APDs)?
APDs must demonstrate a reuse-friendly design that includes the sharing of systems, modules, code, and any other developed artifacts. States could include language describing their efforts to find and learn from or reuse components from similar systems, or efforts the state is making to ensure that other states more easily can reuse the proposed system once it is developed.