Comparison of Ripple and Castellum - Might be helpful for us
-
Global Custom Variables -
Ripple: Variables that appear on a subject’s “profile” in the registry as well as any other study the subject is added to
-
Any custom variables not marked Global will only be visible in the study in which they were created.
-
Blinded Custom Variables -
Ripple: Variables will only be visible to users with certain permissions and are only visible on the study profile card
-
Global Blinded variable is never visible in the Registry
-
Study Setup – Blinded Variables -
Ripple: Blind users from specific custom variables; users with “Leader” status will not see the value for that variable in any participant profile but those with “Study Admin” role will
-
Could be helpful for us to fulfil GDPR requirements more effectively
-
Add an Existing Global Variable button -
Ripple: Add an existing global variable created in a different study to your study
-
Subject Consent Log -
Ripple: In a subject's profile, there is a tab titled Consent Log. This log is used to track the occurrences in a study where consent for procedures is obtained from the subject, a parent/guardian, or others in relation to this subject
-
Subject Consent Log -
Ripple: Should be in a subject's profile
-
Log can be used to track the occurrences in a study where consent for procedures is obtained from the subject, a parent/guardian, or others in relation to this subject
-
Adding a New Consent Record -
Ripple: By clicking the Consent Log button, one can enter a new contact and following information: Consent Title, Consent Date, Consent Type, Version, Consented by (Individual who provided consent), Expiration, Attachments, any additional comments
-
Previous consent records will be displayed
-
Subject Contact Log -
Castellum: Last (un)successful contacts are shown in the Recruitment Dashboard
-
Ripple: Contact Logs that track the occurrence of every contact with the subject, a parent/guardian, or others in relation to this subject
-
Entering new contacts directly in the subject's profile
-
Commentary function -
Ripple: Comments can be made within Tasks, Recruitment Sources and Strategies, Potential Participants and Enrolled Participants
-
E.g.: Pin Comments will pin the comment to the top of the comment list
-
Notify-function: email alert about the comment will be send to the team
-
Global-function: Making a comment gobal will keep it visible in every study the subject is in (if "show global comments" checkbox is checked, global comments in this study will be displayed)
-
My Account Overview -
Ripple: Each user has a personal My Account page to view their account information and settings, as well as their study roles and email preferences
-
Divided into: Personal Details (Red), Studies and Roles (Purple), Logins and Account Creation (Green)
-
Castellum: Personal details might be interesting for us (possible function: change login password)
-
Studies and Roles is interesting for us (possible function: show permissions and roles categorized by studies)
-
Logins and Account Creation: shows when the account was originally created + information about all recent logins
-
This includes date, time, IP address, and browser information; I think it is not practicable for us, since we do not want to record working times
-
Study Setup - Study Details -
Ripple: Space to record important information relevant to your study to create documents
-
Castellum: The goal is not to save research data; but this function might be useful to update relevant information for the recruiter (e.g. study encompasses not only MRT any more but also FRMI)
-
Ripple: Study Short Name (limited to 15 characters and is used throughout Ripple to refer to studies)
-
Study Name (full name of the study; field is not character limited)
-
Castellum: Would it make sense to include such a distinction in Castellum as well?
-
Ripple: Active Recruitment Start/End dates
-
Castellum: We already have “start study” but do we also indicate the end date for recruitment? That might be helpful to monitor how the recruiters/telephone studio are performing + if we are at risk of not meeting recruitment targets
-
Study Setup - Events -
Ripple: Calculates Follow Ups on his own
-
Events can be created and related to others
-
Appointment tracking (All events are displayed in the Enrolled Participants Dashboard; color-coded: Orange = expected appointments, Blue = appointments to be scheduled, Black = completed appointments, Red = appointments that are past due)
-
Castellum: Setting up date and time to call back a subject
-
Would it be helpful for us to make Castellum reminding recruiters when they have to call a subject for a follow up study/provide appointment tracking?
-
Direct Emailing -
Ripple: Sending individual, one-way email communications to participants for event reminders and information about studies
-
Different options: Contact (marking email as the "Date of Last Contact" for this participant), Pin Email (email is pinned to the top of the email communications page), Notify (sending email notification to the team), Global (Save email log to global registry data)
-
All communications are saved in the Email Log to track past communications (includes the date the email was sent, subject and message, and the recipients)
-
Subject will receive email from “no-reply@ripplescience.com” + will be unable to reply to email
-
Such a function might easy the work of our recruiters