Removed alerts for mismatch between visit date and screening date

Site users no longer receive automatic alerts when the screening visit date and the actual screening event date do not match.

Previously, as per product design, site users were alerted whenever a subject was screened on a date different than the date entered for the screening visit. This is not relevant for some studies and sometimes leads to confusion for site users. For example, when a site user specified a screening visit's date, but then proceeded to actually screen the subject the next day.

Starting with this release, this automatic alert is no longer displayed for this particular use case. In case your study requires this type of alert, you can set up a custom rule to either send notifications or raise queries when this screening visit date mismatch occurs. While the previous visit date mismatch alert was only visible for the user performing the screening action, custom rules have the additional benefit that they can reach multiple users. Rules that send notifications allow multiple email addresses and, in the case of queries, they are visible for all users with the appropriate permissions or roles.

If you decide on using custom rules to alert site users of the mismatch between a screening visit's date and the actual screening date, you may want to review The Subject object documentation. The Subject Object was introduced in Oracle Clinical One Platform 24.1 to access data not collected in forms, such as the screening date.

Note:

Remember that rules run at the time data is submitted. So, for these cases, it is recommended that the rule you configure targets or references data entered in a visit occurring after the screening visit.

You can find additional information on the Subject Object and how to create different types of custom rules in the Rules Developer Guide.

Parent topic: User experience