Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

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 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

      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 into all instruments on your project ensuring any instruments that are setup as a ‘survey' are tested as such. This is extremely 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 / Piping /Calculations / Field validations

      • External Modules

      • Survey Settings:

        • Survey Queue

        • Survey Invitations

        • Automated Survey Invitations

      • Any other features/customization utilized in your project

    3. How To Test Data Collection

    4. How To Test Public Surveys

    5. How To Test Private Surveys

  4. 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

  5. Have others test it out

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

  6. 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)

  7. The "Move Project To Production Status" box will display. 

    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.
                 

  8. Once your project has been submitted, the REDCap Support Team will be notified and review your project.   

    1. You will be notified if your project has been approved or if further information/testing/checks are required to proceed.

...