Castor eConsent Release Notes 2025.1.x.x
Table of Contents
Major Release eConsent 2025.1.0.0
Release dates
EU server: February 5, 6 pm CET / 12 pm ET
US server: February 6, 9 am CET / 3 am ET
New features and enhancements
- In this release our main focus was upgrading our infrastructure. These technical improvements are not necessarily visible to the user, but they are needed to ensure a reliable user experience for the user.
- We have improved the registration flow for participants. The fields are now in a more logical order and for US participants it is now easier to select a State/Province/Region, which ensures a smoother experience when filling in your personal details.
Maintenance release 2025.1.1.0
Release date
EU & US servers: February 24, 9 AM CET / 3 AM ET
New features and enhancements
- eConsent now supports Italian and French for all participant-facing elements.
- Password rotation can now be configured per study by Castor. Users will be forced to reset their password after a configurable amount of days. The two most recent passwords can not be re-used.
- Validation for US zip codes has been added on the participant detail page that is part of the onboarding flow for participants.
Maintenance release 2025.1.2.0
Release date
EU & US servers: March 7, 9 AM CET / 3 AM ET
New features and enhancements
- Various technical improvements to help our Support team assist customers more efficiently.
Minor release 2025.1.3.0
Release date
EU & US servers: March 24, 9 AM CET / 3 AM ET
New features and enhancements
Passwordless authentication
To enhance security and usability, we are introducing a passwordless login experience for participants in our eConsent product. This change applies only to newly created studies and replaces traditional passwords with one-time passwords (OTP) sent via email.
Email-Based OTP Authentication - Instead of entering a password, participants will receive a one-time password (OTP) via email to authenticate/
Simplified Registration and Login Flow - Participants only need to enter their first and last name during registration. An OTP is then sent to their email for account activation. Future logins will also require an OTP for authentication.
Effortless Signing of Documents - An OTP is required when signing a document. When a participant initiates a signature, the system automatically sends an OTP to their email. Once authenticated, the signature is confirmed.
No More Forgotten Passwords - Because an OTP is generated for each login, participants no longer need to remember passwords or go through a password reset process.
Other enhancements
- It is now possible to adjust the text of the participant questions when editing a draft ICF.
System defect fixes
- We fixed an issue where, after Castor Support would change the email address of a LAR user, the system would log an ATE which specified that a participants' email address was changed instead of that of a LAR.
Maintenance release 2025.1.4.0
Release date
EU & US servers: April 22nd, 9 AM CET / 3 AM ET
New features and enhancements
- The Participant ID will now be shown in the PDF version of a form. This is only applied to newly created forms. Existing forms are not affected.
- Resolved an issue where some ICF forms had minor tickbox-text misalignment
- Resolved issues with wording and presentation of authentication modals for users of OTP/SSO
Hotfix release 2025.1.4.1
Release date
EU & US servers: April 28th, 3 PM CET / 9 AM ET
System defect fixes
- Fixed an issue where the content would be cut off in ICFs with a large amount of text.
- ATE which specified that a participants' email address was changed instead of that of a LAR.
Maintenance release 2025.1.5.0
Release date
EU & US servers: May 23rd, 9 AM CET / 3 AM ET
New features and enhancements
- We fixed an issue where, after signing a document, the document overview would not indicate that the document was signed.
- We fixed an issue where the 'Name' column width in the Consent form overview could not be adjusted.
- Resolved an issue where it was possible for duplicate participant IDs to be created in CDMS as in eConsent, due to eConsent not being prompted to trigger a retry/check. Resolved by storing the Participant ID created in CDMS in a temporary storage in eConsent meaning when a retry happens, eConsent will first do a lookup in the temporary storage before executing another creation in CDMS
Minor release 2025.1.6.0
Release date (tentative)
EU & US servers: 1st July, 9 AM CET / 3 AM ET
New features and enhancements
- Castor's new browser and operating system policy will be applied across the eConsent platform - the full details of which are available in a dedicated page here
- All clinicians will need to comply with the new policy when using the eConsent platform, regardless of their study
- Participants on existing studies (those live prior to the release of 2025.2.0.0) will not have the policy applied by default. All participants on newly created studies will have the policy applied, and existing studies can migrate on request.
- Resolved an issue where removing an ICF assigned to a participant was generating errors
- Implemented underlying technical infrastructure changes to improve maintainability and performance