Frequently Asked Questions

A validation error occurs when additional information is required for certain fields on a page. This error will be indicated by red script on the page under the section that was required. In order to avoid a validation error, enter in all required information before attempting to validate data. For many screens this will occur upon selecting a button located towards the bottom of the page to validate your entries.

FAQ ID:92936

This table indicates what reports are available to State Users. These can be found under the "Reports" tab.

FAQ ID:92941

Once a state submits a submission package to CMS, they may not edit it while it is in review. The state may withdraw the submission package, but once withdrawn, the package cannot be edited or resubmitted.

CMS may open the package for revisions informally via a clarification request. Clarification questions are entered into the Correspondence Log. The CPOC can compile questions from the Submission Review Team members by accessing the Analyst Notes. Please note, that the reviews of every RU does not have to be completed in order to send a request for Clarification to the State. During a Clarification, the State will have the opportunity to edit content. After the state has responded to Clarification, the CMS Point of Contact must assign Submission Review Team members to Reviewable Units again and review the submission package again.

After requesting Clarification, CMS (specifically the CPOC) has the option to prevent package submission. This is a way for CMS to pull the package back from the Clarification request. This may be necessary as the clock continues during the Clarification period. The CMS review team may not continue their review while the package is back with the State for Clarification, therefore the CPOC should exercise caution when to sending a Clarification, knowing that review will be temporarily suspended.

Another option is after CMS Point of Contact has reviewed the submission package, he/she has the option to Request Additional Information regarding the submission package. All Reviewable Units must appear in the complete status (represented by a checkmark) by having at least one Review Team member complete the review in order to initiate RAI. RAI stops the 90 Day Clock. In this option, the State will have the opportunity to edit content.

FAQ ID:92991

Select the "Records" tab in the upper tool bar. Click on the Quality Measure you are working with and then search for the report you would like to view by entering the report package ID.

FAQ ID:92996

Yes, at the end of each report there is an "Upload Documents" section that allows you to upload any relevant documents.

FAQ ID:93011

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:

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

FAQ ID:91216

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:

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

FAQ ID:91221

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:

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

FAQ ID:91226

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:

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

FAQ ID:91231

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:

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

FAQ ID:91236