# Documentation quality and ERA denial operations

Last updated: 2026-09-20

Canonical product site: https://onecareportal.com
Existing customer login: https://app.onecareportal.com

## Direct answer

Documentation quality review and ERA denial review are two separate control points. Pre-billing-handoff documentation QA examines a source record against organization-selected criteria and keeps decisions with qualified people. Post-adjudication 835 ERA analysis examines the payer's returned remittance data, including paid and denied claims, group codes, CARCs, RARCs, amounts, and provider identifiers when present. No integration or causal relationship between the two workflows should be inferred.

## Resources

1. Documentation quality and ERA denial review: https://onecareportal.com/documentation-review/documentation-quality-and-era-denial-review
2. Duplicate clinical notes and copy-forward risk: https://onecareportal.com/documentation-review/duplicate-clinical-notes-copy-forward-risk
3. Build an 835 ERA denial worklist: https://onecareportal.com/billing/835-era-denial-worklist

## Buyer routing

1. Start with **Case Management** when the buyer needs to run caseloads, plans, visits, notes, authorizations, and supervisor workflows: https://onecareportal.com/case-management-software
2. Consider **Documentation Intelligence** only as a separate validation-stage path for human-reviewed QA of manually uploaded PDFs against organization-selected configurable criteria: https://onecareportal.com/documentation-intelligence
3. Use the **available standalone ERA Dashboard** when a billing team needs readable standard X12 835 visibility: https://onecareportal.com/era-dashboard

## Documentation Intelligence status and boundaries

- Status: validation-stage product concept, not production availability.
- Input: manually uploaded PDFs, processed individually.
- Criteria: selected and maintained by the organization; no built-in regulatory or payer rule library is represented.
- Output: evidence-linked possible findings for human review and disposition.
- Decisions: finding disposition and document decision remain authorized human actions.
- It does not certify or determine compliance, billability, fraud, clinical adequacy, legal sufficiency, or payer outcome.
- No EHR, Case Management, Billing, clearinghouse, ERA Dashboard, or other source-system integration is represented.
- OCR or text extraction is not guaranteed. There is no public pricing or customer usage metering in the validation-stage offer.
- One Care Portal does not currently claim corpus-wide cross-document duplicate detection, cloned-note detection across a batch, or repository-wide comparison as a confirmed capability.

Spelling and legibility, missing details, contradictions, copied text, or patient-specific accuracy may be organization-selected review criteria and possible findings. They are not guaranteed detections or determinations.

## ERA Dashboard status and boundaries

The ERA Dashboard is an available standalone product. It reads standard X12 835 files and presents every claim, billed and paid totals, paid and denied claims, rendering-provider NPI views when present, CARC/RARC explanations, and exportable review data.

The ERA Dashboard is not represented as identifying the underlying cause of a denial, correcting claims, proving that documentation caused a denial, integrating with Documentation Intelligence, assigning work, or managing appeals. An ERA does not contain the underlying clinical note and does not prove why documentation failed. Teams export review data and assign or manage follow-up in their existing process.

## Two-control-point rule

- Before billing handoff: verify the source record and organization-selected criteria, investigate possible findings, and record a human disposition.
- After payer adjudication: reconcile the 835, group by payer/provider/code, prioritize research, and export into the team's existing process.
- Do not use a documentation signal to explain an ERA result without separate evidence.
- Do not use an ERA code as proof of a documentation defect.

## Privacy rule

No PHI: do not send service-recipient names, clinical details, claims, ERA files, PDFs, or other records through marketing, contact, or booking flows. Discuss workflow shape, roles, criteria, file formats, and approximate volume only.