Quandri Knowledge Hub
Testing
This article is broken into 5 sections.
- Pre-Work
- Assigning Daily Activities
- Running in Read-Only
- Result Reviewing Best Practices
- Deployment
Pre-Work
Please review your configuration and if you have any questions about updating your configuration, don’t hesitate to reach out to your point of contact at Quandri.
Assigning Activities
The first step is to assign your download of daily activities to Quandri in Epic. This can be done in the following steps:
- In Epic, navigate to the Configure
- Under the Activity tab, select Codes
- Click Basic Settings
- Find the activity code that you would like Quandri to process
- Change the Owner type to Specific Person
- Change the Specific owner to the Quandri’s user code. Make sure to set up Quandri's user code as an Employee in Epic.
After you complete this workflow, your daily activities should be assigned to Quandri.
Note: It may take Epic a few days to enable these changes. During testing, Quandri will look at each activity, tell you what it would have done had it been in production, and reassign it to who you specified in your configuration.
We advise assigning the complete download of daily activities to Quandri rather than a batch of outdated activities to ensure that Quandri is trained on the exact data it will encounter once it goes into production.
Running in Read-Only
During testing, Quandri will run in read-only mode. In this mode, Quandri will:
- Look at each of the activities on the homepage of Epic
- Download the attachments
- Mark what it would rename the document in a spreadsheet and;
- Reassign it to your team.
At the end of Quandri's run, you will receive an email with the daily spreadsheet that displays the actions it would have taken with each of your activities. We recommend that you dedicate 1 hour per day to reviewing the results of your eDoc Management's run. You can utilize this mode to tweak your configuration to get it working exactly as you’d like. You can also report any inaccuracies to the Quandri team to diagnose.
Results Reviewing Best Practices
On the spreadsheet provided, Quandri will indicate if each activity was a Success or an Error. An Error indicates that Quandri either was unable to classify the document type, or it had trouble extracting a specific data point.
For example:
Lookup Code |
Status |
Activity Code |
Carrier |
Doc Type |
Old Description |
New Description |
Error Message |
ROBELEO-01 |
Success |
EREN |
SGI |
Renewal |
… |
… |
|
JOSHMAR-01 |
Error |
ENEW |
… |
Failed to identify document type |
To easily review the activities and provide feedback to Quandri, add a new column on the right side of the table labeled "Review".
For the Errors, please indicate in that column either the document type or the data point that Quandri was unable to extract (for example, if the Error Message says “Failure to extract Policy Type”, please indicate what the correct Policy Type is in the Review column).
For the Successes, it’s a good idea to go through a handful of activities to ensure the bot is renaming the document the way you would like. If you would like to make changes to your configuration, you can do that on the Quandri Platform. If there are any successes that you determine are incorrect (ie, your configuration states that you’d like Date of Loss pulled for Claims, and Quandri is pulling the Policy Effective Date), please indicate that in the Review column.
It is not essential to go through every single activity from the run. A handful of successes and a handful of errors will be enough to provide Quandri with feedback to build in if needed.
Deployment
Once you have run your cababilty in the testing phase enough to get comfortable with it, you can turn read only mode off and deploy your eDoc Management capabilty.
Quandri will still continue weekly check-ins with you and provide the same level of support after you deploy, the only difference is that Quandri is making real changes in your environment and adding value to your business.
Need more help?
Reach out to Quandri Support with your query if you can't find what you are looking for in our Knowledge Hub.