TABLE OF CONTENTS
Document Intake
All documents that arrive on the Reveleer platform are processed. Before moving to the Intake module, all documents are first reviewed through a chart routing engine (internally referred to as ‘the bot’). The bot will match, and route based on project settings. Any document for which the bot cannot confidently match or if the entire document is to be ignored will revert to the Intake module for manual review.
It is important to note that Intake is the repository for documents on the platform.
- Active: all documents that have pages that need to be associated or approved.
- Archive: all documents that have been processed (approved, denied/removed).
- Processing: all documents in process of ingestion before the can be worked in intake.
Suggested Document Routing Workflow
(Right click to open in new browser window)
Document Routing
1. Document Arrives into the Reveleer Platform: Documents can be ingested in a number of ways including fax, sFTP, bulk upload, Provider Gateway
2. Chase ID = File Name, Chase Selected at upload?: If a document is named for a single chase ID or if a Chase ID is selected at upload, the document will bypass the chart routing bot and Document Intake
3. DECISION: Bot Processing: The Chart Routing bot will assess documents based on Service Organization settings
Intake Module
4. Intake Manual Review: The document will become active in the Intake Module for manual review
Document QA
5. DECISION: Included in Sampling %?: If project settings dictate the use of Document QA and the chase is selected as part of the review percentage, pages associated to the chase will be available for review in the Document QA Module
6. Document QA: Documents will arrive in QA based on sampling percentage, through move backs from Clinical Data Entry, and if the chase exceeds the page count threshold determined by project settings
7. Data Entry: Once a chase has fully committed pages associated, the pages will be present in Data Entry
Document Intake Module
Within the Intake Module: all documents will be manually reviewed to determine what type of page(s) it contains to parse the document and route its contents to the correct Module. The classification of pages are as follows: Medical Records, Invoices, Pends, and Unusable Pages. Once the User makes the determinations, qualifying page(s) must be assigned to the appropriate Chase. To this end, the User will match Patient name; Patient date of birth; Provider; Gap. Upon completion of the review, the User will Submit, Hold, or Remove the document.
Document Intake Workflow
(Right click to open in new browser window)
Assignment
1. User will work by Assignment or Get Next: A User begins with a document to be worked
2. DECISION: Working Pages: Working pages will consist of all pages that are not committed to a chase and need review
3. Committed Pages by BOT: Committed Pages by the Chart Routing Bot will show all pages that have been committed to a chase in full confidence
Manual Parcing
4. Ignore this Page: All Unusable pages can be ignored through Ignore this Page. Unusable pages include; copies of the original medical record request that contain no provider notes, blank pages, cover sheets with no provider notes, chase or invoice that do not associate to an active project
5. The Page is Part of a Chase: Specific pages can be directly associated to an open, active chase
6. This Page is Part of an Invoice: Pages that consist of itemized bills, notes regarding payments due for providing or processing a medical record. If an invoice includes multiple chases, only one needs to be associated as Invoices will be parced in the Invoicing Module, not in the Intake Module
7. This Page is Part of a Pend: Page with notes from providers or vendors where the request cannot be satisfactorily fulfulled
Selection:
8. Working Pages: User has identified the applicable chase(s) and after all pages are identified, will commit all pages
9. Committed Pages: Committed Pages by the Chart Routing Bot and User
Completing Document
10, Remove: Full document is to be removed and moved to archive
11. Hold: Full document is to be placed on hold, all in committed status will maintain attached to chase(s)
12. Submit: All pages associations are confirmed and/or committed and will be processed
Document Intake Statues, Hold Buckets
Document State Group are document statuses. They are very specific to Intake, here are what they are:
| Document State Group | Status | Description |
| Active | Document Not Matched to Chase | New document that needs to be processed. |
| Complete / DocumentIntakeComplete | Document Intake Completed | Document that has been fully processed. |
| Removed / DocumentIntakeCancel | Unable to Find Any Matching Chase, Remove From Active List | Documents that have been removed because they contain nothing that could be used for record collection. |
| Processing | Various | Document has been loaded and is being processed by System
|
| On Hold | Various | Document has some block to completion and is being reviewed
|