Contact Us

If you still have questions or prefer to get help directly from an agent, please submit a request.
We’ll get back to you as soon as possible.

Please fill out the contact form below and we will reply as soon as possible.

  • Contact Us
  • Home
  • CDMS
  • Castor CDMS Manual
  • Automation Engine

Test your automations

Contact Us

If you still have questions or prefer to get help directly from an agent, please submit a request.
We’ll get back to you as soon as possible.

Please fill out the contact form below and we will reply as soon as possible.

  • CDMS
    Castor CDMS Manual Castor CDMS Calculations Manual Frequently Asked Questions Articles for Data Managers Castor CDMS Compliance Release Documents
  • eConsent
    Castor eConsent Manual Castor eConsent Compliance Release Documents
  • SMS
    Castor SMS Manual Castor SMS Compliance Release Documents
  • Castor Connect
    Castor Connect Compliance Release Documents Castor Connect Manual Castor Connect - Participant Quick Start Guide
  • Helpdesk
    News Other Resources Castor products knowledge resources
  • Status page
  • Completing a Study
+ More

Table of Contents

Review your automations Example 1. When I update a field, add a query Example 2. When I update a field, show/hide form Example 3. When I update a field, show/hide visit Example 4. When I add an email address to a participant, create and send survey package

A guide to practice testing your automations and become familiar with the automation's behaviour. In order to complete this tutorial, you must have at least one existing automation. If you don't have an automation, try creating one!

Review your automations

First, it is important to review your automation in the Automation Overview, taking special note of the conditions that must be satisfied when the event occurs. Once you have done so and know the procedure you must follow to trigger your automation, continue to test your automation. 

If you are unsure how to determine the correct procedure, view the four examples below to get an idea. Examples will be provided based on the the event and the action associated with it. General conditions will be assigned to each case to exemplify how conditions fit within the layout of automations.

Note: For each example, it is ideal to check the audit trail as well to ensure that all of your actions are being properly recorded.

Example 1. When I update a field, add a query

Event: Field Value Updated.
Example condition: Study field value "weight" is greater than 120 kg.
Action: Add open query with the question "Are you sure?".

Testing forms:

  1. Navigate to the Participant tab.
  2. Either create a new test participant via the "Create a new participant" button or access a test participant.
  3. In data-entry, find the field "weight". Specify the answer to be greater than 120 kg (eg. 130 kg).
  4. Now, either wait a few seconds, or refresh the form containing the target field by navigating away from it, then returning to it.
  5. An open query appears on the "Weight" field. When you click on it, you can see the message "Are you sure?" appearing. This can also be viewed in the Monitoring tab.

Example 2. When I update a field, show/hide form

Event: Field Value Updated.
Example condition: Study field value "Can patient participate in the study" is equal to "No".
Action: Hide form "Measurements".
Note 1: This example uses a calculation field, meaning the fields used in the calculation must make the calculation equal the desired value.
Note 2: If you delete this automation, any form you have hidden using this automation will reappear.

Testing forms:

  1. Navigate to the Participants tab.
  2. Either create a new test participant via the "Create a new participant" button or access a test participant.
  3. In data-entry, find the field "Can patient participate in the study". Specify the answer no by:
    1. Set "Does the patient have example disease?" to "Yes".
    2. Set "Is patient older than 65" to "No".
    3. Set "Has the patient signed informed consent?" to "Yes".
  4. If you look at the form navigator, something should have changed. First, notice that the Measurements form has disappeared. Furthermore, the progress bar for the participant should adapt to reflect the smaller number of questions.

Example 3. When I update a field, show/hide visit

Event: Field Value Updated.
Action: Hide visit "Visit 1".
Example condition: Study field value "Can patient participate in the study" is equal to "No".
Note: This example uses a calculation field, meaning the fields used in the calculation must make the calculation equal the desired value.

Testing forms:

  1. Navigate to the Participants tab.
  2. Either create a new test participant via the "Create a new participant" button or access a test participant.
  3. In data-entry, find the field "Can patient participate in the study". Specify the answers:
    1. Set "Does the patient have example disease?" to "Yes".
    2. Set "Is patient older than 65" to "No".
    3. Set "Has the patient signed informed consent?" to "Yes".
  4. Viewing the form navigator, something should have changed. First, notice that the Visit 1 visit has disappeared. Furthermore, the Progress bar for the participant should adapt to reflect the smaller number of questions.
  5. Note: If you delete this automation, any visit you have hidden using this automation will reappear.

Example 4. When I add an email address to a participant, create and send survey package

Event: Email Address Added To Participant.
Example condition: Study field value "patient gender" is Male AND study field value "patient height" is greater than 1.95 meters.
Action: Create and send survey package "Survey for male participants taller than 1.95 meters"
Note 1: This example contains TWO conditions. Both conditions must be satisfied before the event tries to trigger the action.
Note 2: Currently this automation only works with newly added email addresses, meaning it will not trigger the automation when a participant with an existing email address gets an updated email address.

Testing forms:

  1. Navigate to the Participants tab.
  2. Either create a new test participant via the "Create a new participant" button or access a test participant that does not yet contain an email address.
  3. In data-entry, find the field "patient gender". Specify the patient is "Male" using the radio buttons.
  4. In data-entry, find the field "patient height". Specify the height as being greater than 1.95m (e.g. 1.96).
  5. Back in the Participants tab, click on the cogwheel for the participant you just edited. Select "Update email address" and fill in a test email address (e.g. your own).
  6. Navigate to either the Surveys tab in study management or the Surveys tab in the participant's data-entry view.
  7. Your specified survey should appear, planned or sent on the dates specified.

The above can also be done via importing (either importing email addresses or importing participants with conditions met and email addresses attached to them). This should be only tested with 2-3 participants to begin. As you become more comfortable with using you automation, you may begin using it in your live study!

enhance evaluate

Was this article helpful?

Yes
No
Give feedback about this article

Related Articles

  • Introduction to the Automation Engine
  • Create automations with the Automation Engine
  • Select an event for your automation
  • Select a condition for your automation
ISO 27001
FDA - 21 CFR part 11
ICH GCP compliant
HIPAA compliant
CDISC
ISO 9001
gdpr compliant

Products & Industries

  • Electronic Data Capture (EDC)
  • ePRO
  • eConsent
  • Decentralized Clinical Trials (DCT)
  • Clinical Data Management
  • Medical Device & Diagnostics
  • Biotech & Pharma
  • CROs
  • Academic Research

Resources

  • Thought Leadership
  • Blog
  • Castor Academy
  • Knowledge Base

 

Company

  • About Us
  • Careers
  • News
  • Contact Support
  • Contact Us

Legal & Compliance

  • Terms of Use
  • Privacy & Cookie Statement
  • Responsible Disclosure Policy
  • Good Clinical Practice (GCP)
  • ISO Compliance Certificates
  • GDPR & HIPAA Compliance
  • Security Statement

© 2022, Castor. All Rights Reserved.

Follow us on social media


Knowledge Base Software powered by Helpjuice

Definition by Author

0
0
Expand