Written and maintained by CASRAI Editorial Board
Published
On this page
Informational only; this clinical research informatics reference explains the Vanderbilt REDCap Mobile Application architecture and regulatory governance and does not provide medical advice.
The REDCap Mobile App is an offline electronic data capture (EDC) application for iOS and Android tablets and smartphones developed by the Paul A. Harris team at Vanderbilt University Medical Center (Harris et al., JAMIA Open, 2021) as an extension of the REDCap (Research Electronic Data Capture) platform. Designed specifically for field epidemiology, home health visits, disaster-response cohorts, and global clinical trials operating in environments with intermittent or zero internet connectivity, the REDCap Mobile App downloads a project’s data dictionary and longitudinal event schedule via a project-specific REDCap API token, stores collected participant records in an AES-256 encrypted local SQLite database on the mobile device, and synchronizes records and audit logs back to the central institutional REDCap research database once network connectivity is restored.
What Is REDCap Mobile App and How Is It Used in Clinical Research and Healthcare?
Unlike the browser-based REDCap survey interface or the participant-facing MyCap patient-reported outcomes app, the REDCap Mobile App is a staff-facing offline data collection instrument engineered for clinical research coordinators (CRCs), field interviewers, and community health workers.
When comparing the REDCap Mobile App against standalone humanitarian field survey tools such as KoBoToolbox, research informatics teams evaluate how the mobile client interacts with the central REDCap server across four architectural stages:
| Workflow Stage | REDCap Mobile App Technical Operation | Connectivity Requirement | Security & Audit Control |
|---|---|---|---|
| 1. Server Privilege & Token Provisioning | Project administrator grants user rights for REDCap Mobile App and generates a 32-character hexadecimal API token and QR initialization code. |
Online (HTTPS connection to institutional REDCap host). | Role-based access control and REDCap User Rights and Data Access Groups (DAGs) restrict which records a device can pull. |
| 2. Project Initialization on Device | App scans the QR code (or accepts the 10-character initialization code) to download the project Data Dictionary, branching logic, calculated fields, and Repeating Instruments. | Online (initial setup or metadata refresh). | TLS 1.2/1.3 in transit; local app requires a separate device user PIN and administrator password. |
| 3. Offline Field Data Capture | Field staff create new records or update downloaded longitudinal events, capturing discrete fields, finger-drawn e-consent signatures, audio recordings, and camera photographs. | 100% Offline (zero cellular or Wi-Fi required). | Data at rest are stored in an AES-256 encrypted SQLite container; every keystroke and form save is timestamped in the local device log. |
| 4. Bidirectional Sync & Conflict Resolution | User executes Send Data to Server when connectivity returns; app detects record ID collisions or field-level edits and prompts reconciliation before committing via API. |
Online (Wi-Fi or cellular data). | Full mobile interaction log is uploaded to the central REDCap Logging module (`Mobile App` event tags); local device records can be wiped post-sync. |
Step-by-Step Configuration: Setting Up a Project for the REDCap Mobile App
Because the REDCap Mobile App synchronizes asynchronously with the central database, instruments must be configured carefully before moving the project to Production status:
- Enable the Mobile App Module and Configure User Rights: In the central REDCap project sidebar, open
User Rights, select the field coordinator’s username, and check the box forREDCap Mobile App. Decide whether to checkAllow user to download data for all records to the app?:- For cross-sectional single-visit studies or high-sensitivity ePHI cohorts, uncheck record downloading so that stolen or lost tablets contain only blank forms and newly collected records—never the entire study cohort.
- For longitudinal multi-visit studies where field workers need prior visit values to populate branching logic, assign the user to a site-specific Data Access Group (DAG) so the app downloads only records belonging to that coordinator’s assigned clinic or village.
- Generate the API Token and Scan the Initialization QR Code: Navigate to the
REDCap Mobile Applink in the left project menu, request or create the user’s API token, and display the on-screen QR Code (or copy the temporary 10-character initialization code if the server does not have direct internet routing). On the tablet, log into the local app profile, tapSet Up Mobile Project, and scan the QR code. - Test Branching Logic, Calculated Fields, and Action Tags Offline: While the REDCap Mobile App supports standard branching logic, calculated fields, matrix fields, signature fields, and file uploads, it does not execute server-side External Modules, live SQL queries (`sql` field type), or real-time Clinical Data Pull (CDP) calls while offline. Validate every instrument on the physical tablet in airplane mode before deploying to field sites.
- Execute the Daily Synchronization Protocol (`Send Data to Server` & `Secure Send`): When field staff return to connectivity, they tap
Send Data to Server.- If two tablets collected new participants offline using overlapping auto-numbered Record IDs (e.g., both tablets created Record
105offline), the app automatically detects the collision during sync and appends or increments the new Record ID on the server rather than overwriting existing participant data. - If an existing longitudinal record was modified both on the server and on the tablet, the app presents a field-by-field comparison screen allowing the coordinator to choose whether to upload the tablet values or retain the server values.
- If a tablet cannot reach the server over the network, the app provides an Emergency Data Dump option that exports an encrypted CSV/ZIP backup package for manual administrator import.
- If two tablets collected new participants offline using overlapping auto-numbered Record IDs (e.g., both tablets created Record
What Standards or Regulatory Requirements Govern REDCap Mobile App?
Clinical trials and healthcare epidemiological studies using the REDCap Mobile App must enforce mobile device management (MDM) and data governance controls aligned with federal regulations:
- HIPAA Security Rule (45 CFR § 164.312(a)(2)(iv) & § 164.310(d)(1)): Under HIPAA technical and physical safeguards for portable workstations collecting electronic Protected Health Information (ePHI), the REDCap Mobile App encrypts its local SQLite database using AES-256 encryption, enforces role-based PIN authentication with automatic lockouts after failed login attempts, and allows administrators to remotely revoke the user’s REDCap API token (`Delete/Revoke Mobile App API Token`) so a lost or compromised tablet is immediately blocked from pulling or pushing server data.
- FDA 21 CFR Part 11 (Electronic Records; Electronic Signatures): For IND/IDE clinical investigations, the REDCap Mobile App records a local device audit log capturing the authenticated mobile user, timestamp, record ID, and data values created or modified offline. Upon synchronization, this local log is transmitted to the central REDCap
Loggingtable, preserving an immutable, time-sequenced audit trail from offline point-of-capture to central database lock. - Data Minimization and Local Identifier Stripping: Best-practice IRB protocols configure the project’s Data Dictionary so that direct HIPAA identifiers (full name, street address, medical record number) are either excluded from offline download via `Identifier` field tags or confined to a separate registration instrument that is not enabled for mobile download.
How Does REDCap Mobile App Integrate with EHR and Health Informatics Workflows?
In hybrid clinical trials that combine hospital EHR data with community or home follow-up visits, the REDCap Mobile App operates alongside REDCap’s HL7 FHIR interoperability services:
- Central Server Clinical Data Pull (CDP) & FHIR R4 Pre-Population: While the mobile app itself operates offline without direct EHR connectivity, the central REDCap server can pull baseline demographics, laboratory values, and problem lists from the health system’s EHR (such as Epic or Oracle Health) via REDCap Clinical Data Pull (CDP) on SMART on FHIR. When the coordinator runs
Refresh Setup & Dataon the tablet prior to leaving the hospital for home visits, those EHR-populated baseline fields are downloaded into the encrypted mobile project container. - CDISC ODM XML and API Analytics Pipelines: Once field tablets synchronize their offline data back to the central REDCap database, the uploaded records immediately become queryable via the standard REDCap REST API (`exportRecords`) and exportable in CDISC Operational Data Model (ODM) XML, SAS, R, Stata, or SPSS formats for biostatistical and Data and Safety Monitoring Board (DSMB) review.
Frequently Asked Questions
What is REDCap Mobile App and how is it used in clinical research and healthcare?
The REDCap Mobile App is a staff-facing iOS and Android application developed by Vanderbilt University (Harris et al., JAMIA Open, 2021) that enables offline electronic data capture for clinical research and field epidemiology in regions with poor or no internet connectivity. Coordinators initialize a project via a QR-encoded API token, collect discrete form responses, e-consent signatures, and media offline in an AES-256 encrypted local database, and synchronize records back to the central REDCap server when connectivity returns.
What standards or regulatory requirements govern REDCap Mobile App?
Use of the REDCap Mobile App in human subjects research is governed by the HIPAA Security Rule (45 CFR § 164.312 encryption and access controls; § 164.310 workstation/device safeguards), FDA 21 CFR Part 11 electronic record and audit trail requirements, and institutional IRB data minimization policies enforced via REDCap User Rights, Data Access Groups (DAGs), and remote API token revocation.
How does REDCap Mobile App integrate with EHR and health informatics workflows?
The REDCap Mobile App integrates with health informatics workflows through the central REDCap server: baseline EHR data imported via HL7 FHIR R4 Clinical Data Pull (CDP) can be synced to field tablets before offline home visits, and field-collected records synced back from the app are logged in the central audit trail and exported via the REDCap API or CDISC ODM XML.
Sources
- Harris PA, Delacqua G, Taylor R, Pearson S, Fernandez M, Duda SN — The REDCap Mobile Application: a data collection platform for research in regions or situations with internet scarcity, JAMIA Open (2021; PMC8440097): https://pmc.ncbi.nlm.nih.gov/articles/PMC8440097/
- Vanderbilt University REDCap Consortium — REDCap Mobile App Technical Overview and Documentation: https://projectredcap.org/software/mobile-app/







