U.S. flag

An official website of the United States government

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.

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.

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.

What is the impact of the OMB A-87 expiration for states utilizing the exception for system integration development?

States will need to incur costs for goods and services furnished no later than December 31, 2018 to make use of this Exception. Therefore, if work is completed by December 31, 2018, it can be funded under the OMB A-87 Exception and states should follow typical invoicing and claiming processes. However, if an amount has been obligated by December 31, 2018, but the good or service is not furnished by that date, then such expenditure must be cost allocated by program in proportion to their use of the system in accordance with OMB A-87.

What is the Office of Management and Budget (OMB) Circular A -87 Exception?

OMB Circular A-87requires costs associated with building shared state-based Information Technology (IT) systems that support multiple health and human service programs be allocated across all benefitting programs in proportion to their use of the system. The OMB A-87 Exception revised this approach by allowing human service programs (e.g. SNAP, TANF, LIHEAP, etc.) and others to utilize a wide range of IT components, needed by Medicaid but also of use to these other programs, at no additional cost except for interfaces or other uniquely required services specific to those programs.

If Medicare changes a rate mid-year, how will the reporting requirement account for that change? Or how will the state be informed of the change?

For the aggregate demonstration of Medicaid expenditures, we intend to use the Medicare rates released for services on or after January 1 of each year. We would suggest that states setting their rates according to Medicare rates in the state plan would follow a similar practice. States are, of course, welcome to use the quarterly updates of durable medical equipment, prosthetics, orthotics and supplies (DMEPOS) if that’s their intention, but we are not requiring those rate updates beyond the January 1 DMEPOS update.