Reviewing Exported Service Notes: A Supervisor QA Workflow

Start by defining the reviewer and the criteria

Name the authorized reviewer, the records in scope, and the selected criteria before opening a queue. Criteria should be program-specific, versioned, and maintained by the organization responsible for the review.

Use a queue with distinct states

1. Ready for review: the source PDF and criteria version are present.
2. Possible finding: a signal points to page evidence and awaits human verification.
3. Finding disposition: the reviewer confirms, dismisses, or resolves the finding.
4. Document decision: the reviewer approves, returns, or escalates the document.

Require source-evidence inspection

A concise flag should link the reviewer back to the relevant page. The reviewer should compare the signal with the full source context and applicable guidance before deciding.

AI-generated review signals require human verification against the source document and applicable guidance.

Preserve disagreement and follow-up

A useful workflow records why a reviewer dismissed or confirmed a possible finding, who owns follow-up, and whether the document was approved, returned, or escalated. Recurring dismissals may indicate that criteria need refinement rather than that staff need correction.

Keep the boundary explicit

A review flag is not a determination of fraud or noncompliance. A completed review is an organizational workflow outcome—not a certification of compliance, billability, clinical adequacy, or legal sufficiency.

Sources and scope

This guide is operational education, not legal, billing, clinical, or compliance advice. Confirm current requirements with the applicable program authority and qualified organizational leaders.

• CMS HCBS Internal Records Review for Providers
• CMS Sample Checklists for Internal Monitoring and Auditing