Exporting to Synapse
Your study can be configured to automatically export health data to Synapse. This document covers how to configure your study, export your data, and understand your data in Synapse.
If your study is already configured to export to Synapse, you can skip to Exporting Your Data. To determine if your study is configured, use the get Bridge App API to retrieve your app configuration. If the
synapseProjectId fields are set, you're good to go.
If these aren't filled out, you'll need to create a Project and a Team in Synapse. You will need to give BridgeExporter administrator permissions, so that this account can create tables and manage their permissions. To do this:
- Browse to the home page of your Synapse project.
- Click "Share".
- Under "Add People", type in BridgeExporter.
- Select BridgeExporter from the auto-complete list that pops up.
- BridgeExporter should be added to the list of people at the top of the popup. On the right, there's a dropdown. Click on the dropdown and select "Administrator".
- Optionally uncheck "Notify people via email". BridgeExporter is an automated account, and as such, any email would just be ignored.
- Click "Save".
You don't need to do anything special for the Team. By default, you become the Team Manager when you create the team. If people need access to the Synapse tables, you should add them to this team. To do this:
- Have the team member create a Synapse account. Note their Synapse username.
- Browse to the Team's home page in Synapse.
- On the right hand, click the "Tools" dropdown and click "Invite User".
- Under "User Search", type in the username.
- Click on the user in the auto-complete list that pops up.
- Click "Send Invitation".
- Next time they log into their Synapse account, they should have the option to accept the invitation and join your Team.
Lastly, you may want to add the Team to the Project, so that your team members can view other content in your Project (such as Wiki, Files, etc). To do this:
- Browse to the home page of your Synapse project.
- Click "Share".
- Under "Add People", type in the name of your Team.
- Select the Team from the auto-complete list that pops up.
- Your Team should be added to the list of people at the top of the popup. On the right, there's a dropdown. By default, the dropdown is set to "Can download". Feel free to change this to whatever you deem appropriate. (That said, we do not recommend giving Administrator privileges to such a wide audience.)
- Click "Save".
Configuring Your Study
Note the Synapse ID from the Project you created in the previous step. This can be found in the Project's home page, near the top left. It should look like "syn5611559".
Also note the Team ID from the Team you created in the previous step. This can be found in the Team's URL. For example, if the URL is
https://www.synapse.org/#!Team:3335336, the Team ID is 3335336.
Now update the fields in the App (
synapseDataAccessTeamId fields) and use the App update API to update your app's configuration.
If you need to disable exports to Synapse, you can set the App's
disableExport field to
true and update the app.
Once saved to the server, your study should now be configured to export its data to Synapse.
Exporting Your Data
Bridge automatically exports your study's data to Synapse every night. This export runs nightly at 3am Pacific Local Time and is subject to change without notice. Bridge will export all data from the previous day, using midnight Pacific Local Time as the nightly cutoff.
For example, on October 11th at 3am PDT, Bridge will export data from October 10 12am PDT to October 11 12am PDT to Synapse.
In addition, if you need faster turnaround (either for lab work, or for app development and QA), you can trigger an On-Demand Export (not currently documented through our Swagger file). (Note that because of clock skew and asynchronous processing, if you submit health data, and then immediately press the Export Now button, the Export may begin before the health data is processed.)
The On-Demand Export feature remembers the last time data was exported for this study (either a nightly export or the On-Demand Export) and only exports data that has been submitted since then. As such, you don't have to worry about double-exporting anything with the Export Now feature.
Understanding Your Data
Bridge exports your data to Synapse as tables. To find them, navigate to your Project in Synapse and click on the Tables tab.
Bridge creates 4 different types of tables in your Project:
- Health Data Summary Table, previously known as the appVersion table. This table contains a summary of all health data exported to Synapse. Each health data record is a single row in this table. This table is best used for statistics, reporting, and general health checks.
- Individual health data tables. Bridge creates a table for each revision of each schema. These tables contain the submitted health data. Each health data record is a single row in one of these tables.
- Default Health Data Record Table. This is used for health data records that do not correspond to any particular schema (or for records whose schemas could not be found). Each health data record is a single row in this table.
- Study status table. Each export job (nightly or on-demand) appends a row to this table. This is used for advanced features not covered in this doc.
Both the summary table and the health data tables contain a set of common fields:
|Unique ID for this health data record.
|App version, as reported by the app. Generally in the form "version 1.0.2, build 12".
|Phone information, as reported by the app. Generally contains phone hardware information and OS information.
|Calendar date (Pacific Local Time) when the data was exported to Synapse.
|De-identified code, which uniquely represents an individual participant in this study.
|External ID, a unique ID for each individual, defined and set by the apps and managed outside of Bridge. This field is app-specific and may not be filled out in each table.
|Comma-separated list of data groups. Can be used for tagging test users or study subpopulations.
|When the health data was measured, as reported by the app. This is displayed in the Synapse Web UI in your local time zone, but is stored externally as epoch milliseconds and does not contain any inherent time zone information.
|The participant's time zone, at the moment this data was measured, as reported by the app. This time zone is a string representation of a UTC offset. Combine this with createdOn to get a date-time with time zone information.
|Participant's sharing scope, representing what level of sharing they have consented to. The two possible values are:
|Error messages indicating that this health data record failed validation. For example, the record may have missing required fields, may have fields of the wrong type, or may have multiple-choice answers that are not allowed.
|NOTE: Studies were previously known as substudies, and for backwards compatability, this field name is maintained in the exported research data. A mapping from study ID to the participant's external ID. If the participant is not in that study, there will be no entry for that particular study. A user might be in a study without an external ID. The data is in the format "|[substudyId1]=[externalId1]|[substudyId2]=[externalId2]|".
The Health Data Summary Table (previously called the appVersion table) includes one additional field:
|Name of the table that contains the health data record this row is referencing.
Health Data Tables
Some fields in the health data tables are file handles (attachments). In the Synapse Web UI, these are displayed as links, which allow you to download the attached file. In the Synapse API or through the R, Python, or Java clients, these are file handle IDs, and require a separate call to Synapse to download the attached files.
Lastly, every row in the health data tables also includes a rawData field, which includes a link to the raw JSON or zip file submitted by the client, and a rawMetadata field, which includes all metadata submitted by the client app.
Default Health Data Record Table
This table also includes the same common fields, health data metadata fields, raw data, and raw metadata fields as health data tables. The key difference is that records in this table do not correspond to any schema (or to non-existent schemas).