Page tree

Content from this environment has been migrated to https://confluence.wustl.edu/

Skip to end of metadata
Go to start of metadata

 

FAQ List

1.0 PI and PA Issues

1.1 - Boilerplate language for inclusion in grants and IRB documentation

 

Grant Acknowledgement:
Please note that any publication that results from a project utilizing REDCap should cite grant support (Supported by Clinical and Translational Science Award (CTSA) Grant [UL1 TR000448] and Siteman Comprehensive Cancer Center and NCI Cancer Center Support Grant P30 CA091842).

Examples of Text for inclusion into submissions:

Example 1: (more for general citation)

The Washington University School of Medicine  Institute for Informatics (I2), Informatics Core Services (ICS) will be used as a central location for data processing and management. Washington University, belongs to a consortium of institutional partners that work to maintain a software toolset and workflow methodology for electronic collection and management of research and clinical trial data. REDCap (Research Electronic Data Capture) data collection projects rely on a thorough study-specific data dictionary defined in an iterative self-documenting process by all members of the research team with planning assistance from the Center for Biomedical Informatics. The iterative development and testing process results in a well-planned data collection strategy for individual studies. REDCap also contains a Survey tool for building and managing online surveys. The research team can create and design surveys in a web browser and engage potential respondents using a variety of notification methods. Both REDCap and REDCap Survey systems provide secure, web-based applications that are flexible enough to be used for a variety of types of research, provide an intuitive interface for users to enter data and have real time validation rules (with automated data type and range checks) at the time of entry. These systems offer easy data manipulation with audit trails and reporting for reporting, monitoring and querying patient records, and an automated export mechanism to common statistical packages (SPSS, SAS, Stata, R/S-Plus).

Example 2: (more for IRB, need to update stats accordingly)
The Washington University School of Medicine Institute for Informatics (I2), Informatics Core Services (ICS) will be used as a central location for data processing and management. Washington University, belongs to a consortium of institutional partners that work to maintain a software toolset and workflow methodology for electronic collection and management of research and clinical trial data. REDCap (Research Electronic Data Capture) data collection projects rely on a thorough study-specific data dictionary defined in an iterative self-documenting process by all members of the research team with planning assistance from ICS. The iterative development and testing process results in a well-planned data collection strategy for individual studies. REDCap servers are securely housed in an on-site limited access data center managed by Research Infrastructure Services at Washington University. All web-based information transmission is encrypted. The data is all stored on a private, firewall protected network. All users are given individual user ids and passwords and their access is restricted on a role-specific basis. REDCap was developed specifically around HIPAA-Security guidelines and is implemented and maintained according to Washington University guidelines. REDCap currently supports > 2100 academic/non-profit consortium partners on six continents and >456,000 research end-users [1].

Example 3: (more for general citation)
Study data were collected and managed using REDCap electronic data capture tools hosted in the Washington University School of Medicine Institute for Informatics (I2), Informatics Core Services (ICS).  REDCap (Research Electronic Data Capture) is a secure, web-based application designed to support data capture for research studies, providing: 1) an intuitive interface for validated data entry; 2) audit trails for tracking data manipulation and export procedures; 3) automated export procedures for seamless data downloads to common statistical packages; and 4) procedures for importing data from external sources.

1Paul A. Harris, Robert Taylor, Robert Thielke, Jonathon Payne, Nathaniel Gonzalez, Jose G. Conde, Research electronic data capture (REDCap) – A metadata-driven methodology and workflow process for providing translational research informatics support, J Biomed Inform. 2009 Apr;42(2):377-81.


Publications/Proceedings/Presentations:
P.A. Harris, R. Thielke, R. Taylor, J. Payne, N. Gonzalez, J.G. Conde. Research Electronic Data Capture (REDCap) – A metadata-driven methodology and workflow process for providing translational research informatics support. Journal of Biomedical Informatics, 2008 (doi:10.1016/j.jbi.2008.08.010).

P.A. Harris, R. Taylor, R. Thielke, J. Lee, R. Sanders, M. Isozaki, H. Howard, S. Hemphill, C. McGraw, B. Nieves, A. Peshansky, A. Nida, M. Lin. The REDCap Consortium Project: A Case Study in Collaborative Software Development for Clinical Research Informatics. (Panel Presentation – AMIA Spring Conference, 2008)

P. Harris, R. Thielke, R. Schuff, J. Obeid, M. Oium. The REDCap consortium – A case study in translational research informatics resource sharing among academic institutions. (AMIA Spring Conference, 2007)

P.A. Harris. REDCap (Research Electronic Data CAPture) project progress report for informatics resource sharing / collaboration at ten academic institutions. (Clinical Research, 2007)

P.A. Harris, N. Gonzalez, M Silva-Ramos, J.G. Conde. Web-based data collection – collaborative development of metadata collection and export modules. (Clinical Research, 2006)

P.A. Harris, J.D. Payne. Creating custom web-based data collection systems. (Clinical Research, 2005) (Abstract)
The following is an overview of our REDCap installation.

Our REDCap database is hosted on Unix servers on our divisions secure computer network. User access is provided via an external secure web server.  All web communication between the user web browser and the web server is SSL encrypted. The database server itself is currently not encrypted via any encryption at rest schema. Further protections are provided via strict Unix permission configurations on the servers themselves.

The database is incrementally backed-up nightly, with baseline snapshots taken at the beginning of each month.  Daily incremental backups are stored for approximately 30 days, and the baseline snapshots are currently store indefinitely.  Uploaded files are stored on a secure Unix file servers and are protected by our off-site backup server.

Access to the data username/password keys is restricted in accordance with our University’s HIPAA policy.

 

I2 WUSM ICS Acknowledgement Statement

It is very important to the continued funding of the Siteman Comprehensive Cancer Center that the productive collaboration of its cores is acknowledged in publications and presentations.  This aids in measuring our productivity and provides documentation of the scope of our services.

In addition, all publications using the services of the I2 WUSM ICS should contain one of the following acknowledgements:

“The authors wish to acknowledge the support of the I2 WUSM ICS, Siteman Comprehensive Cancer Center and NCI Cancer Center Support Grant P30 CA091842 .”

 

“The authors wish to acknowledge the support of the I2 WUSM ICS and NCI Cancer Center Support Grant P30 CA091842, Siteman Comprehensive Cancer Center,  for supporting the REDCap clinical data capture service as a research resource at WUSM“

 

ICTS Member Publication Acknowledgement Instructions.
NIH Funding Acknowledgement

Use of any ICTS Core or service requires the following NIH Funding Acknowledgement for all publications and projects.

“Research reported in this publication was supported by the Washington University Institute of Clinical and Translational Sciences grant UL1 TR000448 from the National Center for Advancing Translational Sciences (NCATS) of the National Institutes of Health (NIH). The content is solely the responsibility of the authors and does not necessarily represent the official view of the NIH.”
ICTS Scholars and Trainees, please note:

ICTS grant supported scholars and trainees should reference the applicable NIH sub award number noted below for their direct career development/training support.

KL2 TR000450 – ICTS Multidisciplinary Clinical Research Career Development Program TL1 TR000449 – ICTS Clinical Research Predoctoral Training Program
Questions can be directed to icts@dom.wustl.edu or 314-362-9829.

Information on the National Center for Advancing Translational Sciences (NCATS) is available at http://www.ncats.nih.gov/. Information about the Clinical and Translational Science Awards program can be found at http://www.ncats.nih.gov/research/cts/cts.html.

Publication Requirements Applicable clinical trials must be registered with ClinicalTrails.gov. (http://www.clinicaltrials.gov/)

PubMed Central ID (PMCID)

NIH-funded investigators are required to submit (or have submitted for them) their final, peer-reviewed manuscript to PubMed Central (PMC) upon acceptance of publication to be made publicly available within 12 months of publication. This policy applies to NIH-funded manuscripts accepted for publication on or after April 7, 2008. Note: PMCID is not the same as PMID.

See the WU Benard Becker Medical Library website for complete instructions: https://becker.wustl.edu/classes-consulting/specialized-expertise/nih-public-access-policy.

 

 

2.0 User Account Issues

2.1 - I have a REDCap account. Why don’t I have access to any databases?

You only have access to databases that you create and other databases to which you have been given access.  If there is a database that you need to use, contact the PI or REDCap Project Administrator with your REDCap user name.  REDCap Administrators (that’s us) do not give access to databases.

2.2 - I’ve switched departments. Do I need a different REDCap account?

No, you can use your existing REDCap account on any database to which you have access.  You should send us an email, though, with your updated contact information.

2.3 - Can non-Washington University personnel get REDCap accounts?

Yes, provided they are collaborating on a Washington University project or a project of a WU affiliate. They fill out the same user-account application as WU applicants do.  Non-Washington University applicants must supply the name and email address of their WU collaborator.

2.4 - My supervisor’s account was suspended for inactivity. Will you reactivate it?

For security reasons, the request has to come from the user and not from a second party. Please have your supervisor send an email to REDCap_Helpdesk@wustl.edu asking that his account be reactivated. The email address should be the same one that was given on the user’s REDCap-account application.

2.5 - My supervisor forgot his password. Will you reset it?

For security reasons, requests to reset passwords must come from the user and not from a second party. Please have your supervisor send an email to REDCap_Helpdesk@wustl.edu asking that his password be reset. The email address should be the same one that was given on the user’s REDCap-account application.


3.0 Study Development

3.01 - REDCap Best Practices for Data Collection of Clinical Trials

(See linked page)

3.02 - What are the steps for creating a REDCap database for my research?

First, apply for a REDCap user account. Next, view the relevant video tutorials to learn about database creation, variable types, branching logic, item validation, and other REDCap features. (The videos can be viewed without an account.)  After you receive your account, create preliminary versions of your forms on the Demo server*, test them, and refine them.  When you are satisfied that your forms are ready to use, apply for a REDCap project account if you do not already have one.  When the project account has been created, move the database to the Production server and do more testing, this time with real data.  Put the database into production status when appropriate.  At this point you have the option of retaining the existing data or erasing it.

*Note: Users with database-creation privileges on the Production server, whether based on the current project or a previous one, have the option of creating and developing their project on the Production server rather than the Demo server. This saves the step of moving the project from the Demo to the Production server. Developing the project on the Production server is especially helpful when the project is a longitudinal one or involves surveys. Both of these require customization that must be done on the Production server.

3.03 - What is a REDCap project account?

The project account is an authorization to create project-related databases on the Production server.  The account application specifies the PI, the Project Administrator, the project name, and the HRPO number, if applicable.  The account is specific to a project.  If you want to create a database related to a different project, a new application should be submitted.

3.04 - Do Quality Improvement Projects need IRB approval?

HRPO's recommendation is for Quality Improvement project researchers to contact Mitchell Shawn Saulisbury-Robertson who is the Expedited Review Manager and request a determination on what approval is needed for their data collection. Determinations are made on a case by case basis. 

Name: Mitchell Shawn Saulisbury-Robertson

Address: Campus Box 8089

Phone: (314) 747-7022 

Title: HRPO Expedited Review Manager

Department: Human Research Protection Office

Email: m.saulisbury-robertson@wustl.edu

3.05 - Who can create databases on the Production server?

Only the project PI and the designated project administrator (PA) are authorized to create databases on the Production server, and only after a REDCap project-account application for the project has been submitted.  (After the database is created, other users can be given the Database Management privilege to develop and modify the database.)

3.06 - Why is the “Move project to production” button grayed-out?

There are two possibilities: either you do not have database-creation privileges on the Production server or your database is on the Demo server. 

Creation of databases on the Production server is restricted to REDCap Project Administrators (PA) and Principal Investigators (PI) named on REDCap Project-account applications. See Account Request Form for access to the application.

If you are the PA or PI and the button is grayed-out, your project is probably on the Demo server. The database must be moved to the Production server before it can be put into production status.  See the FAQ item on moving databases to the Production server.

If you have a REDCap account for the project and you are using the Production server, it may be that we neglected to check the box that gives you database-creation privileges. Send an email to REDCap_Helpdesk@wustl.edu to let us know.

3.07 - Move REDCap Study To Production Status

To put a database into production status, you must have access to the Production Server. A Project Account must be created before data can be entered.

Here are the steps for moving a database into production:
1. If the database is on the Demo server, download a copy of the data dictionary. If it is on the Production server, start at step 2.

2. Log on to the Production Server and create a database. (There should be a tab near the top of the REDCap screen labeled “Create New Project.” If that tab is missing, your database-creation privilege has not been activated. Contact the REDCap administrators to correct this.) A project request form must be submitted for each study designating the Project Administrator and Principal Investigator. Only Project Administrators and Principal Investigators are authorized to create databases on the Production Server.

3. Upload the copy of data dictionary to the Production Server.

4. If the database is a longitudinal database, define the events and assign forms to the events.

5. Enter some test data to satisfy yourself that the database is functioning the way you want it to. Please test your database thoroughly, making changes to the data dictionary as needed. After the database is put into production, any changes have to be approved by a REDCap administrator.

6. Put the database into production by going to the Control Panel and Settings page and clicking the button labeled “Move to Production Status.”

7. Use the User Rights page and give database access to your users.

3.08 - When should I put my database into Production Status?

Databases can only be put into production status on the Production server. Production status is not available on the Demo server.

Please do not rush to put the database into production status. Do sufficient testing to assure yourself that the database is ready for use. Test it yourself and have colleagues test it by making up and entering data. When you’ve got it running smoothly, move it to the Production server if it isn’t already there (a REDCap project account is needed for this.) If there are any made-up records in the database you can delete them and start entering real data. (There is an Erase All Data button on the Other Functionality page.) This is the true test of whether or not the database is ready for production. If the database passes your tests you can put it into production status, retaining the data that have been entered. If the database requires changes, you can make them and retain the existing data if appropriate or delete the data if it needs to be re-entered. After the database is in production status, changes may need to be approved by a REDCap Administrator before they take effect.

If you find you’ve put the database into production status too soon, you can ask the REDCap Administrators to move it back to development status. You can put it back into production when it’s ready.

3.09 - REDCap Double Data Entry Feature

The Double Data entry feature allows a project administrator to designate two users per study to perform double data entry. Other users are then able to compare the data entry results, using the data comparison tool. This requires that the Double Data Entry feature be activated for the study.

Alternative way of performing Double Data Entry
Project administrators may also choose to designate a study participant ID prefix or suffix (ie. “x_”), in order to compare data entries. Data entry comparisons can then be made using the data comparison tool, and selecting the appropriate comparisons. (ie. “01” and “x_01″)

3.10 - Where are the video tutorials located?

The latest versions of the tutorials can be found at the Video Resources tab on the REDCap Consortium website.

3.11 - Aside from the video tutorials, what REDCap educational materials are available?

Once you have your account you can read the REDCap Help & FAQ page.  There is a tab to it on most REDCap screens.  The REDCap starting page <http://www.biostat.wustl.edu/redcap/> has links to several REDCap User Group presentations and REDCap newsletters.

There is also a free online training course developed by Vanderbilt and offered through Coursera (course:Clinical Data Management)

3.12 - What is the difference between the Demo server and the Production server?

The Demo server is used for getting acquainted with REDCap features and, optionally, creating and testing databases that will later be used for data entry on the Production server. Databases on the Demo server are not authorized for data collection. While the Production server can also be used for creating and testing databases, its main distinction is that databases can be put into production status and used to collect real data.

Databases and surveys cannot be put into production status on the Demo server. Production status only exists on the Production server.

Longitudinal databases should be created on the Production server or moved to the Production server before events are created. This is because the event table and the form*event table do not transfer from one server to another: they have to be created on the serve on which they will be used. Moving the database to the Production server before this customization will reduce the amount of duplicated effort.

Similarly, surveys should be created on the Production server or moved there before much customization is done. The customization does not transfer to the Production server, so to avoid wasted effort, the project should be on the Production server before customization is done.

User accounts are created on the Production server.  The account is not available on the Demo server until after the user logs into the Production server and changes the temporary password.  Once that is done, the account will be activated on the Demo server within a half-hour.  If the account is not activated, contact the REDCap Administrator at REDCap_Helpdesk@wustl.edu. Users who will just be entering data into an existing database on the Production server may not need to ever use their account on the Demo server.

Any user can create databases on the Demo server.  Only Principle Investigators (PI) who have submitted REDCap project-account applications and the designated REDCap Project Administrator (PA) can create databases on the Production server.

Only test data, not real data containing PHI, should be entered into databases on the Demo server.

Data entered into databases on the Demo server is subject to deletion if the REDCap Administrator finds that we need to recover disk space.

Navigate to the URL https://redcap.wust.edu to select either server.

3.13 - How can I add a new choice to an existing radio or dropdown item without changing previously entered data?

It’s important to know that the choices in radio and dropdown items are displayed in the order in which they are found in the data dictionary. This isn’t necessarily numeric order.

Suppose you have a radio item with the choices:

      • 1,Adams
      • 2,Grant
      • 3,Jones
      • 4,Smith

and later want to add another choice, Clark, and also to keep the choices in alphabetical order. This is the way NOT to make the changes:

      • 1,Adams
      • 2,Clark
      • 3,Grant
      • 4,Jones
      • 5,Smith

If these changes are approved, existing data for Grant, Jones, and Smith will be corrupted. Records that were entered as Grant will belong to Clark, those that were entered as Jones will belong to Grant, and so on.

The new choice can be added without changing existing data in this way:

      • 1,Adams
      • 5,Clark
      • 2,Grant
      • 3,Jones
      • 4,Smith

The choices will still appear in alphabetical order and existing data will not be changed.

3.14 - How can I edit and format the text within my project?

Text formatting can be added to certain elements in your project using CSS styles and HTML tags.  
Examples include: 

 Field labels
 Section headings and descriptive text fields
 Survey welcome and thank-you messages
 Survey invitation emails

Basic HTML & CSS Formatting in REDCap

3.15 - How do I setup Twilio to send SMS text messages and voice calls?

REDCap has the capability to utilize a third party SMS and voice call service called Twilio for sending survey invitations via SMS text messages and also for having respondents take surveys via a voice call or SMS.  With this feature enabled, you can invite a participant to take a survey by sending them an SMS message or by calling them on their phone.  The participants can then take your surveys, either as a voice call survey or as an SMS message conversation.  The survey data would then be collected in REDCap directly from their phone without having to use the website.  
SETUP & CONFIGURATION:  Before you begin the setup steps below, you must:
1. Register and setup up your own Twilio account at www.twilio.com
2. Fund your account with some money using the Billing page in Twilio (since there is a cost for each phone call made and for each SMS message sent and
3. Purchase a phone number to be used for this REDCap project (see the Numbers page in Twilio).  Each project must have its own number.
Once you have a phone number setup in Twilio for your project, you will need to send an email to the REDCap administrator (redcap_helpdesk@wustl.edu) with the following information:

1. Twilio Phone Number
2. Twilio Auth Token
3. Twilio Account SID

(see the API Credentials section on the Twilio main Account Settings page)

Note: Please ensure you have DISABLED Twilio's 'Request Inspector' for this account:
A Twilio feature named Request Inspector causes all activity to be logged in detail and stored on Twilio's servers. For the highest level of privacy, it MUST BE DISABLED in your Twilio account in order to be able to utilize the Twilio services in REDCap. You will find this setting on the Configure page under 'Programmable Voice'

Once your receive a confirmation email back from your REDCap administrator that your project is connected to your Twilio account, you can then configure how you want to use Twilio in your project. In general, not much is different between administering a survey normally in REDCap than when using Twilio SMS/voice calls except that you additionally choose how your survey invitations are delivered. The following choices are available:

1. Initiate survey as voice call
2. Initiate survey as SMS conversation
3. Send survey invitation with survey link via SMS
4. Send survey invitation via SMS to take survey as voice call (respondent makes call)
5. Send survey invitation via SMS to take survey as voice call (respondent receives call when replying via SMS).
Any or all of these invitation delivery methods can be utilized within a single project. The choice of delivery method completely depends upon your specific use case for how you want to collect data from your participants.  It is NOT recommended to use option 

VOICE CALL SURVEYS: When participants take a survey as a voice call, questions are asked one at a time, in which the Twilio service will use text-to-speech technology to read the questions to the participant audibly on their phone. You may choose the language and/or dialect in which the text should be read. Participants will respond by entering numbers on their phone's keypad, thus only numeric responses can be used because of this limitation (this includes the use of integer/number fields and also multiple choice questions with numeric codings, in which the participant will enter the numeric coded value on their keypad, not the label that is read to them over the phone). For example, the question might be a Yes-No question, which might look like 'Do you like ice cream? Yes, press 1. No, press 0.', or a number question like 'What is your age?'.

SMS SURVEYS: When participants take an SMS survey, questions are asked one at a time as an SMS text message conversation/thread. SMS surveys provide more response possibilities than voice calls. While participants in voice calls can only respond with numbers, they may respond with any kind of alpha-numeric text for an SMS survey.
Note:  Only REDCap administrators are allowed to enable the Twilio option to initiate a survey as an SMS conversation. Much like email, SMS is not considered a secure form of communication, so you may not want to administer surveys as SMS conversations if the particpant will be submitting identifying information (PHI or PII) unless you have been granted special permission from the participant to do so. Given such sensitive privacy issues, only your local REDCap administrator can enable the optional setting to use SMS surveys. Please notify your administrator about this if you wish to have this option enabled.

COMPATIBILITY: Most of REDCap's survey features still function much the same when taking a survey via SMS or as a voice call. This includes the enforcement of required fields, field validation, branching logic, using the Survey Queue for multiple surveys (only works with Auto-Start enabled), survey email notifications and confirmations, the Participant List, Automated Survey Invitations, survey Stop Actions, and computer adaptive tests (CATs) downloaded from the REDCap Shared Library. One of the few survey features that is not compatible is the Survey Login feature.
COST: In order to use the Twilio SMS and Voice Call services in a REDCap project, you will have to connect your project to your Twilio account by entering your Twilio credentials into REDCap during the setup process. And as REDCap makes calls and/or sends SMS messages using this service, all charges to your Twilio account will be made based upon its usage. This is not done by REDCap but is done internally by Twilio as you use its services. In this way, no monetary transactions are made by REDCap, and thus it is your responsiblity to maintain the funds in your Twilio account in order to ensure that the service continues to work for your REDCap project. If your Twilio account runs out of funds, the Twilio services in REDCap will cease to function. For information on the cost of each call or each SMS message, visit your Twilio account to view the rates.
PRIVACY & SECURITY INFO: It is important to understand that this feature utilizes the third-party service Twilio.com, which means that all voice calls and SMS messages will be routed through Twilio's servers. However, REDCap goes to great length to ensure that voice call records and SMS transcriptions do not stay in Twilio's logs but are removed shortly after being completed. This is done for security and privacy concerns (e.g., HIPAA), in which your survey participants' phone numbers and their survey responses do not get permanently logged on Twilio's servers but instead remain securely in REDCap.
IRB COMPLIANCE:  All projects requiring IRB approval must report to the IRB that their project utilizes Trilio.

4.0 - Study Management

4.01 - What is the REDCap URL?

The URL for the Production server is 
https://redcap.wustl.edu/redcap/srvrs/prod_v3_1_0_001/redcap/ and the URL for the Demo server is 
https://redcap.wustl.edu/redcap/srvrs/dev_v3_1_0_001/redcap/ . However, we don’t recommend that you bookmark these links because they may change. Instead, bookmark a link to one of our preceding pages.

If you bookmark https://redcap.wustl.edu/ you will have buttons with which to select either server.

If you bookmark http://www.biostat.wustl.edu/redcap/ you will have easy access to the the servers and the REDCap FAQ.

4.02 - I tried to give a user access to my database but REDCap says he cannot be granted access because he is not yet a REDCap user. What’s up with that?

If you are on the Production server, either the person doesn’t have a REDCap account or you are entering the user name incorrectly.  If you are on the Demo server, it is likely that the person hasn’t yet logged in to the Production server and changed his password.  Accounts are created on the Production server and transferred to the Demo server after the password is changed. 

4.03 -  I logged in to REDCap and there aren’t any projects listed under “My Projects.” They were there yesterday. Where did they go?    

It’s possible but unlikely that your access to the projects was revoked.  It’s much more likely that the projects were on the Production server and you logged in to the Demo server, or vice versa.     

4.04 - I’ve created a REDCap database. How do I give others access to it?    

When a database is created, only the user creating the database has access to it.  The database creator can give access to others through the User Rights page in REDCap.  Navigate to the User Rights screen and enter the person’s REDCap user name.  Assign the necessary rights.     

4.05 - How do I delete a record?    

The ability to delete records exists in REDCap but is turned off by default.  A user with access to the User Rights page can turn it on.  When the Delete Record right is active, there will be a Delete Record button at the bottom of each form.  Deleting a record deletes all data for all forms for that ID for that arm of the database, not just the form on which the delete button is pressed.  We strongly suggest that it be turned on only when necessary and turned off again when not needed.


4.06 - I entered an ID incorrectly. How can I correct it?    

The ability to change record IDs exists in REDCap but is turned off by default.  A user with access to the User Rights page can turn it on.  We strongly suggest that it be turned on only when necessary and turned off again when not needed.  

4.07 - I changed my password on the Production server. Do I also have to change it on the Demo server?   

You do if you want to use the same password on both servers. User accounts are created on the Demo server. When the user logs in for the first time and changes the assigned password to a new one, the account is automatically enabled on the Production server with the same new password. That is the only time that the passwords are automatically synchronized. After that, if you change your password on one server it does not affect the password on the other server. It is up to you keep them the same or different, as you prefer.    

4.08 -  How do I get my password reset?    

Navigate to the login page for the server you want to use, click the “Forgot your password?” link, and enter your user name. If REDCap responds that it can’t reset your password then you either entered an incorrect user name or you have not yet set a security question. You will need to send a request to REDCap_Helpdesk@wustl.edu asking that your password be reset. If REDCap displays your security question and your answer it correctly, REDCap will send you an email with a link that will take you to a page where you can set a new password.

4.09 - How do I set a security question so that I an reset my password myself?

Log in to the REDCap server that you want to use. In the upper-right corner of most REDCap pages is the link labeled “My Profile.” Click the link and then click the “Reset password recovery question” button. Select the question you want to use, enter the answer, and save the page.

4.10 -  How do I see the same summary of proposed data-dictionary changes that the REDCap Administrator sees?    

When making changes to the data dictionary of a project that is in production status, the user can see a summary of the changes along with REDCap’s evaluation of the changes. The is the summary that the REDCap administrators see when the changes need approval. It lists variables being added, deleted, and changed, and it also lists warnings when a change can lead to corruption or loss of data.

To see the summary when submitting changes, click the link “View detailed summary of all drafted changes.

4.11 - Will you give me access to a REDCap project?    

No. You are asking us to give you access to another person’s data and we can’t do that. You need to contact the project’s PI or REDCap Project Administrator (PA.) If you don’t know who either of those are, we may be able to help you identify them. Information that will be helpful to us:
the exact name of the database in REDCap;
the study’s HRPO number;
the names of others who have access to the database.     

4.12 -  How do I transfer my project to a new PI?    

This is best done while you are still at Washington University.

Have the incoming PI submit a new REDCap Project Account.

Give the incoming PI access to the project-associated REDCap databases.

Send an email to REDCap_Helpdesk@wustl.edu telling us the name and email address of the new PI and the exact names of the project-associated REDCap databases that will be transferred to the new PI.

If you leave the university without first transferring your REDCap project to a new PI we will have to check with HRPO to verify that the new PI is in charge of the project. The new PI still needs to submit a REDCap project-account application.

4.13 - How do I designate a different REDCap Project Administrator for my project?    

The PI should send an email to REDCap_Helpdesk@wustl.edu giving the name, email address, and REDCap user name of the new REDCap Project Administrator. In addition, the REDCap project ID (PID) number must be specified. The PID number is in the project’s URL when accessing the project. It is the string of digits following the string “pid=” . In the following example, the PID is 1647 :

https://redcap.wustl.edu/redcap/srvrs/prod_v3_1_0_001/redcap/redcap_v6.11.2/index.php?pid=1647     

5.0 - Data Export

5.01 - My REDCap data are not importing into SPSS correctly. What should I do??

SPSS is very sensitive to invalid data. The first thing to do is to run the Field Validation Errors (Incorrect Data Type) task in the Data Quality tool in the Applications section of your REDCap project. (This requires permission on the User Rights screen.) Correct any errors and try the export again.


Carriage Returns in text fields can also cause problems. Run an export that excludes non-validated text fields and try importing it into SPSS. If this import succeeds then there are problems in the text fields. Either edit the text data, deleting carriage returns, or exclude the fields from your exports.

Field names must begin with a letter.  If importing a field name the begins with an underscore you will need to rename the field in the SPSS syntax file before running the SPSS program.  Remember the SPSS CSV file does not contain the column names so only the SPSS syntax file needs to be edited.


If neither of these steps solve them problem, send a copy of the log generated from the import, along with a description of the problem and the steps you’ve taken to solve it, to REDCap_Helpdesk@wustl.edu.

 

6.0 - MyCap

6.01 - What is MyCap

MyCap is an extension to REDCap that lets researchers capture patient reported outcomes using a participant’s phone or tablet. MyCap is similar to REDCap surveys in that participants enter data which is then synchronized to the researcher’s REDCap project. REDCap surveys are administered through a web browser whereas MyCap “tasks” are administered through a custom designed mobile application for Android and iOS devices.

6.02 - MyCap Features

MyCap has many features in addition to capturing basic task data:

·         Offline access: Participants may complete tasks without internet connectivity. Data are stored in an encrypted database on the device and synchronized to REDCap when possible.

·         Active tasks: Some tasks utilize the device’s hardware sensors to capture steps taken, sound, images, video, heart rate, and more.

See http://researchkit.org/docs/docs/ActiveTasks/ActiveTasks.html for information on active tasks. 

·         Scheduling: Flexible scheduling for one-time tasks, repeating tasks, and permanent tasks. 

·         Reminders: Participants receive a notification on their device when a task is due.

·         Secure text messaging: Researchers may send a message to an individual participant or an announcement to all participants.

·         Customization: Researchers use the MyCap module within REDCap to define informational screens, specify contact information, choose a color scheme.

·         Security: The MyCap mobile app protects participant data by requiring a 6-digit passcode to unlock the app.

·         Multi-project support: A participant may join multiple projects on a single device.. 

6.03 - To Demo MyCap

1) Install MyCap from the Google Play Store or Apple App Store. Links are provided on https://projectmycap.org/.

2) Visit https://www.projectmycap.org/?demo

   Page 173 of 200 REDCap version 9.1.2 updated June 28, 2019

3) Scroll down to the bottom of the page and submit the “PUBLIC DEMO” form. You should see a QR code after submitting the form.

4) Open the MyCap mobile app and scan your QR code.

To request a new MyCap-enabled REDCap project or to ask any question regarding MyCap, please email mycap@vumc.org.

 

6.04 - To Setup a Wash U. Production MyCap Project

Contact the REDCap Administrator at REDCap_helpdesk@wustl.edu

 

6.05 - Difference between REDCap Mobile App and MyCap, consider this information


6.06 - MyCap Boilerplates

Technology Boilerplate for IRB Submissions

Patient level, clinician level, and clinic level data for [Change to represent your study] will be collected using MyCap and stored electronically in the REDCap platform.

MyCap makes it easy for researchers to capture participant/patient reported outcomes using mobile devices. REDCap is used to define tasks/instruments/surveys to be completed by participants. MyCap translates REDCap task metadata into a structure compatible with ResearchKit and ResearchStack. When a project participant completes a task, MyCap converts the results into a format compatible with REDCap before synchronizing back to the REDCap project.

MyCap App Security:

Participant data is stored locally on the device in an AES-256+SHA2 encrypted database. Data remains on the device if an internet connection is not available. Applies to both iOS and Android devices.

When an internet connection is available, data is transmitted to REDCap using a SSL connection. A hash-based message authentication code (HMAC) is used to verify the integrity of the data and to authenticate the sender.

Data is wiped from the device after the MyCap app verifies that data has been successfully transmitted. Note that there is an optional MyCap feature that lets a participant see some of the data s/he has entered for an individual task/instrument/survey. By default, data is wiped.

Authentication to Device:

Participants create a 6-digit PIN that is used to open the MyCap, this is in addition to the authentication already on their device. A participant can choose to disable the MyCap PIN feature.

Boilerplate for Consent Document

Risks: Participation in the research study using the MyCap App involves entering the data in a secure, encrypted environment.  No data entered can be intercepted and read using this method.  [If your study uses this feature: There is an optional MyCap feature that lets a participant see some of the information s/he has entered for an individual task/instrument/survey. When this is used, data remains on the device to provide visual feedback back to the research subject, by default, data is wiped.]

Cost for the Research Subject:  The MyCap App is free to download and use.

Benefits:  You will be able to participate in the research study using your own device at a time convenient to you.

How your information is stored:  Your information is stored locally on your device in an AES-256+SHA2 encrypted database. Information remains on the device if an internet connection is not available. Applies to both iOS and Android devices. When an internet connection is available, information is transmitted to REDCap using a SSL connection. A hash-based message authentication code (HMAC) is used to verify the integrity of the data and to authenticate the sender. Your information is wiped from the device after the MyCap app verifies that data has been successfully transmitted.

Upon consenting, you acknowledge that you will be receiving personal health and identifying questions to answer within the application

 




 

 


  • No labels