Working...  Working...
This value you provided is not a number. Please try again.
This value you provided is not an integer. Please try again.
The value entered is not a valid Vanderbilt Medical Record Number (i.e. 4- to 9-digit number, excluding leading zeros). Please try again.
The value you provided must be within the suggested range
The value you provided is outside the suggested range
This value is admissible, but you may wish to double check it.
The value entered must be a time value in the following format HH:MM within the range 00:00-23:59 (e.g., 04:32 or 23:19).
This field must be a 5 or 9 digit U.S. ZIP Code (like 94043). Please re-enter it now.
This field must be a 10 digit U.S. phone number (like 415 555 1212). Please re-enter it now.
This field must be a valid email address (like joe@user.com). Please re-enter it now.
The value you provided could not be validated because it does not follow the expected format. Please try again.
Required format:
/^((0?[1-9])|([1-8][0-9])|(9[0-8]))[0-9]{3}$/
/^((29([-\/])02\3(\d{2}([13579][26]|[2468][048]|04|08)|(1600|2[048]00)))|((((0[1-9]|1\d|2[0-8])([-\/])(0[1-9]|1[012]))|((29|30)([-\/])(0[13-9]|1[012]))|(31([-\/])(0[13578]|1[02])))(\11|\15|\18)\d{4}))$/
/^((02([-\/])29\3(\d{2}([13579][26]|[2468][048]|04|08)|(1600|2[048]00)))|((((0[1-9]|1[012])([-\/])(0[1-9]|1\d|2[0-8]))|((0[13-9]|1[012])([-\/])(29|30))|((0[13578]|1[02])([-\/])31))(\11|\15|\19)\d{4}))$/
/^(((\d{2}([13579][26]|[2468][048]|04|08)|(1600|2[048]00))([-\/])02(\6)29)|(\d{4}([-\/])((0[1-9]|1[012])(\9)(0[1-9]|1\d|2[0-8])|((0[13-9]|1[012])(\9)(29|30))|((0[13578]|1[02])(\9)31))))$/
/^((29([-\/])02\3(\d{2}([13579][26]|[2468][048]|04|08)|(1600|2[048]00)))|((((0[1-9]|1\d|2[0-8])([-\/])(0[1-9]|1[012]))|((29|30)([-\/])(0[13-9]|1[012]))|(31([-\/])(0[13578]|1[02])))(\11|\15|\18)\d{4})) (\d|[0-1]\d|[2][0-3]):[0-5]\d$/
/^((02([-\/])29\3(\d{2}([13579][26]|[2468][048]|04|08)|(1600|2[048]00)))|((((0[1-9]|1[012])([-\/])(0[1-9]|1\d|2[0-8]))|((0[13-9]|1[012])([-\/])(29|30))|((0[13578]|1[02])([-\/])31))(\11|\15|\19)\d{4})) (\d|[0-1]\d|[2][0-3]):[0-5]\d$/
/^(((\d{2}([13579][26]|[2468][048]|04|08)|(1600|2[048]00))([-\/])02(\6)29)|(\d{4}([-\/])((0[1-9]|1[012])(\9)(0[1-9]|1\d|2[0-8])|((0[13-9]|1[012])(\9)(29|30))|((0[13578]|1[02])(\9)31)))) (\d|[0-1]\d|[2][0-3]):[0-5]\d$/
/^((29([-\/])02\3(\d{2}([13579][26]|[2468][048]|04|08)|(1600|2[048]00)))|((((0[1-9]|1\d|2[0-8])([-\/])(0[1-9]|1[012]))|((29|30)([-\/])(0[13-9]|1[012]))|(31([-\/])(0[13578]|1[02])))(\11|\15|\18)\d{4})) (\d|[0-1]\d|[2][0-3])(:[0-5]\d){2}$/
/^((02([-\/])29\3(\d{2}([13579][26]|[2468][048]|04|08)|(1600|2[048]00)))|((((0[1-9]|1[012])([-\/])(0[1-9]|1\d|2[0-8]))|((0[13-9]|1[012])([-\/])(29|30))|((0[13578]|1[02])([-\/])31))(\11|\15|\19)\d{4})) (\d|[0-1]\d|[2][0-3])(:[0-5]\d){2}$/
/^(((\d{2}([13579][26]|[2468][048]|04|08)|(1600|2[048]00))([-\/])02(\6)29)|(\d{4}([-\/])((0[1-9]|1[012])(\9)(0[1-9]|1\d|2[0-8])|((0[13-9]|1[012])(\9)(29|30))|((0[13578]|1[02])(\9)31)))) (\d|[0-1]\d|[2][0-3])(:[0-5]\d){2}$/
/^(?!\.)((?!.*\.{2})[a-zA-Z0-9\u0080-\u02AF\u0300-\u07FF\u0900-\u18AF\u1900-\u1A1F\u1B00-\u1B7F\u1D00-\u1FFF\u20D0-\u214F\u2C00-\u2DDF\u2F00-\u2FDF\u2FF0-\u2FFF\u3040-\u319F\u31C0-\uA4CF\uA700-\uA71F\uA800-\uA82F\uA840-\uA87F\uAC00-\uD7AF\uF900-\uFAFF!#$%&'*+\-/=?^_`{|}~\d]+)(\.[a-zA-Z0-9\u0080-\u02AF\u0300-\u07FF\u0900-\u18AF\u1900-\u1A1F\u1B00-\u1B7F\u1D00-\u1FFF\u20D0-\u214F\u2C00-\u2DDF\u2F00-\u2FDF\u2FF0-\u2FFF\u3040-\u319F\u31C0-\uA4CF\uA700-\uA71F\uA800-\uA82F\uA840-\uA87F\uAC00-\uD7AF\uF900-\uFAFF!#$%&'*+\-/=?^_`{|}~\d]+)*@(?!\.)([a-zA-Z0-9\u0080-\u02AF\u0300-\u07FF\u0900-\u18AF\u1900-\u1A1F\u1B00-\u1B7F\u1D00-\u1FFF\u20D0-\u214F\u2C00-\u2DDF\u2F00-\u2FDF\u2FF0-\u2FFF\u3040-\u319F\u31C0-\uA4CF\uA700-\uA71F\uA800-\uA82F\uA840-\uA87F\uAC00-\uD7AF\uF900-\uFAFF\-\.\d]+)((\.([a-zA-Z\u0080-\u02AF\u0300-\u07FF\u0900-\u18AF\u1900-\u1A1F\u1B00-\u1B7F\u1D00-\u1FFF\u20D0-\u214F\u2C00-\u2DDF\u2F00-\u2FDF\u2FF0-\u2FFF\u3040-\u319F\u31C0-\uA4CF\uA700-\uA71F\uA800-\uA82F\uA840-\uA87F\uAC00-\uD7AF\uF900-\uFAFF]){2,63})+)$/i
/^[-+]?\b\d+\b$/
/^[a-z]+$/i
/^\d{10}$/
/^[a-z0-9-_]+$/i
/^[-+]?[0-9]*\.?[0-9]+([eE][-+]?[0-9]+)?$/
/^-?\d+,\d$/
/^-?\d+\.\d$/
/^-?\d+,\d{2}$/
/^-?\d+\.\d{2}$/
/^-?\d+,\d{3}$/
/^-?\d+\.\d{3}$/
/^-?\d+,\d{4}$/
/^-?\d+\.\d{4}$/
/^[-+]?[0-9]*,?[0-9]+([eE][-+]?[0-9]+)?$/
/^(\(0[2-8]\)|0[2-8])\s*\d{4}\s*\d{4}$/
/^(?:\(?([2-9]0[1-9]|[2-9]1[02-9]|[2-9][2-9][0-9]|800|811)\)?)\s*(?:[.-]\s*)?([2-9]1[02-9]|[2-9][02-9]1|[2-9][02-9]{2})\s*(?:[.-]\s*)?([0-9]{4})(?:\s*(?:#|x\.?|ext\.?|extension)\s*(\d+))?$/
/^\d{4}$/
/^[ABCEGHJKLMNPRSTVXY]{1}\d{1}[A-Z]{1}\s*\d{1}[A-Z]{1}\d{1}$/i
/^(0[1-9]|[1-9]\d)\d{3}$/
/^\d{3}-\d\d-\d{4}$/
/^(\d|[01]\d|(2[0-3]))(:[0-5]\d){2}$/
/^([0-9]|[0-1][0-9]|[2][0-3]):([0-5][0-9])$/
/^[0-5]\d:[0-5]\d$/
/^[0-9]{4,9}$/
/^\d{5}(-\d{4})?$/

Notifications

System Notifications
General Notifications

Conversations

Create new conversation

Multiple Surveys (classic)PID 9
Data Quality

This module will allow you to execute data quality rules upon your project data to check for discrepancies in your data. Listed below are some pre-defined data rules that you may utilize and run. You may also create your own rules or edit, delete, or reorder the rules you have already created. To find discrepancies for a given rule, simply click the Execute button next to it, or click the Execute All Rules button to fire all the rules at once. It will provide you with a total number of discrepancies found for each rule and will allow you to view the details of those discrepancies by clicking the View link next to each. Read more detailed instructions.

You can only add new Data Quality Rules to the project by uploading a CSV file with a new Data Quality Rules configuration. The format for the CSV upload file can be acquired by exporting the CSV file of your existing Data Quality Rules.
Note: You cannot edit or delete existing Data Quality Rules using the CSV file but can only do that by clicking the edit/delete icon next to a given Rule.
Select your CSV file of Data Quality Rules to be added:
Displayed below is a preview of all new data quality rules you are about to commit. Please look over the additions, and then approve them by clicking the Upload button.
Note: These new data quality rules will be added to the existing set of data quality rules.
Data Quality Rules
Execute rules:


Apply to:
Rule #
Rule Name
Rule Logic  (Show discrepancy only if...)
Real-time execution?
Total Discrepancies
Delete rule?
pd-3
A
Blank values*
 -
pd-6
B
Blank values* (required fields only)
 -
pd-4
C
Field validation errors (incorrect data type)
 -
pd-9
D
Field validation errors (out of range)
 -
pd-5
E
Outliers for numerical fields
(numbers, integers, sliders, calc fields)**
 -
pd-7
F
Hidden fields that contain values***
 -
pd-8
G
Multiple choice fields with invalid values
 -
pd-10
H
Incorrect values for calculated fields
 -
pd-11
I
Fields containing "missing data codes"
 -






 
Enter descriptive name for new rule
(e.g., Participants below age 18)
 
Enter logic for new rule
(e.g., [age] < 18)
Execute in real time on data entry forms?
* The Blank Values rules above automatically exclude fields hidden by branching logic when searching for blank values. If a field is hidden by branching logic on a data entry form or survey, then it is expected that such a field would not have a value. Thus for these cases, the values for those hidden fields will not be classified as missing. Additionally, checkbox fields are also excluded since an unchecked checkbox is itself often considered to be a real value. Note: This rule will not return any fields that are blank but also have Missing Data Codes. If you wish to find fields with Missing Data Codes, it is recommended to execute Rule I instead.
** The term 'outlier' refers to a value that is more than two standard deviations from the mean.
*** The term 'hidden fields' refers to any fields on a survey or data entry form that are not being displayed because branching logic is hiding them, which assumes that the field's value should be blank/null.
You may hide certain results from displaying again and again by excluding them. Simply click the 'exclude' link for a result in the table of discrepancies for a rule, and that result will not be counted next time in the number of discrepancies for that rule, nor will it be displayed in the table of results. Results that have been excluded can be viewed again by clicking the 'view' link at the top of the results table for that rule, in which it will display the number of excluded results if any should exist. Results may have their exclusion status removed by clicking the 'remove exclusion' link in the results table for an excluded result.
Data issues found with the Data Quality module can be resolved using the Data Resolution Workflow. After executing any given data quality rule and viewing the results in the pop-up window, you will see a button in the 'Resolve issue' column that allows you and other users in the project to leave comments and/or complete a formal data resolution process for documenting details of the data issue, including the origin the issue, who resolved the issue, and how it was resolved (if applicable). Once the data resolution process has been opened for an item, it will then appear in the 'Resolve Issues', which allows you to view all open items that need to be resolved.
Enabling the 'real-time execution' functionality for a custom rule is a great way to add more data validation on a data entry form to ensure that data are getting entered correctly *at the moment* they are entered, as opposed to checking the quality of the data retroactively by executing the rules here on this page. Using the 'real-time execution' feature is an excellent way to be proactive about maintaining the quality and integrity of your data.

Checking the 'real-time execution' checkbox for any custom data quality rule will enable the rule to be executed invisibly on data entry forms whenever a user clicks the Save button to create or modify a record. After clicking Save, it will execute all relevant data quality rules invisibly (i.e. behind the scenes) and will display a warning pop-up message if any of the rules have been violated, in which it will display a list of the data quality rules that were violated and also display the fields involved with their data values. If no rules were violated, then it will save the record as usual and not display a pop-up message. Just like the results that are returned when executing rules on the Data Quality page itself, results displayed on data entry forms for 'real-time execution' can be excluded (if desired) so that they will not be displayed again if they are still in violation in the future.

NOTE: The pre-defined rules cannot have 'real-time execution' enabled, but only the custom rules can. Also, the 'real-time execution' functionality does not work on survey pages, nor does it get executed when performing data imports (either via the Data Import Tool or via the API). Thus, it only works on data entry forms.
REDCap 12.2.0 - © 2025 Vanderbilt University