Overread Percentage Configurations for Risk/IVA
We updated and consolidated our overread settings into two distinct buckets across OR1 and OR2:
1. Percentage of deficient chases.
2. Percentage of non-deficient chases.
Now within project configurations under the IVA/Risk settings tab, users will be able to dictate whether or not a certain percentage of both deficient and non-deficient chases land in OR1 and OR2 respectively. The default percentage of deficient chases that will land in Overread will be set a 100%. The default setting for non-deficient chases will be at 0%. There is also disclaimer text explaining that any deficient OR1 percentages set below 100% could result in some pursuits not getting created and invalid chases being sent to delivery.
Data Entry Checklist
We added a new feature called Data-Entry Checklist that will allow clients to host a customized checklist within their coding screens. Users will be required to fill out all components of the checklist before being able to submit coding results. We also included a validation reason dropdown that can be customized to display certain contextual information related to the effort that went in to completing the checklist.
Configuration
The checklist can be configured under a dedicated tab called "Data Entry Checklist" within project settings. Users will be able to pick specific coding screens they'd like the checklist to appear on (Abstraction/MRR, OR1, and OR2). Checklist labels can be configured via text inputs under the 'Data Entry Checklist items' section. The configuration for validation reasons will appear under 'Data Entry Checklist Results' where users can enter/edit specific text to be used as part of the checklist confirmation flow.
Data Entry Display
Once the Data Entry Checklist content has been saved within project configurations, it should appear on all applicable data entry screens when users perform abstraction/coding. 
Added provider column/filter to the PSR-Assignment Grid
As part of our ongoing effort to present more action-oriented information in our grids, we have added provider as a dedicated column within the PSR-Assignment grid. This will allow users to search and filter Addresses by certain providers.
Coverage Page selection prompt when generating pull lists for Provider Outreach
Previously, email and faxes were sent immediately when the "Fax" or "Email" buttons were clicked from within the Address Details page. Now, users will be prompted to review the details of the fax or email (Chase Count and Delivery Details) as well as be prompted to select the appropriate Cover Sheet to use for the fax or email.
Creating a New Chase from scratch
Managers or above now have the ability to Create a New Chase within the Reveleer platform.
Accessed via Chase Query, the user will be presented with a Create a New Chase wizard that will walk them through the process of creating a new Chase. They will be able to define the required attributes of the Chase, including: Chase Key, Measure, Member, Provider, and Address. The user will be allowed to search and select from existing Members, Providers, and Addresses within a Project. If certain elements are new or can't be found, users will be able to create them directly from the wizard. Upon completion of the process, the chase gets created instantly and is available to be worked within the Reveleer platform.
Project Configuration: Include in Get Next
Project administrators will now have a dedicated project configuration that determines whether or not a project will be included as part of the Get Next address and chase allocation/assignment. By default, all new and current projects will have the "Include in Get Next" checkbox checked on.
Provider Outreach: Email requests added to the Contact Attempt History grid
Now when users send out a medical records request via email, it will appear as a dedicated entry within the Contact Attempt History Grid.
Get Next Combo Buttons in Doc Intake
We expanded our Get Next assignment logic and functionality to apply to all possible document processing steps in Doc Intake. Now users can carry out submit, hold, and remove actions while also triggering a Get Next assignment. These options will be presented as combo buttons allowing users to either perform the base action or perform the intended action along with Get Next allocation.
Filter Retrieval/Clinical Grids by Pend ID
Users now have the ability to filter both the Retrieval and Clinical grids by Pend ID. When a user clicks on 'filter' from either the Retrieval or Clinical grid they will be presented with an input that allows them to enter a specific Pend ID.
Chart Viewer - View All Pages (Service Organization Config)
Previously we required users to view all pages of a document when reviewing charts in Document Intake and Document QA. We recently introduced a Service Organization setting that will allow account administrators to determine whether or not users will have to review all pages of a chart before being able to submit/progress to the next steps of document processing/medical record review.
Clinical Pends in Overread
We now have the ability to create a Clinical Pends from within the Overread module. The same functionality exists between Clinical Pends created in Overread1 and Overread2.