PCMH Annual Reporting Submission Checklist

This checklist covers the annual PCMH reporting workflow from confirming the reporting year and DRI to reviewing required measures, completing the NCQA attestation, and submitting the package in Q-PASS. It is meant to track the submission process itself, not to replace the underlying quality or clinical documentation work. Use it to make sure every required step is completed in order and verified before the deadline.

Use it once per annual reporting cycle, with a clear recurrence tied to the organization’s PCMH deadline. Many teams also run a pre-deadline dry run a few weeks earlier to catch missing data, incomplete attestations, or approval bottlenecks. If your reporting calendar changes, update the recurrence_config so the task stays aligned to the actual submission window.

The DRI is usually a quality, compliance, or practice operations lead who can coordinate data collection, approvals, and final submission. Clinical leaders, analysts, and practice managers may each own checklist items, but one person should own the full workflow end to end. That keeps blocking items visible and prevents the submission from stalling on handoffs.

It supports the submission workflow, but it does not replace NCQA guidance, internal policy review, or the evidence behind each measure. You still need to confirm that the submitted data matches the organization’s source records and current program requirements. Treat this as an operational control for the annual filing, not as legal or accreditation advice.

Common failures include missing a required measure, using the wrong reporting period, forgetting to verify attestation details, and submitting before internal approval is complete. Another frequent issue is assuming the Q-PASS upload is finished without checking for validation errors or incomplete fields. This checklist adds verification steps so those problems are caught before the deadline.

Yes. You can add organization-specific measures, internal approvers, evidence links, and local review steps without changing the overall submission flow. If your system has multiple sites or service lines, split the checklist into checklist items that reflect each site’s data owner and approval path. Keep each item independently verifiable so the checklist stays easy to audit.

This template works well alongside annual quality reporting, policy attestation, and accreditation readiness checklists. It can also be linked to upstream data-collection tasks so the reporting team can see whether a measure is blocked or ready for submission. If you already use Kanban or ITIL-style runbooks, this checklist can serve as the final submission gate.

It is designed for planned annual reporting, where the steps, deadline, and approval chain are known in advance. For ad hoc corrections or resubmissions, create a separate task so the checklist does not get overloaded with exception handling. Keeping the annual workflow distinct makes it easier to track recurrence and avoid priority inflation.