MyCap Mobile Application
- A tool for researchers – a customizable participant-facing mobile application freely available to capture patient reported outcomes based on a REDCap project.
- A tool for participants – a centralized study ‘home’ (app) for information and actions that facilitates continuous participant engagement and participant retention. It is available on iOS devices (iOS v11.0+) and Android (v5.0+) at no-cost.
How does MyCap work?
MyCap is a standard feature of REDCap v13.0+. Data is collected from participants through the app via customizable surveys and the automated administration of active tasks (activities performed by participants using mobile device sensors). All data collected in the MyCap App is automatically sent back to the REDCap server as soon as internet connection is available (i.e., it can also be used for offline participant data collection). Frequent data collection is strongly encouraged for MyCap usage.
MyCap also facilitates participant engagement and retention by providing quick access to project staff and secure two-way communication (e.g., messaging and announcements) within the App.
For more information about MyCap, check out the MyCap website, publication, resources, videos, and a list of MyCap use cases.
External Modules
External modules extend existing REDCap functionality in new and creative ways. These modules are not developed by the main REDCap development team at Vanderbilt, instead they are made available by members of the REDCap consortium.
Vanderbilt introduced the concept of external modules in version 8 of REDCap. The following policies ensure that our local GWU REDCap production instance will continue to run smoothly while allowing users to utilize this functionality to the fullest.
Many of the existing external modules will be sufficiently useful for regular REDCap users, however some may only be useful for GWU REDCap administrators.
If you are interested in using an existing external module, please contact the REDCap team at redcap@gwu.edu. Be sure to include the name of the module and the project for which you would like this module implemented. Vanderbilt maintains a repository of available external modules.
All external module requests will be classified by the REDCap support team in one of two categories: Administration and Global.
- Administration External Modules: Modules in this category are restricted to GWU REDCap administrators. The REDCap support team will not implement administration external modules.
- Global External Modules: These will be the everyday use modules. Users can choose from the list accessed via the external modules link above. Users will notify the REDCap team of each module request, for which we will work diligently to assure access to the module(s).
Once an external module has been classified, it can then be implemented. There are three phases of implementation: Installation phase, Enable phase, and Configuration phase.
- Installation phase: Any external module will need to be installed to the GWU REDCap instance only once. Part of this process is to verify that the particular module will work with the GWU installation of REDCap and confirm that it poses no security risks. Once a module is installed, we will make it discoverable in the “External Modules” section of any project. Click on the “Enable a Module” in the “External Modules” section to view all available external modules. These modules will not need to be re-installed and can go straight to the enable phase.
- Enable phase: Installed external modules will need to be enabled for each project separately. Enabling a module must be done by a REDCap administrator. There is no additional charge for enabling a module that has already been installed.
-
Configuration phase: Some external modules will be very simple and will not require any specific configuration. However, as the technology matures, we expect the modules to become exceedingly more complex over time. Once a module is enabled, authorized users in a project should be able to configure the external modules themselves if required. Assistance in configuring a module from a REDCap administrator will be provided as a fee-for-service.
Clinical Data Interoperability Services (CDIS) (Coming Soon)
REDCap can communicate with any EHR (electronic health record system) that has implemented 'SMART on FHIR' web services that allow for interoperability and data extraction from the EHR. In this way, REDCap can be embedded inside and launched within an EHR user interface (e.g., Cerner, Epic Hyperspace). This feature allows REDCap users to easily add patients to their projects and/or to access patient data inside a REDCap project. In addition to launching REDCap inside the EHR, REDCap can also extract data from the EHR to import clinical data into a REDCap project by using a feature called 'Clinical Data Pull' (CDP). CDP provides an adjudication process whereby REDCap users can approve all incoming data from the EHR before the data is officially saved in their REDCap project. Another feature is called 'Clinical Data Mart' which works differently than CDP in that the Data Mart can pull patient information in bulk while CDP pulls patient information from the EHR just one patient at a time. To learn their differences and strengths, see the sections below for documentation.
GWU E-Consent Tools
eConsent for research is available using REDCap. You can use eConsent to conduct and record consent for remote participants or for participants in clinic on computers, tablets, or other touchscreen devices. Participants will be able to sign the consent form electronically with a stylus, mouse, or finger and submit it to the study team. Participants can also electronically type their name for a signature. Once the consent form is submitted, the participant will receive an email that includes a PDF attachment with a copy of their signed consent form.
Can eConsent be used on all projects?
An electronic consent process (eConsent) is allowable on research studies, even for greater-than-minimal-risk studies. The IRB will review the use of eConsent on a study by study basis, considering the details of your proposed consent process, the study population, and the appropriateness of the electronic platform for the study overall.