Overview

...

1. User calls the upload API to create an upload session, upload a file, and call upload complete to start the upload validation process. (See Bridge REST APIAPI#Pre-signedFileUpload for details.)
   1. The upload itself is (as described in Bridge Upload Data Format) a zip file containing files of a single activity (survey or task), encrypted with the study's public key (aka cert).
2. Upload validation handlers are kicked off. See next section for more details.
3. The Bridge Exporter runs every night at 9am 10am UTC (2am PST / 3am PDT), which exports the previous day's health data records (using uploadDate) to Synapse, creating Synapse tables as appropriate. See details in next section as well as at For more info, see Bridge Exporter Script

Upload Validation Handlers

...

1. Confirm with app developers the field names and types of the data coming in. Examples will be crucial.
2. Create the schema in staging. The easiest way to do this is the copy-paste the example from the previous section and update the name, ID, and fields. (Don't forget to remove revision, as this will be automatically incremented by the server.) Use the REST APIs at Bridge REST APIAPI#UploadSchemas to create this on the server.
3. Ensure the app developers send data to staging. Wait a day for the Bridge Exporter to run (or force a manual run of the Exporter).
4. Confirm with the research team that the data in Synapse is the data they want. Fix issues and repeat if necessary.
5. Once everything looks good, create the schema in prod.

...