U.S. flag

An official website of the United States government

Frequently Asked Questions

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.

Showing 1 to 10 of 34 results

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. 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

When does the OMB A-87 Exception expire?

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

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.

FAQ ID:93621

How should states account for OMB A-87 exception in their Advance Planning Documents (APD)

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

Are states only required to conduct Upper Payment Limit (UPL) demonstrations for services with approved state plan supplemental payment methodologies?

No, an upper payment limit demonstration considers all Medicaid payments (base and supplemental). States must conduct UPL demonstrations for the applicable services described in State Medicaid Director Letter (SMDL) 13-003 regardless of whether a state makes supplemental payments under the Medicaid state plan for the services.

FAQ ID:92191

Does a health plan's submission of information from its full eligibility file, for the purpose of matching that information to the Medicaid eligibility file, violate the Health Insurance Portability and Accountability Act of 1996 (HIPAA) privacy rules?

State laws determine what information is required of the health plans. A health plan's disclosure and use of information that is required to be submitted under state law - such as, information from insurer eligibility files sufficient to determine during what period any individual may be, or have been, covered by a health insurer and the nature of the coverage that is or was provided by the health insurer — is consistent with the HIPAA privacy provisions.

Under HIPAA, both the state Medicaid agency and most health insurers are covered entities and must comply with the HIPAA Privacy Rule in 45 CFR Part 160 and Part 164, Subparts A and E. In their capacities as covered entities under HIPAA, the state Medicaid agency and health insurers are restricted from using and disclosing protected health information (PHI), as that term is defined in 45 CFR section 160.103, other than as permitted or required by the HIPAA Privacy Rule. However, as relevant here:

  1. A covered entity may use or disclose PHI to the extent that such use or disclosure is required by law and the use or disclosure complies with and is limited to the relevant requirements of the law. (45 CFR 164.512(a)(1)) Under this provision, each covered entity must be limited to disclosing or using only the PHI necessary to meet the requirements of the law that compels the use or disclosure. Anything required to be disclosed by a law can be disclosed without violating HIPAA under the "required by law" provisions. Therefore, health insurers may disclose data elements in addition to the four minimum data elements, up to and including submission of an entire insurer eligibility file, to the extent such information is required to be submitted by state law. (45 CFR 164.512(a))
  2. Separately, a covered entity may use or disclose PHI, without the consent of an individual, for payment activities, including to facilitate payment. (45 CFR 164.502(a)(1) and 164.506) Under HIPAA, the term payment includes activities undertaken by a health plan to determine or fulfill its responsibility for coverage and provision of benefits under the health plan. These activities include determinations of eligibility or coverage, adjudication or subrogation of health benefits claims, and collection activities. (45 CFR 164.501) To the extent plans are releasing this information to the Medicaid program for payment purposes; this is a separate basis for disclosure under HIPAA.
  3. The HIPAA Privacy Rule generally requires covered entities to take reasonable steps to limit the use and disclosure of PHI to the minimum necessary to accomplish the intended purpose. (45 CFR 164.502(b)(1)) However, among other limited exceptions, the minimum necessary requirements do not apply to uses or disclosures that are required by law under 45 CFR 164.512(a).

Supplemental Links:

FAQ ID:91216

May state Medicaid agencies request information on subscribers and dependents covered in other states?

Yes. There is a significant amount of third party coverage derived from health plans licensed in a different state than where the Medicaid beneficiary resides. This can commonly happen when the policyholder works in one state and lives in another state. For example, there may be policyholders who are enrolled in Medicaid coverage in Maryland, or have dependents that are enrolled, who work in Delaware, the District of Columbia, Pennsylvania, Virginia, or West Virginia and also have coverage through their employer in that state. This highlights the need for Medicaid agencies to obtain plan eligibility information from contiguous states in addition to collecting information in their respective state.

Another example is when Medicaid-eligible children are covered by the insurance plan of non-custodial parents who live in a different state than their child(ren). This example is not limited to contiguous states because non-custodial parents could reside in any state in the country. Depending on the size, it may be beneficial for the state to obtain the plan's entire eligibility file. The specific geographical areas to be included in the data exchange should be negotiated with the plans. We recommend use of a Trading Partner Agreement in the exchange of electronic data.

Finally, section 1902(a)(25)(I)(i) of the Social Security Act directs states, as a condition of receiving federal financial participation (FFP) for Medicaid, to have laws in effect that require health insurers doing business in their state to provide the state with the requisite information with respect to individuals who are eligible for, or are provided medical assistance, i.e., Medicaid beneficiaries. State law cannot reach beyond the entities that are "doing business" in their states.

Supplemental Links:

FAQ ID:91221

May state Medicaid agencies use contractors to complete data matches with health insurers?

Yes. State Medicaid programs may enter into data matching agreements directly with third parties or may obtain the services of a contractor to complete the required matches. Such arrangements should comply with Health Insurance Portability and Accountability Act of 1996 (HIPAA)'s "Business Associate" requirements, where applicable. When the state Medicaid program chooses to use a contractor to complete data matches, including matches as required by the Deficit Reduction Act of 2005 (DRA), the program delegates its authority to obtain the desired information from third parties to the contractor.

Third parties should generally treat a request from the contractor as a request from the state Medicaid agency. Third parties may request verification from the state Medicaid agency that the contractor is working on behalf of the agency and the scope of the delegated work.

Supplemental Links:

FAQ ID:91226

Can Medicaid Managed Care Organizations (MCOs) use a contractor to complete data matches with health insurers, as authorized by the state Medicaid agency?

Yes. State Medicaid programs may contract with MCOs to provide health care to Medicaid beneficiaries, and may delegate responsibility and authority to the MCOs to perform third party liability TPL discovery and recovery activities, including data matches as required by the Deficit Reduction Act of 2005 (DRA). The Medicaid program may authorize the MCO to use a contractor to complete these activities. The contract language between the state Medicaid agency and the MCO dictates the terms and conditions under which the MCO assumes TPL responsibility. Generally, any TPL administration and performance standards for the MCO will be set by the state and should be accompanied by state oversight.

When TPL responsibilities are delegated to an MCO, third parties are required to treat the MCO as if it were the state Medicaid agency, including:

  1. Providing access to third party eligibility and claims data to identify individuals with third party coverage;
  2. Adhering to the assignment of rights from the state to the MCO of a Medicaid beneficiary's right to payment by such insurers for health care items or services; and,
  3. Refraining from denying payment of claims submitted by the MCO for procedural reasons.

Third parties may request verification from the state Medicaid agency that the MCO or its contractor is working on behalf of the agency and the scope of the delegated work.

Supplemental Links:

FAQ ID:91231

What is the responsibility of liable third parties regarding health insurers' denials of Medicaid claims based on insurers' procedural requirements?

Under section 1902(a)(25)(H) of the Social Security Act (the Act) before passage of the Deficit Reduction Act of 2005 (DRA), states were required to have laws in effect that to the extent Medicaid payment was made, the state was considered to have acquired the rights of the Medicaid beneficiary to reimbursement by any other party that was liable for payment. However, payers sometimes deny Medicaid claims based on procedural requirements. Section 1902(a)(25)(I) of the Act, added by the DRA, strengthens the statute by requiring states to enact laws that require health insurers:

  1. To accept the state's right of recovery and the assignment to the state of the right of a Medicaid beneficiary or other entity to payment from such party for an item or service for which Medicaid has made payment; and,
  2. To process and, if appropriate, pay the claim for reimbursement from Medicaid to the same extent that the plan would have been liable had the plan's card been used for billing at the "point of sale" (POS).

Specifically, the state should pass laws which require an insurer to agree not to deny claims submitted by the state on the basis of the date of submission of the claim, the type or format of the claim form, or a failure to present proper documentation of coverage at the POS that is the basis of the claim.

Whether a plan provision affecting payment for an item or service is solely procedural in nature or whether it defines or limits the covered benefits must be determined on a case-by-case basis.

Note that nothing in the DRA negates the state's responsibility to provide proper documentation when submitting claims to the health insurer so that the insurer can determine that a covered service for which the insurer is liable was provided.

Supplemental Links:

FAQ ID:91236

Results per page