Page Comparison

Longitudinal Projects
This Knowledge Article reviews both Single and Multi-Arm Longitudinal Projects.
It is extremely important to give much consideration to the design, development and testing of your Longitudinal Project. Understanding reporting considerations & needs is critical. Thorough testing is essential for success.
Initial Considerations
Longitudinal projects provide collection of data over time in order to track changes and progress. Longitudinal projects are useful in the following situations:

...

1. Create your instruments. See Build a Project
   \

2. Enable Longitudinal Mode at the project level

   1. Navigate to your project

   2. Select the "Project Setup" tab

      

   3. Click the "Enable" button next to 'Use Longitudinal data collection with defined events"

      

3. Set up User Rights

   1. Assigning User Rights to team members should be a carefully thought out decision. The consequences of poor user rights decisions could be damaging to the security and integrity of the project. See Knowledge Article User Rights

   2. The User Rights page can be used to determine the roles that a user can assume within a REDCap database. The Data Access Group on the other hand determines the data visibility of a user within a REDCap database.

      1. Data Access Groups restrict viewing of data within a database. A typical use of Data Access Groups is a multi-site study where users at each site should only be able to view data from their site but not any other sites. Users at each site are assigned to a group, and will only be able to see records created by users within their group. See Knowledge Article Data Access Groups

   3. Navigate to the left navigation bar and select User Rights:

      

   4. Add user with customer rights or assign to a role

      

   5. To create DAG, navigate to tab adjacent to User Rights
      

4. Define Events / Arms for the Project (e.g., patient visits, tasks or point in time)

   1. On Project Setup Page, navigate to "Define My Events"

      

   2. Type the title of the event in the text box then click Add New Event

      

   3. Repeat above steps until each of your events have been created
      

5. Link Instruments to relevant events

   1. From the Project Setup page, navigate to "Designate Instruments for My Events"

      

   2. Select "Begin Editing" button

      

   3. Click to place a checkbox on the grid for each instrument / form / survey that should be assigned to each specific event

      

   4. Click "Save"

   5. In order to ensure that other advanced features like reporting and data quality checks in REDCap work properly, always assign the first form to the first event. (i.e. Order your instruments appropriately)

   6. You can link and un-link events in your project during your project set-up and test. Once the project is in Production linking /unlinking events must be done by REDCap Administrator . Reason: You can lose data if you unlink an event. REDCap provides no warning
      

6. Longitudinal Calendar (optional feature. You can not link to Google / Outlook Calendars of the department so rarely used) . However, it does allow a REDCap user to view the calendar, and open any patients scheduled for that day and open the instruments for that event.

   1. Can turn on / off as desired (prod or development)

   2. Can't limit user rights. Have access to calendar and all its features

   3. Produces automatically generated schedules

      • by participant

      • based on how set up Arms and Events

   4. Calendar event status can flag "no show" or "cancel" for visit status

   5. To enable, on Project Setup page navigate to Enable Optional Modules section and click on Enable next to Scheduling module

      

   6. Click on Scheduling on left navigation bar.

   7. Select a patient (or create new), define start date & ARM, click Generate Schedule

      

      Can input times and switch scheduled days of the week by changing dates if desired 

   8. When done modifying the Projected Schedule, click Create Schedule

      

   9. You will see a notice that your calendar was successfully created

      

      j. To see the Calendar, navigate to left Navigation pane and select Calendar under Applications

...

Additional Considerations

1. Best practice to always add Record ID to every arm to prevent REDCap issues, especially if using surveys

   1. Create a "single landing page" with just Record ID. Can be invisible to user with a "Thanks for Participating Page" with Submit to continue. See Knowledge Article Longitudinal Surveys
      

2. Actions that can cause data loss in Longitudinal Projects:

   1. Deleting Events

   2. Deleting Arms

   3. Decoupling Forms from Events
      

3. If you create additional forms once project is in Production, need to request REDCap support to link forms to Events.
   

4. Give much consideration to User Rights. If you want to segregate data based on location but have a form that is common to both sites, a user with rights to that form will see data from both sites. Create Data Access Groups
   

5. Branching logic in a Longitudinal Project must identify the arm and the field name.

   1. Classical Branching Equation:

      1. [field1] = '3'

      2. Longitudinal Branching Equation:

         1. Can cross both forms and events, so need to indicate event and field

         2. [event_3][field1] = '3'
            

6. Survey Expiration

   1. Is server time, not what is on your computer

      1. Survey expiration takes all copies of the survey offline.

      2. Warning: If you have survey that is used multiple times in a longitudinal survey if you expire the survey after the first event, be aware that it will expire all the surveys in following events
         

7. Save and return later

   1. The User Code is often lost and user can't find the code when they want to return to complete the survey.

      1. Alternative is to design shorter surveys and poll multiple times via automatic invites
         

8. Anchor
   _GoBack _GoBack

   Deleting or Disabling a survey in Survey Settings.

   1. There are 2 "delete" buttons for any given project.

      1. 1 is in Online Designer – deletes entire form and data is lost

      2. 1 is in Survey Settings – reverts survey back to a form. Data is still available
         

9. When defining Events it is important to think about the days offset and use an accurate representation in case you ever want to use scheduling

...