Are documentation QA and ERA denial review the same workflow?

No. Documentation QA is a pre-billing-handoff review of the source record; ERA denial review is post-adjudication analysis of what the payer returned in an 835 file.

Does an ERA prove that documentation caused a denial?

No. An ERA reports adjudication results and adjustment or remark codes. It does not contain the underlying clinical note and does not establish documentation causality.

Which One Care Portal path should an agency evaluate first?

Start with Case Management when the agency needs to run caseloads, plans, visits, notes, authorizations, and supervisor workflows. Consider validation-stage Documentation Intelligence for a separate human-reviewed PDF QA concept, or the available standalone ERA Dashboard for 835 visibility.

Are Documentation Intelligence and ERA Dashboard integrated?

No integration is represented. They are separate products and workflows, and no integration or causal relationship should be inferred.

Documentation Quality + ERA Review

Direct answer: Use human documentation QA before the billing handoff, then analyze payer adjudication results after an 835 ERA arrives. These are separate workflows that answer different questions.

Written by One Care Portal · Reviewed by One Care Portal · Updated September 20, 2026

Control point 1: pre-billing-handoff documentation QA

This control asks whether a source record appears complete, readable, internally consistent, and ready for an authorized person's next review. A practical team can check organization-selected criteria, inspect the source evidence, resolve missing details or contradictions, and record a human disposition before a separate billing decision.

This review does not certify compliance, billability, fraud, clinical adequacy, legal sufficiency, or payer outcome. CMS explains that records must support coverage, coding, and billing requirements and that incomplete or illegible records can lead to denied payment; use current payer and program requirements with qualified review. CMS: Complying with Medical Record Documentation Requirements.

Control point 2: post-adjudication 835 remittance analysis

This control begins after the payer adjudicates claims and sends an X12 835 ERA. Teams review billed and paid totals, paid and denied claims, group codes, CARCs, RARCs, and rendering-provider NPI information when present. They can group the returned results, prioritize follow-up, and export review data into the team's existing process.

The ERA does not contain the underlying clinical note. A code can guide research, but it does not prove why documentation failed or establish that a particular note caused a denial. Confirm the payer's code definitions, claim history, source records, contracts, and applicable guidance before deciding the next action.

Keep the two workflows separate

Before billing handoff

Confirm the intended source record.
Apply organization-selected review criteria.
Inspect evidence and clarify possible gaps.
Record an authorized human disposition.
Make the billing decision separately.

After adjudication

Confirm payer, payment, and ERA scope.
Separate paid, denied, and adjusted claims.
Read group codes with CARC/RARC context.
Prioritize records for investigation.
Export into the team's established follow-up process.

These are separate workflows and products. No integration or causal relationship should be inferred between a documentation review signal and an ERA result.

Route the buyer to the right OCP path

Case Management comes first when an agency needs to run caseloads, plans, visits, notes, authorizations, and supervisor workflows.
Documentation Intelligence is a separate validation-stage concept for manually uploaded PDFs, organization-selected criteria, evidence-linked possible findings, and human disposition. It has no represented Case Management, Billing, clearinghouse, or ERA integration and no public price.
ERA Dashboard is an available standalone product that reads standard X12 835 files and presents billed and paid totals, paid and denied claims, rendering-provider NPI views when present, CARC/RARC explanations, and exportable review data.

For a focused operating sequence, read the copy-forward risk review guide and the 835 ERA denial worklist guide.

Implementation checklist

Name an owner for each control point.
Document when a record enters and exits pre-billing review.
Keep possible findings distinct from final human decisions.
Record the payer, file, claim, code, and source used for denial research.
Define escalation rules without assuming a denial reason is a documentation defect.
Measure queue age and completion without mixing the two control populations.

Documentation Quality and ERA Denial Review: Two Separate Controls