For MY 2011 P4P tables CWP-C and URI-D, crosswalk to the HEDIS 2012 NDC list for table CWP-C.
*Note: The MY 2011 P4P crosswalk to HEDIS 2012 NDC List posted on December 8, 2011, has been corrected.
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.
For the MUHIT domain, intent refers to the measures criteria, as specified in the Intent section. For Required Submission item 4, count the number of PCPs, or the number of patients assigned to PCPs who meet the criteria listed for each measure. Assign the number of points that correspond to the percentage of PCPs meeting the measures intent.
In MY 2011, health plans may submit results for the Medicare product line and for the commercial product line. Because the Medicare product line is now reported by health plans, the Health Plan Clinical and Testing Measure file layouts have three tabs for the possible reporting scenarios (commercial HMO/POS and Medicare, commercial HMO/POS only, Medicare only).
Scenario 1: The health plan has both commercial HMO/POS and Medicare product lines
Clinical Measure File Layout: Plans that report for both the commercial HMO/POS and Medicare populations must have 66 clinical measure IDs per DMHC ID/Sub Unit, even if an individual PO has only commercial or Medicare enrollment.
Testing Measure File Layout: Plans that report for both the commercial HMO/POS and Medicare populations must have 31 clinical measure IDs per DMHC ID/Sub Unit, even if an individual PO has only commercial or Medicare enrollment.
Refer to Tab (5) Sample HP FileBoth Commercial and Medicare
Examples 1_3: The plan has commercial and Medicare product lines; Pos 11111-00, 22222-03, 22222-05 and 33333-05 also have commercial and Medicare members: the plan submits commercial and Medicare data for these Pos.
Example 4: The plan has commercial and Medicare product lines; PO 44444-01 has only Medicare members: the plan submits Medicare data for PO 44444-01 and populates commercial rows for PO 44444-01 with zero enrollment, zero denominator, zero numerator and rate NB.
Scenario 2: The health plan has commercial HMO/POS product line only
Refer to Tab (6) Sample HP FileCommercial Only: Plans that have the commercial product line only submit data for the commercial product. There are no rows for the Medicare product.
Clinical Measure File Layout: The plan reports 59 clinical measure IDs per DMHC ID/Sub Unit for the commercial product.
Testing Measure File Layout: The plan reports 10 testing measure IDs per DMHC ID/Sub Unit for the commercial product.
Scenario 3: The health plan has Medicare product line only
Refer to Tab (7) Sample HP FileMedicare Only: Plans that have the Medicare product line only submit data for the Medicare product. There are no rows for the commercial HMO/POS product.
Clinical Measure File Layout: The plan reports 7 clinical measure IDs per DMHC ID/Sub Unit for the Medicare product.
Testing Measure File Layout: The plan reports 21 clinical measure IDs per DMHC ID/Sub Unit for the Medicare product.
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.
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.
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.