SNF QRP Data Validation: Assemble the Selected Medical Records and Prove Receipt

Read the current request before retrieving charts

The CMS data-validation FAQ dated October 30, 2026 gives operational instructions for the current process. The official notification is placed in the MDS 3.0 Provider Preview Reports folder in iQIES. The request identifies the selected assessments, documentation and submission instructions; an email alert alone does not define the production scope.

Assign the requested points of contact promptly. The FAQ calls for their submission within five business days of receipt of the notification letter. Use the current letter's link and instructions, including for a later year's selection; do not assume a previous contact submission remains sufficient.

The FAQ describes a 45-calendar-day submission period from the initial notification and a next-business-day adjustment when the deadline falls on a weekend or federal holiday. Preserve the original notification and calculate the actual deadline against the current letter and FAQ. Do not start a new clock when a department eventually opens its retrieval task.

Reconcile requests, records and files separately

The SNF QRP regulation establishes selected medical-record validation, including up to ten records per selected facility and a separate 100-percent selected-chart submission threshold. The operational goal is complete requested documentation, not a favorable file count.

Consider a fictional seven-record request:

The first upload contains six PDF files. That number does not establish whether six or seven requested records were fully covered: a record may span files, and a file may be incomplete. The team maps each requested item to the actual pages and date range, corrects E, F and G, and reconciles the resulting files to all seven requests.

This manifest is an original internal control, not a CMS form. It should use the naming and organization required by the actual request. Avoid changing those instructions merely to fit a local export convention.

Follow the secure channel and document scope

The FAQ identifies a secure portal through the notification letter and PDF submission. It describes request-specific naming, date ranges and documentation sections, and exclusions such as Social Security numbers, photographs, face sheets and material outside the requested dates. Apply the current instructions carefully; do not send the notification letter or medical records through ordinary email.

Supporting documentation must show the relevant clinical record. A generic assertion that an assessment item came from “observation” or “interview” may not provide the requested evidence. Preserve the underlying facts and source history; validation is not an occasion to create retrospective observations or change a supported MDS response to match a preferred result.

Close only after the request is reconciled

CMS distinguishes an automated successful-upload message, including the file count, from a separate message verifying submission of all requested documentation. Keep both. If a confirmation is absent or identifies a gap, use the request's support route promptly and retain the communication.

The FAQ also distinguishes informational validation findings from participation requirements. A validation summary does not justify assuming the selected-record submission obligation was satisfied, and participation does not guarantee that every reviewed item will agree with its supporting record.

The finished packet links the original request, seven-record manifest, actual transmitted files, upload evidence and completeness confirmation. For a platform buyer, this is a concrete test of whether fragmented clinical records can be assembled accurately and their delivery explained before a request-specific deadline.