Screen Failures - New functionality - path for every SF is paid and no SF is paid

Modified on Thu, 04 Apr 2024 at 10:26 AM

To manage Screen Failures you need to have apprioprate permissions:

You have two paths to hold Screen Failures accountable:

1. Any Screen Failures payable or none payable

2. An individual budget for each Screen Failure

To account for Screen Failure you must first add a budget to the clinical trial

Add a new budget version by clicking "+" icon and add neccessary information about version name and validation. Click "Create". After creating you will have an option to set up your budget.

Once you have created a version of the budget, click on the "Pencil" icon to enter the budget and be able to configure it.

Note that a new Screen Failures tab has appeared.

Choose the model in which you will account for SF, as indicated in your contract and click "Save".

In order to bill a patient as Screen Failure we need to have the visit closed and the patient's status set to Screen Failure

A patient with Screen Failure status will appear in a new Screen Failures tab visible from the study dashboard:

If you click on the three dots you will have details - information on the chosen billing model and history - when the SF was added and modified

You can expand the Screen Failure position and depending on the settlement model:

 - each SF paid you will see a quote for the visit from the price list

- no SF paid you will see costs and revenues equal to 0 for visits and procedures

When selecting finances, you have the option to filter by patient status, which includes SF status:

Click filter to find information you need.

Note: Until the invoice is assigned in our system, we can change the payment model Screen Failure

New - Screen Failure status is included in the reports

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select atleast one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article