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
  • EDC/CDMS
  • Castor EDC Manual
  • Fields and field properties

Field properties: validations (edit checks) and dependencies (field logic) in EDC/CDMS

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.

  • EDC/CDMS
    Castor EDC Manual Castor EDC Calculations Manual Frequently Asked Questions Articles for Data Managers Castor EDC 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
  • Helpdesk
    News Other Resources
  • Status page
+ More

Table of Contents

Data validation (real-time edit checks) Data validation using partial dates If a date field allows partial dates to be entered, you can determine how those dates will be handled by dependencies and validations in the “Date field” configuration: Dependencies (field logic) Multiple dependencies

Data validation (real-time edit checks)

Data validation messages can be used to inform users about required actions or warn them about possible errors, based on data they have entered.

 

Please note that the Data Validation tab is not available on the following fields: Time, Remark, Summary, QR code, Repeated Measure, Randomization, Image, Grid, Date and Time, Number and Date, Repeating Data Button and Add a survey.

 

 

Follow these steps to set up a message:

  1. Click the 'Data validation'tab when creating/editing a field.
  2. Choose the condition (the entered value) that will prompt the message.
  3. Choose the message type. There are four types of messages:
  • Message: A simple indication message, outlined in blue, that the user needs to take a certain action.

     
  • Warning: An orange coloured message bar appears to warn the user that something is incorrect.

     
  • Error: A red outlined message can be used to indicate that data has been entered is not accepted or wrong. When the error message type is displayed, the data for that field is not saved. This means that a subsequent field cannot be dependent on a value that would trigger the 'Error' message.

     
  • Exclusion: A message in purple that excludes the subject from the study; when this message is visible to the user, it is possible to navigate to different forms in a Study form:
    • if an exclusion occurs on the study form, data entry is blocked on the entire study and on any repeating data instances. The Exclusion message will be displayed on every form in the study data view with the name of the form where the exclusion has been triggered. The repeating data view will be grayed out: 
    • If an exclusion occurs on a repeating data instance form, data entry is blocked on that same instance, but not blocked on any other repeating data instances or study data.

      You can use this for validating inclusion and exclusion criteria. Please be aware, that it's not possible to leave fields with exclusion criteria empty (user missing), nor possible to enter values which are outside the boundaries you have set.

In the following example an exclusion message is set when the patient has not signed informed consent:

 

* NOTE: max. length of the message to show is 255 characters

Data validation using partial dates

If a date field allows partial dates to be entered, you can determine how those dates will be handled by dependencies and validations in the “Date field” configuration:

  • Ignore - partial values will be ignored by said validations and dependencies
  • Trigger or matching - a partial match will be used for the purposes of validations and dependencies
  • Round up - partial dates will be rounded up to the latest calendar day for the purposes of validations and dependencies (e.g. March 2023 is treated as 31-03-2023)
  • Round down - partial dates will be rounded down to the earliest calendar day for the purposes of validations and dependencies (e.g. March 2023 is treated as 01-03-2023)

You can learn more about partial dates by visiting Entering and managing partial dates in Castor CDMS article.

Dependencies (field logic)

If you want to make a field dependent on another field, e.g. only show the question "Pregnant" when the field Gender is set to "Female", take the following steps:

  1. Click on the 'Dependencies' tab.
  2. Choose 'Yes' for the 'Field is dependent' property.
  3. Choose the Form where the parent field is located. The parent field is the field that your new field will be dependent on, such as 'Gender'.
  4. Choose the parent field.
  5. Choose an operator, e.g. 'equal to' or 'greater than' and then choose a value - this is the value the parent field should have in order for the new field to appear. 

In this example, the current field “Is patient pregnant?” is only displayed when the field "Gender", on the Form "Demographics" is set to "Female":

 

 

Field dependencies will be displayed in the Form Builder alongside the field label - it will be shown in your Form that this field only appears when the defined rule is true:

 

Multiple dependencies

Currently it is only possible to select one condition for a dependency. If you want to set multiple dependencies, e.g. show your new field based on data entered in multiple other fields, then you will need to create a calculation field and use a template described in this article: Can I make a field dependent on multiple fields?

dependency dependencies field dependency field dependencies parent field dependent make a field dependent of the other make a field dependent field property notifications validation exclusion warning error message

Was this article helpful?

Yes
No
Give feedback about this article

Related Articles

  • Create a new field in EDC/CDMS
  • The 'Summary' field in EDC/CDMS
  • The 'Repeated measure' field in EDC/CDMS
  • The 'Remark' field in EDC/CDMS
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

Definition by Author

0
0
Expand