Professional Documents
Culture Documents
Olympus AR Workflow Module 2.0 Business Requirements Document
Olympus AR Workflow Module 2.0 Business Requirements Document
0 AR Workflow Management
Definition:
User Role and management role will be linked with Olympus 1.0
Screen-1 AR upload
Templates and Data base
Manual Upload Template (AMD, MEDISOFT, CR) AR Report output Raw Files.
All the Raw file headers will be retained based on the projects.
Screen-1 AR Upload
Main Screen
1 BLR FFN
2 BLR CAN
3 BLR PIL
4 BLR YCS NY
5 BLR YCS NJ
11 BLR OIWK
1
12 BLR PFHC
13 BLR AMSU
14 BLR HBABA
15 BLR QER
16 BLR CEC
17 BLR WESCT
18 BLR RTRUST
19 BLR CBCT
20 BLR AC 14
21 BLR ALS
22 BLR APC
23 BLR SSAC
24 BLR FBMH
25 BLR RICFA
26 CJB RSS
27 CJB KMN
28 CJB SOPED
29 CJB TBC
30 CJB PAC
31 CJB ARETE
32 CJB RCS
33 CJB ACT
35 CJB AWM4
36 CJB DR. A
37 CJB IMA
38 CJB CRL
39 CJB MMTX
40 CJB CND
41 CJB WFLD
42 CJB Azul
43 CJB T-WORKS
44 CJB BSP
45 CJB ROSPT
46 BLR Pulse
Upload File- Browse the Local folders/ Directories and select for upload.
Logic-
Validated mandatory fields are present in the file which is unique to the client – Respective managers should provide this at the time of Account set-up.
Validate the Project name between Input file and Selected Project in application.
Validate the Format structure for all the mandatory fields.
Required fields - Insurance type, primary, secondary, tertiary, In network, out of network
To set the file unique to the client – create drop down, to do one time set-up.
Drop down1 – Count of Headers
Drop down2 – Content of headers
Drop down3 – header1, 2, 3, 4,5
Drop down4 - content1,2,3,4,5
2
Upload Supporting File formats.
Clicking on Save should show the records in Table and perform existing rule and exclusions before push the claims into AR
assignments tab.
Need to display all the Columns set for the receptive projects.
Each Column should have respective filed Search, Sort option, Filters (Multiple Selection Filters with Check box) within the table.
Show entries.
Upload All records from input file nothing to be excluded or removed.
All the records need to be saved in the database before exclusion.
Should create Column and headers specific project name and should be dynamic.
Multiple file upload option to be provided for all projects.
Need to update the Project name in the AR report. It needs to be validated with “Project name” selection while uploading in Olympus.
Need to add the date and time stamp in the report after uploading (Need to Automate in Olympus)
3
Screen-2 Exclusions
Exclusion Tab
UI Screen to push the data (list of accounts) to excluding from AR assignment screen and from AR work queue.
Will be uploading the exclusion reports file based and exclude from the database according to the rule set for each.
Function -click on view denial report should open View denials screen.
Update the logic to create a denial queue as a separate queue do not map to Denial to AR assignment to exclude worked denials
B. Select user Drop down - Logic- Should show the list of users with skill mapped to the project.
C. Assign button – Logic Clicking on Assign should assign the list of selected account from table to the user selected in Select user drop down.
4
4. Capture denials.
Function -click on Capture denial report should open Capture denial screen.
Manual entry table Grid to manual input data. (Input fields/columns to be provided by ops)
System should auto group the denials based on the CARC/RARC codes.
Steve to provide the CARC/RARC code list and category and subcategory to match,
Enable the option for agent to change the category and subcategory at the time of work.
D. Close/Cancel button.
Should prompt the confirmation screen.
Clear the grids and close or cancel (back to Create denials screen with no changes).
Clicking on Global issues report should open the rules control screen.
A. Close/Cancel button.
Should prompt the confirmation screen.
Clear the grids and close or cancel (back to Create denials screen with no changes).
B. Click on save.
Should expand the new grid below.
Logic- Based on the combinations of the field selections list to be should show list of account from AR assignment and AR work queue in the below table.
Logic – If duplicate rule created or exist, user should get a prompt.
C. Confirm and send for Managers approval. (New button to be added in below grid)
Logic- Rule combination will be sent for manger approval.
D. Close/Cancel button.
Should prompt the confirmation screen and back to grid with no changes.
E. Tickler date.
Once the date is set for the rule created and approved, Accounts related to rule will be behind the screen.
Once date is met notification should be sent and accounts shall move to AR assignment with the notes stating account are in Global issue.
View created rules (Screen to show the created rules and status)
Logics-
Approve, Edit, and delete button to be provided in view rule screen for the rules created.
Only managers will have access to approve and create and save a rule.
No approval required for Supervisor-2 Created rules.
Only supervisor-1 and supervisor-2 can create a rule.
Any Edited and deleted should be again sent for manger approval.
Based on primary and secondary logic.
If the grid selected is primary - Last billed should never show date less than 30 days and should not have option to enter.
If the grid selected is secondary - Last billed should never show date less than 45 days and should not have option to enter.
F. Approve Button
Once manger Approve the Rules –
Logic- Based on the combinations of the filed selections in the RULE Accounts should be excluded from AR assignment and AR work queue in the
below table.
If the rule is approved for editing, related accounts to the rule should be revalidated and related accounts changes to be applied.
If the rule is approved for deleted, related accounts to the rule should brought back to the assignment.
Applied rule and the changes should be shown on the supervisor screen.
G. Edit button.
Should allow team lead and managers/Supervisor to edit the rule set.
All the changes should be sent to supervisor-2 approval.
H. Delete
Rule needs to be removed from screen (need to maintain internal logs)
All the changes should be sent to supervisor-2 supervisor approval.
7. Client Exception report (Discarded) as we will link the tasking tool to apply the same logic.
Client exception needs to be removed as we are already moving the account from AR queue and AR assignment to the client exception
bucket through creating task.
Create task will be converted to TASK and moved to supervisor-1 approval bucket (create approval bucket)
Once Supervisor-1 approves account will be moved to client buket
Other bucket/Department task will show in the respective bucket (coding/supervisor-1/posting) in the AR assignment
to send reminder.
6
Dr J signed off the requirements updated till this page-1 st phase
now complete document is signed off 2nd phase
Clicking on Rules hub should show the option to select Create rules or mange rule.
List of fields to shown - ( All the fields should be Multiple select option enabled (Steve Kennedy)
I. Close/Cancel button.
Should prompt the confirmation screen.
Clear the grids and close or cancel (back to Create denials screen with no changes).
J. Click on save.
Should expand the new grid below.
Logic-
DOS- When Dos is selected less than 30days needs show pop warning and confirmation should send for manager approval.
Based on the combinations of the filed selections list to be should show list of account from AR assignment and AR work queue in the below table.
Color code for account based on TFL Selected.
TFL Logic- Counts (TFL date <>= Todays date)
IF TFL Greater 30 days and less than 60-day amber color based on dos
Lesser than 30 days will be red color based on dos.
K. Confirm and send for approval. (New button to be added in below grid)
Logic- Rule combination will be sent for manger approval.
L. Close/Cancel button.
Should prompt the confirmation screen and back to grid with no changes.
M. Tickler date.
Logic-
Once the date is set for the rule created and approved, Accounts related to rule will be behind the screen.
Once date is met notification should be sent and accounts to move to AR assignment with the notes stating account were in global issues
View created rules (Screen to show the created rules and status)
7
Logics-
Approve, Edit, and delete button to be provided in view rule screen for the rules created.
Only managers will have access to approve and create and save a rule.
No approval required for Manger Created rules.
Only Tl and manager can create a rule.
Any Edited and deleted should be again sent for manger approval.
Based on primary and secondary logic.
If the payer type selected is primary - Last billed should never show date less than 30 days and should not have option to enter.
If the payer type selected is secondary - Last billed should never show date less than 45 days and should not have option to enter.
N. Approve Button
Once manger Approve the Rules –
Logic- Based on the combinations of the filed selections in the RULE Accounts should be excluded from AR assignment and AR work queue in the
below table.
Color code for account based on TFL Selected.
TFL Logic- Counts (TFL date <>= Todays date)
IF TFL Greater 30 days and less than 60-day amber color based on dos
Lesser than 30 days will be red color based on dos.
If the rule is approved for editing, related accounts to the rule should be revalidated and related accounts changes to be applied.
If the rule is approved for deleted, related accounts to the rule should brought back to the assignment.
Applied rule and the changes should be shown on the supervisor screen.
O. Edit button.
Should allow team lead and managers to edit the rule set.
P. Delete button.
Rule needs to be removed from screen (need to maintain internal logs)
Note – Once manager approves the rule, system should show the confirmation of the set rules are applied. (Steve Kennedy)
LOGIC-
A. Once all the exclusion, rule set and exception tracker accounts are excluded, Remaining accounts will be shown here in this screen list.
B. TL should be able to apply the filter and select multiple accounts or all accounts from the table.
8
Claims status output – Response from Availity input. (Steve Kennedy)
Following claims status should be excluded from the AR assignment
Note: Need to prioritize the phase of Auto Run and Run Now of claims status.
Bulk upload
Logic-
A. Will be not linking any 2.0 AR module features.
B. Only TL and above uploads external input file and gets the claims status from Availity.
Output:
Successful verification – apply the status to the AR assignment and update the notes.
Missing pVerify Id –
Allocate to level 1 user for manual verification
Notify the supervisor to work with pVerify team to add the missing payer.
Existing AR accounts – Select and verify the eligibility and repeat the output process mentioned below.
Successful verification – apply the status to the AR assignment and update the notes.
Missing pVerify Id –
Allocate to level 1 user for manual verification
Notify the supervisor to work with pVerify team to add the missing payer.
Insurance Plane Financial Filing Limit Appeal limit from First Insurance Phone
Name Name Class State from DOS denial Number
9
SCREEN – 7 Excluded queue
Show all the list of the excluded data with all the field at the account level. Along with the titles of excluded reasons with time stamp
All the duplicate entries of previous upload will be saved in one screen for a reference.
SCREEN – 9 AR Assignment
Save Plan
Allocation of Accounts by Skill/competency mapping (Mapping to be provided) Need to add a dropdown to select a skill, based on the skill selected users list
should be shown to assign.
Combination for callable and non-callable by mapping the aging categories will be shared
Should link the claims in tasking and AR Assignment to view the status of the task and enable access to pull back the task as required with Time stamp.
10
Role assignment
11