An organization must provide documentation that the community hospital/clinic meets DEA requirements. The organization must also include evidence of verification of the facility DEA in the credentialing file.
FAQ Directory
Here are some of the most frequently asked questions about NCQA’s various programs. If you don’t see what you are looking for in one of the entries below, you can ask a question through My NCQA.
Filter Results
-
Save
Save your favorite pages and receive notifications whenever they’re updated.
You will be prompted to log in to your NCQA account.
Save your favorite pages and receive notifications whenever they’re updated.
You will be prompted to log in to your NCQA account.
-
Email
Share this page with a friend or colleague by Email.
We do not share your information with third parties.
Share this page with a friend or colleague by Email.
We do not share your information with third parties.
-
Print
Print this page.
Print this page.
2.15.2012 Facility DEA What type of documentation should health plans include in credentialing files, if the DEA allows all practitioners in a community hospital/clinic to be covered under facility DEA?
2.15.2012 Notification of expedited external review for Medicare in UM 7, Element D How is factor 4 scored for Medicare members in UM 7, Element D?
2.15.2012 Personal care add-on benefits Are personal care services that are add_on benefits, such as cooking, grooming, transporting, cleaning and assistance with other ADL activities that are not part of medical benefit, subject to review under UM 4-UM 7?
No. Add-on personal care services do not fall within the scope of UM 4-UM 7, but they can be appealed under RR 2 or UM 8 and UM 9. Personal care services that are a part of the medical benefit fall within the scope of medical necessity review if an assessment must be done to determine the member is eligible for the services or if the services will be covered. In such cases, the services would be within the scope of UM 4-UM 7.
This applies to the following Programs and Years:
2.15.2012 Verifying Sanction Information Every 30 Calendar Days Are organizations required to verify sanction information at recredentialing if the information is verified within 180 calendar days at initial credentialing, and every 30 calendar days thereafter?
The answer depends on whether the organization presents sanction information every 30 days to its Credentialing Committee. If so, there is no need to report it at the time of recredentialing. If not, the organization would need to verify and present adverse information to the Credentialing Committee at recredentialing.
This applies to the following Programs and Years:
2.15.2012 Behavioral healthcare practitioner involvement in program design Must the behavioral healthcare practitioner involved in program design be employed by the organization, or may the behavioral healthcare practitioner be a consultant?
2.14.2012 Notification of expedited external review for Medicare in UM 7, Element G How is factor 4 scored for Medicare members in UM 7, Element G?
1.17.2012 Use of Virtual Hold in call abandonment rates Our member phone system measures wait time. If the wait time hits a certain threshold, members can hang up, keep their place in the queue and receive an automatic call back when the next customer support person is available. The system is set to call back every five minutes, for three attempts. When members answer the call-back, they are connected to the customer support person. If a member does not answer after three attempts, is the call considered abandoned, based on the Call Abandonment criteria?
Yes. If the member does not answer the call-back, it is counted as abandoned. If the member answers the call-back and the reports show the results, the call is not counted as abandoned because the member was kept in the queue.
For timeliness (Element C, factor 1), because it is unlikely that the system would start the call-back process before 30 seconds, the call counts as answered outside the 30 seconds.
This applies to the following Programs and Years:
1.17.2012 Use of Virtual Hold in call abandonment rates Our member phone system measures wait time. If the wait time hits a certain threshold, members can hang up, keep their place in the queue and receive an automatic call back when the next customer support person is available. The system is set to call back every five minutes, for three attempts. When members answer the call-back, they are connected to the customer support person. If a member does not answer after three attempts, is the call considered abandoned, based on the Call Abandonment criteria?
Yes. If the member does not answer the call-back, it is counted as abandoned. If the member answers the call-back and the reports show the results, the call is not counted as abandoned because the member was kept in the queue.
For timeliness (Element C, factor 1), because it is unlikely that the system would start the call-back process before 30 seconds, the call counts as answered outside the 30 seconds.
This applies to the following Programs and Years:
1.17.2012 Use of Virtual Hold in call abandonment rates Our member phone system measures wait time. If the wait time hits a certain threshold, members can hang up, keep their place in the queue and receive an automatic call back when the next customer support person is available. The system is set to call back every five minutes, for three attempts. When members answer the call-back, they are connected to the customer support person. If a member does not answer after three attempts, is the call considered abandoned, based on the Call Abandonment criteria?
Yes. If the member does not answer the call-back, it is counted as abandoned. If the member answers the call-back and the reports show the results, the call is not counted as abandoned because the member was kept in the queue.
For timeliness (Element C, factor 1), because it is unlikely that the system would start the call-back process before 30 seconds, the call counts as answered outside the 30 seconds.
This applies to the following Programs and Years:
1.16.2012 Proportion of Days Covered by Medications Should days covered be capped at the number of days for the measurement period? For example, if a members measurement period is January 1_June 30, 2011 (180 days), and the member fills different prescriptions within the class (different GCNs) on January 1, April 1 and June 15, all with a 90-day supply (195 days within the measurement period), should the days covered be calculated as 180 days?
In your example, the measurement period is 180 days (January 1_June 30). Step 2 of the numerator criteria reads, "within the measurement period, count the number of days the member was covered." In this case, look for covered days from January 1_June 30; in essence, the numerator is being capped. The PDC is not calculated by summing the days supply for pharmacy claims. You may need to set up a time array for each claim, to identify the time frame covered by each fill, then count the number of days in the measurement period that are covered by the time arrays. Thus, the numerator may not exceed the denominator for the person-level PDC calculation. Refer to the attached example for SAS code for arrays.
This applies to the following Programs and Years:
1.16.2012 Proportion of Days Covered by Medications For all rates, step 2 of the numerator states that organizations should count the days when a member was covered by at least one drug in the class. However, each rate indicates that there are additional eligible population criteria for the member to have filled at least two prescriptions for the target drug. How can the numerator allow for just one drug in the class to be filled?
At least two prescriptions means that the patient had at least two pharmacy claims for a drug in the target class (this can be refills for the same drug). In the numerator, for a day to be covered, a patient must have a supply on hand of at least one drug in the class.
This applies to the following Programs and Years:
1.16.2012 Proportion of Days Covered by Medications How do you account for claim reversals?
PDC measures are calculated through use of paid, nonreversed claims for target medications. If the drug claims dataset contains claim reversals (and paid claims that were reversed), analysts must ensure that the reversed claims are not used to calculate PDC. Claim reversals can be identified through multiple methods because there may be multiple fields in a drug claim that indicate whether it is a reversal. Many drug claims datasets have a Count field that contains a 1 for a paid claim and a -1 for a claim reversal. The dataset may also have a field called Reversal that contains a Y if the claim is a reversal claim, or an N if it is not a reversal. Reversal claims typically have a negative quantity and a negative cost.
The claim reversal (-1 in the Count field or Y in the Reversal field) may have a Claim Number that is identical to the original claim being reversed. If the Claim Number for the reversal claim is not identical to the Claim Number for the original claim, analysts can create coding logic that will identify the reversed claim as immediately preceding the claim reversal. This latter approach is not usually necessary because most drug claims datasets allow a claim reversal to be linked to an original claim.