Project Settings

Sam Zakrzewski

Modified on: Wed, 17 Jul, 2024 at 2:07 PM

TABLE OF CONTENTS

Project Settings Page Overview
Project Settings Page Overview - Chart Lake

Project Settings Page Overview

Project Name: Edit Project Name
Project Status: This toggle will allow you to set a project to Inactive or Active
Project Owner: Edit Project owner anytime
Reveleer Project Contact(s): This allows a user to configure an email to send notifications to once chases have been added via data load to a project. Multiple emails can be added via a comma separated list.
Dates: These fields can be updated but are for informational purposes only
GetNext for Retrieval: This toggle enables automatic retrieval assignment
GetNext for Clinical: This toggle enables automatic clinical assignment
Dual Role Assignment: If you have employees who perform both Retrieval and Clinical you can set them up for dual role. If enabled, the chase will remain assigned to that user.
Pursuit Approvals: This lets you determine if Pursuits require a Manager/Admin to approve before a chase is created.
New Chase Creation: This lets you determine if Documents can be added to chases that are in overread and beyond.
Inactive Chases: This lets you determine if Documents can be added from document Intake to chases that are Inactive.
Document QA settings: Here you can define the QA percentage you would like reviewed for accuracy for each retrieval method listed. Retrieval Methods are: Fax, Mail, EMR, Field Tech, Provider, Bulk Upload, FTP, Intake, MRR Upload, Pend Upload, PSR Upload, SMRC, Portal Upload, and 3^rd Party Upload.
Max Pages: This can be used to flag charts that have a large number of pages. If chase exceeds max, the chase will go to Doc QA for review, prior to going to Data Entry.

Doc QA Method Definitions of Upload Methods

Note: It's specific to the upload method, not the retrieval method. For example I could pull from an EMR but actually upload the charts via bulk upload, dropping in an sftp etc. The EMR upload is a specific place in the system that qualifies. Bulk upload feature also allows users to specify the original retrieval method which will have the document qualify as coming from that source.

Actual Retrieval Method/Upload Method	Description	In Use?
Fax	Document was uploaded to platform via fax. Documents can be faxed to the Reveleer platform that will route through a folder and upload to the platform with the source being fax or upload via bulk action with an original retrieval source of fax.	Yes
Mail	Document was uploaded to platform via mail. Users can scan in documents to a specific folder configured for mail ingestion or upload via bulk action with an original retrieval source of mail.	Yes
EMR	Document was uploaded to platform via EMR upload. User can upload documents directly to chases via the upload feature from within an EMR AID or upload via bulk action with an original retrieval source of EMR.	Yes
Fieldtech	Document was uploaded to platform via FT upload. User can upload documents directly to chases via the upload feature from within a FT AID or upload via bulk action with an original retrieval source of FT.	Yes
Provider	Document was uploaded to platform via provider gateway chart drop (portal accessed with a pin); shows up as provider email upload in reporting.	Yes
Bulk Upload	Document was uploaded to platform via bulk upload with selecting source of bulk upload.	Yes
FTP	Document was uploaded to platform via sftp. Example would be files being dropped into an SFTP configured for chart ingestion.	Yes
Intake	Document was uploaded to platform via an sftp configured to send documents to intake and not use routing bot. This results in the source being doc intake. This can still be configured but currently isn't being used and is not recommended. It will route all charts that aren't named with a naming convention to intake to be worked manually vs using the routing bot. Essentially same results as if routing bot was off for a SO.	Typically not used anywhere, but still can be configured for a folder set up to ingest charts
MRR Upload	Document was uploaded to platform via MRR Upload. User can upload documents directly to chases via the upload feature from within the chase itself or upload via bulk action with an original retrieval source of MRR Upload.	Yes
Pend Upload	Document was uploaded to platform via Pend Upload. User can upload documents directly to chases via the upload feature from within a pend associated with the chase or upload via bulk action with an original retrieval source of Pend Upload.	Yes
PSR Upload	Document was uploaded to platform via PSR Upload. User can upload documents directly to chases via the upload feature from within a PSR AID or upload via bulk action with an original retrieval source of PSR.	Yes
SMRC	Deprecated; this was an independent console used by Field techs to upload documents. Now documents can be uploaded within platform and this is no longer used.	Retired
Portal Upload	Not in use; referred to an older application that was used to upload charts that is no longer supported.	Retired, although still can be selected in bulk upload
3rd Party Upload	Document was uploaded to platform via 3rd party upload. User can upload documents directly to chases via the upload feature from within a 3rd party AID or upload via bulk action with an original retrieval source of 3rd party.	Yes

Note:

Annotations are visible in audit packages but not in the version of the records that Reveleer sends at the end of the project.

Project Settings Tab is the same for all project types: HEDIS, Risk, IVA, Address Verification

Member Centric Projects Only: There is no Approval Center or MRQA sampling.