Process Steps - Process Steps - The steps for the Intelligent Correspondence for Revenue Cycle ( ICRC ) solution outlined in the process diagram are expanded in the following table. - Content Innovation Cloud - OnBase - Other - Intelligent Correspondence for Revenue Cycle - Other/Intelligent-Correspondence-for-Revenue-Cycle/2.0/Intelligent-Correspondence-for-Revenue-Cycle/Overview/Solution-Design/Process-Steps - 2.0 - 2.0

Intelligent Correspondence for Revenue Cycle

Platform
Other
Product
Intelligent Correspondence for Revenue Cycle
Release
2.0
License
ft:lastPublication
2026-06-17T22:37:10.232000
ft:locale
en-US

The steps for the Intelligent Correspondence for Revenue Cycle (ICRC) solution outlined in the process diagram are expanded in the following table.

Step Description
Capture Integration

ICRC connects to OnBase, enabling documents to be captured using any OnBase capture tool that can place documents in a Capture Process Designer (CPD) enabled scan queue.

Separation/Classification
  • In the separation process, ICRC uses documents' contents to separate documents within a batch.
  • In the classification process, ICRC uses a document's content to identify and assign the type of business correspondence.
  • If ICRC cannot automatically classify the document or is unable to meet the configured confidence level, it sends the document to a user process where a human user manually assigns the classification.
  • Users can delete and reorder pages within a document, or split and merge documents within a batch.
  • Users can flag/route documents for review by another user, such as a manager or coworker.
Extraction
  • After classification, ICRC attempts to extract the data needed to associate the document with a specific patient account, guarantor, or invoice in the repository. Each document type has a required set of data that is needed to pass the document on to the repository.
  • If ICRC cannot apply all the required data, the document is sent to a user process where a human user manually assigns the data.
  • Users can flag/route documents for review by another user, such as a manager or coworker.
Page Segmentation
  • Whenever ICRC detects a multi-patient document, it extracts the necessary metadata for each patient account.
  • ICRC creates a copy of the document for each patient account detected in the multi-patient document.
  • A user reviews the copy of the document for each patient. The user can manually remove sections of the document to redact unwanted patient data as needed.
Assistance Needed
  • Documents flagged for assistance during extraction or classification are routed to an Assistance Needed task list.
  • The user addressing an Assistance Needed task has access to all features available in the original review task. The user also can do the following:

    • View comments regarding the flagged document.
    • Flag the document for rejection and select a customer-configured rejection reason, such as Poor quality or Non-correspondence document. Documents flagged for rejections are sent to OnBase as the Correspondence Rejected Documents Document Type
Quality Review
  • Documents can be routed to an optional quality review process, where a human user manually reviews documents for accuracy.
  • Administrators can configure ICRC to route all documents or a specified percentage to quality review.
  • Quality review users can flag/route documents for review by another user, such as a manager or coworker.
Release to OnBase Repository

Documents and their metadata are released to OnBase.