| Panel | ||||||
|---|---|---|---|---|---|---|
| ||||||
| Note | ||||||
Per University Policy, real data should NEVER be collected indevelopmentDevelopment mode.!Before you may start collecting real data, your project must be moved to Production mode. Before moving a REDCap Project to Production, be certain to test it out by entering test data. All the test data will be deleted when the project is moved to production.‘Move to Production Request’ must be submitted and approved by a REDCap Administrator |
Follow the below instructions to submit your request:
Check project settings.
...
Project must have a meaningful project
...
title with CTSI number included in title
Ensure the purpose of the project is not “Just for fun”
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. A checklist of things to test is at:
...
/wiki/spaces/~62bf0f53268cac6e31c5f4b1/pages/276987956
Instructions are at: Modify Project Title, Purpose, etc.
Select PHI identifiers
Test the project process, using test records:
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!
Survey delivery and collection as if you were the end user/participant
Repeat forms
Events / Arms (if longitudinal project)
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.
Test project fields, functions, and modules including:
Survey Delivery & record tracking
Branching logic
...
Calculations
...
Validations
...
Piping
/ Piping /Calculations / Field validations
External Modules
Survey Settings:
Survey Queue
Survey Invitations
Automated
...
Scheduling module – used to generate schedules for your project calendar for a longitudinal project (Cannot be used for automated survey invitations)
...
Mobile App
...
Surveys
...
Repeat forms
...
Arms (if project contains 2 or more)
...
Export data and review it for correctness
...
Survey Invitations
Any other features/customization utilized in your project
...
Select PHI identifiers
...
Verify that the first field on the first form is unique and Not a PHI identifier (list of PHI identifiers is at: What Are PHI and PII Identifiers )
...
Export data and have statistician look at it to verify it meets his/her expectations.
Test the project process, including:
...
Events (if longitudinal project)
Review and update User Rights/Roles/Privileges
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!!
https://utahctsi.atlassian.net/servicedesk/customer/portal/3/article/276988105?src=-1101536905
https://utahctsi.atlassian.net/servicedesk/customer/portal/3/article/276988269?src=-1546574335
Have others test it out
Send to co-workers and have them test it out; it always helps to get feedback from others.
Submit the projects ‘Move to Production Request’
Navigate to your project setup page
Scroll to the bottom, and click on "Move project to production" (circled in red in image below)
The "Move Project To Production Status" box will display.
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.
Once your project has been submitted, the REDCap Support Team will be notified and review your project.
You will be notified if your project has been approved or if further information/testing/checks are required to proceed.