Page Comparison

...

Follow the below instructions to submit your request:

1. Check project settings.  Instructions are at: Modify Project Title, Purpose, etc.

   1. Project must have a meaningful project nameMake sure title with CTSI number included in title

   2. Ensure the purpose of the project is not “Just for fun”

   3. If it’s a research project, enter IRB number, Name of P.I., email of P.I., and Name of P.I. as cited in publications

   Test every form on project to make sure they are working and edited correctly. 

   1. 1. Instructions are at: Modify Project Title, Purpose, etc.

2. Select PHI identifiers

   1. How to Select PHI Identifiers

   2. What Are PHI and PII Identifiers

3. Test the project process, using test records:

   1. Enter test data onto into all instruments on your project (ensuring any instruments that are setup as a ‘survey' are tested as such. This is extremely helpful useful in exposing data issues before moving a project to “production” status!

      1. Survey delivery and collection as if you were the end user/participant

      2. Repeat forms

      3. Events / Arms (if longitudinal project)

      4. Create Reports of test data to ensure it meets your project's aim(s)

         • Export data so PI, statistician, etc may review to verify it meets their expectations.

   2. Test project fields, functions, and modules including:

      • Survey Delivery & record tracking

      • Branching logic

   3. Calculations

   4. Validations

   Piping

   • / Piping /Calculations / Field validations

   • External Modules

   • Survey Settings:

     • Survey Queue

     • Survey Invitations

     • Automated

   survey invitations

   5. Scheduling module – used to generate schedules for your project calendar for a longitudinal project (Cannot be used for automated survey invitations)

   6. Mobile App

   • • Survey Invitations

   • Any other features/customization utilized in your project

   7. How To Test Data Collection

   8. How To Test Public Surveys

   9. How To Test Private Surveys

4. Select PHI identifiers

   1. How to Select PHI Identifiers

   2. What Are PHI and PII Identifiers

5. Verify that the first field on the first form is unique and Not a PHI identifier

6. Export data and have statistician look at it to verify it meets his/her expectations. 

7. Test the project process, including:

   1. Events (if longitudinal project)

   2. Surveys

   3. Repeat forms

   4. Arms (if project contains 2 or more)

   5. Export data and review it for correctness

   6. Create Reports and export these to see if they meet your project's aims

8. Review and update User Rights/Roles/Privileges

   1. We highly recommend no more than 2 users have “User rights” AND “Project Set Up” privileges.

      These are the highest level of privilege able to be assigned! We recommend only the PI and lead coordinator have both these permissions.

       Any user with these permission can edit not only their own rights, but other users' as well plus have access to key functionality!!

   2. https://utahctsi.atlassian.net/servicedesk/customer/portal/3/article/276988105?src=-1101536905

   3. https://utahctsi.atlassian.net/servicedesk/customer/portal/3/article/276988269?src=-1546574335

9. Have others test it out

   1. Send to co-workers and have them test it out; it always helps to get feedback from others.

 The Process

To move your project to production status, follow the these steps:

1. After completing the check-list of items to test before moving your project to production, navigate to the "Project Setup" page,

2. scroll Submit the projects ‘Move to Production Request’

   1. Navigate to your project setup page

   2. Scroll to the bottom, and click on "Move project to production" (circled in red in image below)

   

   Next a notice will display (shown in image below).  Verify you have done everything listed on it before moving your project to production, especially testing the project.

                        

   Image Removed

3. The "Move Project To Production Status" box will display (shown in image below).  Here, select whether to keep the existing entered data, or delete it.  Then

   1. Because real data should never be collected in development mode, you should request to delete existing test data, then click "YES, Move to Production Status" to submit your

   request. NOTE: since real data should never be collected in development mode, you should

   1. request

   to delete existing test data

   1. .
                 

      Image Modified

4. Once your project has been submitted, the REDCap Support Team will be notified and review your project. You will either be notified of errors that exist and/or approve your project.   

   1. You will be notified

   by REDCap when

   1. if your project has been

   moved to production

   1. approved or if further information/testing/checks are required to proceed.