10:30 am - 10:55 am Rm 309 IntermediateREDCap is built around change management principles, but it can still be confusing how to maintain a separate test environment. This session looks at a few ideas and one real-life example.
ABSTRACTLori L. Millikan | Managing Test and Production EnvironmentsREDCap is built around change management principles, but it can still be confusing how to maintain a separate test environment.
- Why bother having a separate test environment?
- Training
- Play around
- Lots of moving parts
Quick overview of REDCap change management tools available
- Project Setup
- Online Designer – Draft Mode (with undo) and Review Changes
- Copy or Back Up the Project
- Project Revision History
- Data Dictionary (both download and upload)
Some test/prod ideas using these tools alone (will highlight advantages/disadv of each)
- No test environment—make changes directly to production with Draft Mode
- Create a copy of your project whenever you want to make changes
- Maintain two REDCap projects and copy data dictionary/alerts/etc. from test to prod
Real-life Foster Care Bridge Clinic model
Maintain two REDCap projects AND some basic documentation outside of REDCap
- Slide showing the test/prod projects that have animations adding in the two turnover docs
-- Advantages added = more easily understood and searched
-- Disadvantage added = time to do the documentation
- Test project never gets moved to production status, always in development status
- May end up with acceptable differences (like the word TEST added to surveys)
- Look at actual turnover list
- Look at some actual go-live documents
Other REDCap tools we use
- Upload/download Data Quality Rules
- Upload/download Alerts? (never got this one to work well?)
- Logging Manage/Design events
Some differences between Test and Production are always there:
- “TEST” language on some surveys and alerts
- Alert recipients, time frames and [Secure Message] tags
- Reports, Project Dashboards
Discussion - What do the session participants do?
