What it actually means when Precisian says a finding is “citation-grade.” A worked example from a recent compliance engagement, anonymized, with the artifacts visible.
The phrase, before the work
“Citation-grade” gets used loosely in healthcare consulting. Most of the time it just means “we wrote down where this came from.” That is not what the phrase means in a Precisian case file. Citation-grade means a finding can be cross-examined by a Medicare Administrative Contractor reviewer, an Administrative Law Judge, or an OIG inquiry team, and the supporting record can be produced in under an hour, regulation cited, record located, quote highlighted, page numbered.
This piece walks through what that looks like in practice. The example is anonymized but the methodology is unchanged from a recent compliance program review we conducted for a multi-site post-acute operator under active UPIC scrutiny.
The case file the engagement opened with
The engagement opened with a single question from the Compliance Officer: If a contractor sampled twenty charts tomorrow, would our documentation hold? The answer, after the first chart audit pass, was no. Of twenty charts pulled at random, fifteen had at least one finding we classified as material exposure under contractor methodology. The Compliance Officer’s team had reviewed many of those same charts internally in the previous ninety days. None of the findings had surfaced internally.
The reason was simple: internal audit was checking the existence of documentation. Contractor methodology checks the defensibility of documentation. Those are different standards.
The three layers of a citation-grade finding
Every Precisian finding ties to three artifacts:
- The regulation. Cited to the title, part, and section. 42 CFR 484.55. 42 CFR 483.20. Medicare Benefit Policy Manual, Chapter 7, Section 30. Not “CMS rules,” not “the regulations.” The actual document, the actual section.
- The record. The specific chart entry, signature, order, or assessment that is supposed to satisfy that regulation. Identified by document name, date, patient identifier (anonymized in the case file), and page or section reference.
- The quote. The text from the record that either does or does not satisfy the requirement, captured verbatim. When the documentation is missing, the absence is documented as specifically as the presence would have been.
That is the spine of a citation-grade finding. Most internal compliance programs document the regulation. Some document the record. Very few document the quote and the absence of the quote with the rigor a contractor reviewer applies.
A worked example, from the same engagement
In one of the twenty charts, the resident’s Section GG functional scoring on the most recent MDS coded Self-Care Eating at a level of 04 (Supervision or touching assistance). The chart was selected for the Section GG sample because PDPM case-mix output for the resident exceeded the agency average and we wanted to test the audit defensibility.
The internal audit had reviewed the MDS and confirmed Section GG was completed. The Precisian case file finding read differently:
Finding 14-GG-Eating: Section GG self-care eating score (Item GG0130A) coded as 04 (Supervision or touching assistance) on MDS dated [date]. The MDS coding is not supported by clinical record review.
Regulation: RAI User’s Manual, Chapter 3, Section GG, page GG-12: “Code based on the resident’s level of assistance using clinician judgment and direct observation, as well as the assessment of qualified staff who provide care to the resident.”
Record: CNA shift documentation for the seven-day look-back period prior to the ARD. Days reviewed: [list of dates]. Total observations: 21 shifts.
Quote (from CNA documentation, [date]): “Resident fed independently. No assistance required. Tray returned approximately 80% consumed.” Quote (from CNA documentation, [date]): “Independent with all meals during shift.” Pattern across 21 shifts: No documentation of supervision, touching assistance, setup, or verbal cueing in any observed meal.
Defensibility assessment: The clinical record across the seven-day look-back does not support the coded level. The defensible code based on observed performance is 06 (Independent). The case-mix impact of the recode is approximately $X per day for the remainder of the PDPM stay.
Recommendation: MDS correction submitted per RAI guidance. Coder education on observed-versus-assessed performance scoring. Re-audit of Section GG eating, dressing, and toileting items across last six MDS submissions.
That is the structure. Regulation cited to the section. Record identified to the dates and shifts. Quote pulled verbatim from the source. Defensibility assessed against the actual standard. Recommendation tied to a remediation path with measurable signal.
Why the structure matters
If this same chart had been sampled by a UPIC reviewer six months later, the contractor would have built the finding the same way. The methodology is the methodology — whether the work is being done from the defense side or the audit side. That is why the standard matters. A finding written this way is already built to defend, because it was built using the same architecture the contractor will use to attack it.
The Compliance Officer in this engagement told us, after the case file was delivered, that the difference was not just rigor — it was language. The internal audit findings had been written for the Compliance Committee. The Precisian findings were written for the reviewer who would eventually sit across from the team in deposition. The audience shifts the standard.
What it takes to run at this standard internally
Three operational elements separate citation-grade compliance programs from the ones that decorate:
- Regulation indexing. Every internal audit category has a specified regulatory citation at the section level, maintained against current versions of the CMS State Operations Manual, RAI Manual, and applicable program manuals. The indexing is reviewed quarterly — regulations move, and stale citations are a tell that a program is paper-only.
- Verbatim record capture. Internal audit findings document the quote, not the summary. “Note did not document homebound status” is a summary. “Note dated [date], page 2, contains no reference to homebound status; the only ambulation reference reads: ‘Patient ambulated to clinic with cane.’” is the quote.
- Defensibility framing. Every finding asks: would this hold under cross-examination? If a reviewer disagrees with the call, is the underlying record specific enough to support the disagreement — or specific enough to support the agency’s position? Findings that cannot answer that question are surfacing exposure, not closing it.
The reason we are publishing this
The Precisian case-file methodology is not proprietary. It is contractor methodology, applied from the defense side, with the discipline of an investigative case file rather than a consulting deliverable. We publish the structure openly because the providers who run their compliance programs to this standard year-round are the ones who hold up at contractor sample — whether or not they work with us.
If your internal audit findings do not include the regulation, the record, and the verbatim quote, the program is operating at a different standard than the contractor will use when the sample lands. Closing that gap is the work. Open a case file with us if a sharper read on your program would be useful.