PCMH Annual Reporting Submission Checklist

This checklist covers the annual NCQA PCMH attestation workflow from gathering evidence to final submission in Q-PASS. It is meant for the reporting cycle, not for day-to-day care management or initial recognition setup. Use it to verify required measures, confirm supporting documentation, and complete the submission before the deadline.

The DRI is usually a practice manager, quality coordinator, or PCMH program lead, with input from clinical leadership and data/reporting staff. If your organization uses a centralized quality team, that team can own the checklist while local clinic staff supply evidence. The key is to assign one accountable owner so blocking issues do not stall the submission.

This checklist should recur annually, aligned to the NCQA reporting cycle and your internal deadline buffer. Many teams also run a pre-deadline review checkpoint a few weeks earlier to catch missing measures or broken links. If your organization has multiple sites, you may want a site-level prep checklist before the final enterprise submission.

Common failures include missing evidence files, using the wrong reporting period, and submitting measures that do not match the attestation narrative. Teams also miss internal review steps, which creates last-minute blocking issues when leadership asks for revisions. This checklist helps by breaking the work into independently verifiable checklist items instead of one large end-of-cycle task.

Yes, it is designed around the compliance workflow for NCQA PCMH annual reporting and attestation. It supports verification steps, evidence collection, and submission readiness, which are the parts most likely to create audit or filing risk. You should still confirm the exact measure set and instructions for your recognition year, because NCQA requirements can change.

Yes, and customization is expected. You can add site-specific evidence requests, internal approval steps, payer-specific reporting notes, or a final sign-off step from the DRI. Keep each checklist item atomic so a yes/no answer is clear and the team can see exactly what is done, blocked, or still pending.

Email threads and spreadsheets often hide ownership, make it hard to see blocking items, and create version confusion near the deadline. A checklist template gives you a single runbook with clear recurrence, assignment, and verification steps. That makes it easier to track progress and reduce rework when multiple people contribute evidence.

Yes, the checklist can point to source documents, shared folders, Q-PASS records, and internal approval workflows. Many teams link each checklist item to the exact evidence file or report needed for verification. That keeps the submission process traceable without forcing people to search across disconnected tools.

Mark the item as blocking, assign a DRI, and escalate immediately to the person who can resolve it. If the issue cannot be fixed before submission, document the gap clearly and route it through your internal compliance review process. The checklist should make the risk visible early enough that leadership can decide whether to proceed or delay.