Working …
This value you provided is not a number. Please try again.
This value you provided is not an integer. Please try again.
The value entered is not a valid Vanderbilt Medical Record Number (i.e. 4- to 9-digit number, excluding leading zeros). Please try again.
The value you provided must be within the suggested range
The value you provided is outside the suggested range
This value is admissible, but you may wish to double check it.
The value entered must be a time value in the following format HH:MM within the range 00:00-23:59 (e.g., 04:32 or 23:19).
This field must be a 5 or 9 digit U.S. ZIP Code (like 94043). Please re-enter it now.
This field must be a 10 digit North American phone number (like 415 555 1212). Please re-enter it now.
This field must be a valid email address (like joe@user.com). Please re-enter it now.
The value you provided could not be validated because it does not follow the expected format. Please try again.
Required format:

Notifications

System Notifications
General Notifications

Conversations

Create new conversation

AUD MOCAPID 16
MyCap uses a configuration versioning system. When a participant opens their MyCap mobile app, it sends a request to the REDCap server to see if a new configuration version has been published. The mobile app updates itself as needed if a new version is found.

Changes you make to the MyCap configuration do not automatically trigger a new version. You must explicitly indicate that changes you have made should be published to the MyCap mobile app.

 MyCap Participant Management

An app synchronization issue is created when the Android or iOS MyCap app sends a task result to the REDCap server that is incompatible with your REDCap project for some reason. This typically occurs when a participant completes an old version of a task/instrument. The purpose of the synchronization issue mechanism is to always capture data that is sent from the MyCap app, ensuring no loss of data. Synchronization issues indicate a problem and should be investigated. Show example

EXAMPLE

  1. You create a task/instrument with a "Multiple Choice - Radio Buttons (Single Answer)" field. You specify choices having values:
    0, No
    1, Yes
    2, Sometimes
  2. You publish MyCap project configuration version 1 and a participant joins your project.
  3. The participant completes the task with answer  No (0) and the result is sent to REDCap to be saved.
  4. REDCap accepts the result because  No (0) is a valid choice value.
  5. Later, you decide to change the values of your multiple choice field to:
    No, No
    Yes, Yes
    Sometimes, Sometimes
  6. You forget to publish a new version of the MyCap configuration.
  7. The participant completes the task again with answer  No (0) and the result is sent to REDCap to be saved.
  8. REDCap rejects the result because  No (0) is no longer a valid choice value. It was changed to  No (No).
  9. MyCap creates a synchronization issue using the rejected REDCap response.
  10. You review the synchronization issue and see that the result could not be saved due to an invalid choice value.
  11. You create the appropriate REDCap entry using the provided synchroniozation issue data, and then flag the synchronization issue as resolved.
  12. You publish MyCap project configuration version 2 so participants recieve your updated multiple choice field values.

App Sync Issues
(in descending order by date)
Date Begin time: Date End time: (M/D/Y H:M)
Display Display
Reset
Displaying of 0
Date
Status
Participant
Instrument
Result ID
Action
No Synchronization Issues exist
REDCap 15.0.35 - © 2026 Vanderbilt University - Cookie policy