Two operational control points

Documentation quality and ERA denial review: two separate controls

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.

Qualified agency staff interpret possible findings and make the final program, billing, clinical and compliance decisions. 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.

Use the ERA's adjustment and remark codes to guide research, then consult the payer's code definitions, claim history, source records, contracts and applicable guidance. Qualified staff determine the reason and next action from the complete evidence.

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 distinct review points. Qualified staff can use the source record, claim history and payer response together when deciding what to investigate next.

Route the buyer to the right OCP path

  1. Case Management comes first when an agency needs to run caseloads, plans, visits, notes, authorizations, and supervisor workflows.
  2. Compliance Review is a separate human-reviewed documentation QA module for manually uploaded PDFs, organization-selected criteria, evidence-linked possible findings, and human disposition. Start with PDF uploads today, and discuss the connected workflow your agency wants to build. See published standalone pricing on the product page.
  3. 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 based on verified evidence.
  • Measure queue age and completion for each control point.

Choose the right review workflow

Start with Case Management fit, or discuss a separate documentation-review workflow. Do not include PHI, service-recipient names, clinical details, claims, ERA files, or records in the booking flow.

Discuss Your Workflow

Frequently asked questions

When should our team use each review?

Use documentation QA to review the source record before billing handoff. Use ERA denial review to inspect the payer's 835 results after adjudication.

How do we investigate a denial that may involve documentation?

Start with the ERA adjustment and remark codes, then compare the claim history, payer guidance and source record. Qualified staff determine the reason and next step from the available evidence.

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. Use Compliance Review for separate human-reviewed PDF QA, or the available standalone ERA Dashboard for 835 visibility.

How do Compliance Review and ERA Dashboard fit together?

Use Compliance Review for human QA before the billing handoff and ERA Dashboard to inspect 835 results afterward. Tell us how you want these workflows to connect so we can plan the right setup together.