AI-assisted documentation QA · Product validation

Documentation Intelligence for Medicaid and Human-Service Agencies

AI-assisted review. Human-controlled decisions.

One Care Portal is validating a workflow designed to review manually uploaded PDFs against the criteria your organization selects. It would surface evidence-linked possible findings while authorized human reviewers inspect the source and make and record each disposition.

Keep the EHR, state system, or case-management platform your agency already uses.

See how the review workflow works

Do not submit PHI, service-recipient names, clinical details, or records through the marketing booking flow.

The operating problem

A source system can store the record without providing the review workflow your team needs

High-volume reviews often move through samples, spreadsheets, and email. Criteria vary by program and supervisors need to distinguish an AI signal from the organization's final decision.

Inconsistent review coverage

Teams may review only part of a high-volume queue or discover missing information late.

Disconnected follow-up

Possible issues, corrections, and dispositions can become scattered across spreadsheets and email.

Mandatory source systems

The system you must keep may not support the agency's preferred criteria or QA queue.

A three-step, human-controlled review workflow

1 · Upload

Add existing PDF records

Choose the program and manually upload supported PDF documentation exported from the source system.

2 · Inspect

Review evidence-linked signals

Evaluate the document against selected configurable criteria and inspect the page evidence behind each possible finding.

3 · Decide

Record the human outcome

Finding disposition: confirm, dismiss, or resolve. Document decision: approve, return, or escalate. Each action remains an authorized human decision.

Validation scope

Know the current boundaries before discussing fit

Files: manually uploaded PDFs only, processed individually, with a maximum size of 20 MB per PDF.

Evidence: AI-provided evidence text with a cited PDF page for human verification.

Extraction: text extraction or OCR is not guaranteed for scanned, handwritten, protected, or low-quality PDFs.

Criteria: configured and maintained by the organization; no built-in regulatory or payer rule library is represented.

Integrations: no EHR, Case Management, Billing, clearinghouse, or source-system integration is represented in this validation.

Commercial controls: customer usage metering and public pricing are not part of this validation-stage offer.

Evaluation examples

What reviewers may look for

Based on the selected criteria and the information available in the individually uploaded document, Documentation Intelligence may help reviewers look for:

  • missing expected elements;
  • unclear or incomplete narratives;
  • internal inconsistencies;
  • expected signatures or attestations;
  • possible service-plan or goal disconnects;
  • date, time, location, or unit details when present and included in the selected criteria.

One Care Portal does not currently claim corpus-wide cross-document duplicate detection or batch note comparison as a confirmed capability. Read the duplicate-note and copy-forward risk guide.

Decision boundaries

A possible finding is not a determination

Documentation Intelligence does not certify or determine compliance, billability, fraud, clinical adequacy, or legal sufficiency.

  • A review flag is not a determination of fraud or noncompliance.
  • The product does not guarantee payment, compliance, or audit outcomes.
  • It does not replace qualified program, billing, clinical, compliance, or legal judgment.
  • It does not invent missing documentation.
  • A completed review is an organizational workflow outcome, not a compliance certification.

Existing-system coexistence

Add a review layer without replacing the system your organization must use.

Review records the organization already creates.

Begin with one program or service line.

Keep the existing system as the authoritative source.

Use the human queue to decide what needs follow-up.

Choose the right One Care Portal path

Primary operating platform

Need to run the care workflow?

Choose Case Management for caseloads, plans, visits, notes, authorizations, supervisor processes, and related program operations.

Explore Case Management →

Separate review layer

Need to review records from a system you must keep?

Use Documentation Intelligence to discuss a bounded PDF review workflow while retaining the source system.

Read documentation review resources →

Frequently asked questions

What is Documentation Intelligence?

Documentation Intelligence is One Care Portal's human-reviewed documentation QA module for manually uploaded PDFs and selected configurable program criteria.

Does it replace our EHR, state system, or case-management platform?

No. It is designed as a separate review layer while the existing source system remains authoritative.

What file type is supported in the validation workflow?

The validation workflow is scoped to manually uploaded PDFs.

What are the current validation limits?

Uploads are PDF only, processed individually, and limited to 20 MB per PDF. AI-provided evidence text includes a cited page for human verification. OCR is not guaranteed; criteria are organization-configured; no built-in regulatory library, source-system integration, customer usage metering, or public pricing is represented.

Does a flag determine noncompliance, fraud, billability, clinical adequacy, or legal sufficiency?

No. Flags are possible findings that require human verification and disposition.

Who makes the final decision?

Authorized human reviewers inspect source evidence and record the final disposition.

Which decisions can reviewers record?

Finding dispositions are confirm, dismiss, or resolve. Document decisions are approve, return, or escalate.

Is Documentation Intelligence currently available?

One Care Portal is validating buyer workflows and product fit. Discuss your workflow with the team; this page does not represent production availability.

Should we send records before a workflow discussion?

No. Do not send PHI, service-recipient names, clinical details, or records through marketing forms or the booking flow.

Product validation

Map your current review process before discussing product fit

Tell us which source system you must keep, which PDF records your authorized team reviews, and how criteria and dispositions work today. Do not include PHI or records.