Frequently Asked Questions

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. The A-87 Exception applies only to design, development, and implementation. Maintenance and operations work should continue to be allocated in accordance with the A-87 Circular. OMB Circular A-87  – Cost Principles for State, Local, and Indian Tribal Governments, has been Relocated to 2 CFR, Part 225 .

FAQ ID:93611

On July 20, 2015, the U.S. Department of Health and Human Services and the U.S. Department of Agriculture announced a three-year extension of the Exception to the OMB A-87 cost allocation requirements from December 31, 2015 to December 31, 2018. We are currently making plans for the OMB A-87 exception to end.

FAQ ID:93616

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.

FAQ ID:93621

For FFY2019 annual APDs and budget tables, including the Medicaid Detailed Budget Table (MDBT), must be completed as follows:

• For Q1 FFY2019, states can allocate costs in accordance with the OMB A-87 Exception
• For Q2-Q$ FFY2019, and all APDs going forward, states should allocate costs as required under the OMB A-87 Circular

If a state has already submitted their annual APDs without providing separate budgets they will need to complete an APDU with a revised MDBT and cost allocation plan. The update should address how cost allocation will be done prior to, and after, December 31, 2018. Budget tables should be completed as described above.

The Data and Systems Group (DSG) that approves APDs does not approve cost allocation methodology. States working to develop their new methodologies should send operational cost allocation plans to Cost Allocation Services  and the regional office fiscal staff for all benefiting programs.

FAQ ID:93626

State Medicaid Director Letter #17-004 addressed this area by stating: “Reductions necessary to implement CMS federal Medicaid payment requirements (e.g., federal upper payment limits and financial participation limits), but only in circumstances under which the state is not exercising discretion as to how the requirement is implemented in rates. For example, if the federal statute or regulation imposes an aggregate upper payment limit that requires the state to reduce provider payments, the state should consider the impact of the payment reduction on access.” In addition, the long-standing policy of the Medicaid program has been that Medicare rates are sufficient to ensure access.

FAQ ID:93521

We acknowledge that there are differences between the Medicare and Medicaid populations, but nothing in the policy guidance or statute compels states to reduce the items that states provide to people with disabilities under the state plan. As noted above, the statute does not expressly compel states to reduce the payment rates for DME. The statute limits the amount of money that the federal government will pay (i.e., FFP) for the relevant DME in the aggregate as compared with the relevant DME provided in the Medicare program. States retain the flexibility to make payments at rates that best serve the needs of their Medicaid beneficiaries.

FAQ ID:93526

In section 156.100 of the proposed rule on Essential Health Benefits/Actuarial Value/Accreditation, we propose criteria for the selection process for a state that chooses to select a benchmark plan. The essential health benefits benchmark plan would serve as a reference plan, reflecting both the scope of services and limits offered by a typical employer plan in that state. This approach and benchmark selection, which would apply for at least the 2014 and 2015 benefit years, would allow states to build on coverage that is already widely available, minimize market disruption, and provide consumers with familiar products. Since some base-benchmark plan options may not cover all ten of the statutorily required essential health benefits categories, we propose standards for supplementing a base-benchmark plan that does not provide coverage of one or more of the categories.

We also propose that if a base-benchmark plan option does not cover any items and services within an essential health benefits category, the base-benchmark plan must be supplemented by adding that particular category in its entirety from another base-benchmark plan option. The resulting plan, which would reflect a base-benchmark that covers all ten essential health benefits categories, must meet standards for nondiscrimination and balance. After meeting these standards, it would be considered the essential health benefits-benchmark plan.

The proposed rule also outlines the process by which HHS would supplement a default base-benchmark plan, if necessary. We clarify that to the extent that the default base-benchmark plan option does not cover any items and services within an essential health benefits category, the category must be added by supplementing the base-benchmark plan with that particular category in its entirety from another base-benchmark plan option. Specifically, we propose that HHS would supplement the category of benefits in the default base benchmark plan with the first of the following options that offer benefits in that particular essential health benefits category: (1) the largest plan by enrollment in the second largest product in the state's small group market; (2) the largest plan by enrollment in the third largest product in the state's small group market; (3) the largest national Federal Employees Health Benefit Program plan by enrollment across states that is offered to federal employees; (4) the largest dental plan under the Federal Employees Dental and Vision Insurance Program, for pediatric oral care benefits; (5) the largest vision plan under the Federal Employees Dental and Vision Insurance Program, for pediatric vision care benefits; and (6) habilitative services as described in section 156.110(f) or 156.115(a)(4).

Supplemental Links:

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

FAQ ID:94466

The U.S. Office of Personal Management released a proposed rule implementing the Multi-State Plan Program on November 30, 2012. To ensure that the Multi-State Plans are competing on a level playing field with other plans in the marketplace, the proposed regulation largely defers to state insurance law and the standards promulgated by HHS and states related to qualified health plans. Under the proposal, Multi-State Plans will be evaluated based largely on the same criteria as other qualified health plans operating in Exchanges. The few areas in which the Office of Personal Management proposes different regulatory standards from those applicable to qualified health plans are areas where the Office of Personal Management has extensive experience through its administration of the Federal Employees Health Benefits Program. However, in order to ensure that these few differences will not create any unfair advantages, the Office of Personal Management seeks comment from states and other stakeholders on these proposals. The regulation appeared in the Federal Register on December 5, 2012, and the comment period runs through January 4, 2013.

Supplemental Links:

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

FAQ ID:94471