• In your study folder, go to: (Admin) > Folder > Management and click the Folder Type tab.
• Under Modules, place a checkmark next to REDCap.
• Click Update Folder.

• In your study folder, click the Manage tab.
• Click Manage External Reloading.
• Click Configure REDCap.
• Configure connections and reloading on the three tabs:
• Connection - Use this tab to specify the REDCap server you intend to draw data from. You can also define a recurring schedule to automatically reload the data.
• Datasets - Use this tab to specify import behavior for individual REDCap forms. For example, you can import a given form into LabKey as either a dataset (the default behavior) or as a List. You can specify the timepoint type (visit or date), and additional keys when required.
• Advanced - Use this tab to define advanced configurations using XML.

The information you enter here sets up communication between LabKey Server and a REDCap server (or servers). For each REDCap project you wish to load data from, there must be a separate row of connection information.

• XML Export Format: If your REDCap project supports the CDISC format, confirm that this is checked to proceed. Remove this checkmark if your REDCap project does not support the CDISC format or if you are using a REDCap version before than 6.12. Documentation for the earlier non-CDISC format is available in the documentation archive at REDCap Legacy Import.
• REDCap Server URL: The URL of the target REDCap server. The URL should end with 'api/', for example: https://redcap.myServer.org/api/
• Change Token: Check the box to change the authorization token.
• Token: A hexidecimal value used by the REDCap server to authenticate the identity of LabKey Server as a client. Get the token value from your REDCap server, located on the REDCap API settings page of the project you are exporting from.
• Enable Reloading: (Optional). Place a checkmark here to start reloading on a schedule defined below.
• Load On: Optional. Set the start date for the reloading schedule.
• Repeat (days): Optional. Repeat the reload after this number of days.

• Save: Create a connection to the REDCap server. After clicking Save you can refine the import behavior on the Datasets tab. For details see Medidata / CDISC ODM Integration.
• Reload Now: Loads the data from REDCap on demand.

• Click the Datasets tab to configure study properties and per-dataset import behavior.
• Click the (pencil) icon.

Here you can edit settings including:

• Whether the target study is visit or date based.
• For date based studies, you can specify the name of the column containing the date.
• For visit based studies, you can provide a default sequence number.
• Whether to import all datasets with shared defaults or add per-dataset definitions for:
• Whether the dataset is demographic, clinical, or has a third key.
• Whether it should be imported as a list (instead of a dataset).
• Which column to use as the date field or what the default sequence number should be (if these differ from the study-wide settings on the previous page.

• Study and Dataset Configuration Panel.

Available configuration options are described below:

• serverUrl: Required. The URL of the REDCap server api (https://redcap.test.org/redcap/api/).
• projectName: Required. The name of the REDCap project (used to look up the project token from the netrc file). The projectName must match the project name entered on the Authentication tab.
• subjectId: Required. The field name in the REDCap project that corresponds to LabKey Server's participant id column.
• timepointType: Optional. The timepoint type (possible values are either 'visit' or 'date'), the default value is: 'date'.
• matchSubjectIdByLabel: Optional. Boolean value. If set to true, the import process will interpret 'subjectId' as a regular expression. Useful in situations where there are slight variations in subject id field names across forms in the REDCap project.
• duplicateNamePolicy: Optional. How to handle duplicate forms when exporting from multiple REDCap projects. If the value is set to 'fail' (the default), then the import will fail if duplicate form names are found in the projects. If the value is set to 'merge', then the records from the duplicate forms will be merged into the same dataset in LabKey Server (provided the two forms have an identical set of column names).
• formName: Optional. The name of a REDCap form to import into LabKey Server as a dataset.
• dateField: Optional. The field that holds the date information in the REDCap form.
• demographic: Optional. Boolean value indicating whether the REDCap form will be imported into LabKey Server as a 'demographic' dataset.

Example Configuration File

<red:redcapConfig xmlns:red="http://labkey.org/study/xml/redcapExport">
  <red:projects>
    <red:project>
      <red:serverUrl>https://redcap.test.org/redcap/api/</red:serverUrl>
      <red:projectName>MyCaseReports</red:projectName>
      <red:subjectId>ParticipantId</red:subjectId>
      <red:matchSubjectIdByLabel>true</red:matchSubjectIdByLabel> <!--Optional-->
      <red:demographic>true</red:demographic> <!--Optional-->
      <red:forms>  <!--Optional-->
        <red:form>
          <red:formName>IntakeForm</red:formName>
          <red:dateField>StartDate</red:dateField>
          <red:demographic>true</red:demographic>
        </red:form>
      </red:forms>
    </red:project>
  </red:projects>
  <red:timepointType>visit</red:timepointType> <!--Optional-->
  <red:duplicateNamePolicy>merge</red:duplicateNamePolicy> <!--Optional-->
</red:redcapConfig>