Add users
Remove users
Download as Excel/CSV
Archive conversation
Project Home and Design
Data Collection
Applications
Help & Information
Longitudinal Database (1 arm)PID 2
Data Exports, Reports, and Stats
In reports you can add as many filters as you wish, and you can get quite complex with the filter logic using
multiple fields with AND and OR conditional logic. To add a filter, select a field that you wish to filter on, after which you will need to set
both an operator and a value. If the field is multiple choice, it will auto load all of that field's choices in a drop-down so
that you may choose one of the choices. Otherwise, if it is not a multiple choice field, it will instead provide a text box for entering the filter value.
There is no limit to how many times you may use a field as a filter in a single report. TIP: If you want to find instances in your data where a field's value is blank/null, then just leave the value text box blank. Conversely, to find instances where the field has a value (i.e., is non-blank), set the operator as 'not =' with a blank text box.
Using ANDs and ORs with multiple fields allow you to do more complex filtering. If you have two filters with an AND between them, for example, that means that it will apply both of them together when filtering, but if you use OR, it will return results that apply to just one or the other. In general, using AND will often constrict the results further by returning less data in the report than when using OR.
If you have filtering that uses both OR and AND, it is very important to know the order in which REDCap evaluates the ORs and ANDs to ensure that your logic behaves how you expect. Essentially, all the ORs are evaluated for consecutive filter fields as a group, and all the groups are then evaluated as ANDs with each other. For example, it looks like (this OR this OR this) AND (this OR this OR this), in which all the ORs inside the parentheses are evaluated first and then those groups of ORs are then evaluated together using ANDs.
If you wish to do even more complex filtering, you may choose to switch the filtering format over to the 'Advanced Logic', which allows you to hand-type the filtering logic in a big text box. The filter logic is essentially the same kind of syntax as Branching Logic and Calculated field equations, in which you may use all the special functions, such as if(), datediff(), and various mathematical functions, in your filtering logic. REDCap will double check your hand-typed logic for any syntax errors, and it will not allow you to save the report until all errors have been resolved. When using the Advanced Logic, just make sure that your logic ultimately evaluates to either TRUE or FALSE and that it does *not* evaluate to a value, such as a number. For example, datediff([dob], 'today', 'y') is not valid because it will evaluate to a number, but datediff([dob], 'today', 'y') > 30 is valid because it will evaluate as either TRUE or FALSE.
There is no limit to how many times you may use a field as a filter in a single report. TIP: If you want to find instances in your data where a field's value is blank/null, then just leave the value text box blank. Conversely, to find instances where the field has a value (i.e., is non-blank), set the operator as 'not =' with a blank text box.
Using ANDs and ORs with multiple fields allow you to do more complex filtering. If you have two filters with an AND between them, for example, that means that it will apply both of them together when filtering, but if you use OR, it will return results that apply to just one or the other. In general, using AND will often constrict the results further by returning less data in the report than when using OR.
If you have filtering that uses both OR and AND, it is very important to know the order in which REDCap evaluates the ORs and ANDs to ensure that your logic behaves how you expect. Essentially, all the ORs are evaluated for consecutive filter fields as a group, and all the groups are then evaluated as ANDs with each other. For example, it looks like (this OR this OR this) AND (this OR this OR this), in which all the ORs inside the parentheses are evaluated first and then those groups of ORs are then evaluated together using ANDs.
If you wish to do even more complex filtering, you may choose to switch the filtering format over to the 'Advanced Logic', which allows you to hand-type the filtering logic in a big text box. The filter logic is essentially the same kind of syntax as Branching Logic and Calculated field equations, in which you may use all the special functions, such as if(), datediff(), and various mathematical functions, in your filtering logic. REDCap will double check your hand-typed logic for any syntax errors, and it will not allow you to save the report until all errors have been resolved. When using the Advanced Logic, just make sure that your logic ultimately evaluates to either TRUE or FALSE and that it does *not* evaluate to a value, such as a number. For example, datediff([dob], 'today', 'y') is not valid because it will evaluate to a number, but datediff([dob], 'today', 'y') > 30 is valid because it will evaluate as either TRUE or FALSE.
The value you entered does not exist as a valid variable name in this project. Please re-enter it and try again.
What does this setting do?
When building a report for a longitudinal project and using Step 3 (filtering), any filters defined in the report will be applied to each record as a whole, which is the default behavior when the 'Show data for all events for each record returned' checkbox is CHECKED. But if it is UNCHECKED, it will additionally apply the filters to each event within each record returned, in which some (or all) of the events in the records returned could get removed from the results. So if CHECKED, then *all* events are returned for each record, but if UNCHECKED, then some events in each record *may* get removed (depending on the filter).
For example, if the project contains one event to capture demographics information and also contains subsequent visits (events) to capture measurements for vitals, one could set a filter of [sex] = '1' (Female). So if the checkbox setting was left CHECKED (the default setting), it would only return records where the person was female, and the results would contain *all* events (demography and all visits) for each of those records. However, if the checkbox was UNCHECKED in that situation, then not only would it remove the records where the person was male, but it would additionally remove the visit events for the female records, thus returning only the demography event for the female records. In this way, having the checkbox UNCHECKED not only filters out some of the records, but it may also remove some of the events in the records that are returned.
SUMMARY: In most cases, this checkbox setting will be left CHECKED unless you have very specific intentions for unchecking it. If you are still not quite sure how you might use this setting, then it is recommended that you leave it CHECKED.
When building a report for a longitudinal project and using Step 3 (filtering), any filters defined in the report will be applied to each record as a whole, which is the default behavior when the 'Show data for all events for each record returned' checkbox is CHECKED. But if it is UNCHECKED, it will additionally apply the filters to each event within each record returned, in which some (or all) of the events in the records returned could get removed from the results. So if CHECKED, then *all* events are returned for each record, but if UNCHECKED, then some events in each record *may* get removed (depending on the filter).
For example, if the project contains one event to capture demographics information and also contains subsequent visits (events) to capture measurements for vitals, one could set a filter of [sex] = '1' (Female). So if the checkbox setting was left CHECKED (the default setting), it would only return records where the person was female, and the results would contain *all* events (demography and all visits) for each of those records. However, if the checkbox was UNCHECKED in that situation, then not only would it remove the records where the person was male, but it would additionally remove the visit events for the female records, thus returning only the demography event for the female records. In this way, having the checkbox UNCHECKED not only filters out some of the records, but it may also remove some of the events in the records that are returned.
SUMMARY: In most cases, this checkbox setting will be left CHECKED unless you have very specific intentions for unchecking it. If you are still not quite sure how you might use this setting, then it is recommended that you leave it CHECKED.
Select your export settings, which includes the export format (Excel/CSV, SAS, SPSS, R, Stata)
and if you wish to perform de-identification on the data set.
You may create a new report by selecting the fields/variables below that you want to include in the report.
You may add as many fields to your report as you wish, and you can choose which users may view this report.
You will also need to provide a name for your report,
which will then be displayed on the project's left-hand menu for anyone to whom you have given access.
You can filter the results returned in the report in a variety of ways,
including using complex AND/OR logic. When you are finished, click the Save Report button at the bottom.
The new report will then be added to your list of reports, after which you may immediately begin viewing them or exporting them.
You may create a short and easy to remember custom URL that redirects to your public report. Enter the your desired custom URL
that you wish to redirect to your public report. When submitted, it will check if the URL has already been taken.
If not, it will save the custom URL here in your project so that you may continue to use it.
https://redcap.link/
NOTICE: The ending of custom URLs may only contain letters, numbers, dots/periods, dashes, and underscores.
In order to make this report "public" to allow the report to be accessed at a public link, you must first meet the requirements and also agree
to the statements below by checking their checkboxes after reading them. Once that is completed, click the "Make report public" button at the bottom to finalize it.
You have User Rights privileges in this project.
This report does not have any Identifier fields.
You must view the report to confirm it is the correct report you want to make public: You have NOT viewed this report during your current REDCap session. Click here to navigate to this report and view it. Once you have viewed the report, return back to this page before your session ends to continue.
NOTICE: After the report has been made public, only users with User Rights privileges will be able to obtain the public link for the report, as the link will be
displayed on this page, in the report list, and also on the report itself.
Sorry, but you do not meet the requirements above in order to make this report "public". Please review the information above to learn how.
| REDCap 12.2.0 - © 2025 Vanderbilt University |