Export Explorer
Export Explorer lets you query a consolidated database of all your project’s standard data exports, either by writing SQL or by asking questions in plain language. You can also connect an external data analysis application directly to your project’s export database.
These features will be available once exports have been set up for your project and the first file has been generated. Get started by navigating to the Export Explorer tab in your project.
In addition to this article, we strongly recommend visiting the MyDataHelps Data Guide, a GitHub repository with example notebooks and queries for making the most of the MyDataHelps export database.
Query Tab
The Query tab supports Amazon Athena SQL version 2, which has many functions available to help you query your data. To get started, write a SQL select statement and click “Run.” This will execute your query and show the results.
The following sections explore the various components of the Query tab.
Tabbed Queries
You can create different tabs with different queries and results, quickly toggling between them. Select "+" at the top of query window to create new query tabs. Click "x" to close them.
Format SQL
Click the Format SQL button to quickly auto-format your SQL query.
Save
Click the Save button to save your query to run again. You can provide a Name, Category, and Description. Additionally, you can elect to make the report available on the Reporting tab.

After saving, the query will be available under the Queries tab in the right sidebar.
If you want to make any edits to your query, you can click Save again to overwrite it or Edit Settings to adjust the Name, Category, and Description.

Query Library
The Query Library contains common queries focused on participant and project management.
Query Copilot
Query Copilot uses AI to help you use the Export Explorer—no SQL experience necessary. Ask your project data questions in plain English and it will return SQL queries for you to run.
- Copilot does not have access to participant data or query results.
- Be as specific as possible in your prompts. Specify the exact name of a survey and for wearable data, specify the data source (e.g., Fitbit).
- After copilot generates a query, you need to click “Run”.
- Export Explorer results are only up to date as of your last export.
You can try some of the following example Query Copilot prompts:
- How many participants completed “Baseline_Survey”?
- Give me a list of all participant survey tasks, their delivery dates, and completed dates.
- How many participants have connected a Fitbit, and of those participants, how many have sleep data?
- Show me the number of participants who have any mention of ‘diabetes’ in their EMR data, grouped and sorted by age decade.
Database Structure
This tab shows the database tables available in your project. Any of the tables in this schema can be used in a from statement, and clicking on a table or its columns will insert it into your editor window. Expanding a table will reveal the columns in the table along with the columns’ data types.
All timestamps in Export Explorer are in UTC. Timestamps originally recorded in local participant time such as survey start and end dates will include an associated `{timestamp}recordedoffset` field denoting the offset from UTC when recorded.

The default example query in the editor is only an example and may not work for all projects. While many projects export the allparticipants model, the query will fail if the table is not present in your project’s database schema.
In addition to the columns documented on data exports, each table contains a _provenance column, which contains metadata about every record. This metadata includes information about the origination of the record, including the source export identifier and date range.
Processing History
In addition to the tables containing data from exports, the export database provides a history of all exports processed. This table is named processing_history and can be found alongside other tables.
This table contains a row representing each time any export model is successfully updated in the database. Its natural key is the tuple of model_key and modified_time. A meaningful surrogate key is model_key, processed_key, and lock_time.
It is insufficient to use model_key and processed_key as the natural key of this table because the export database may process an export more than one time.
| Field Name | Data Type | Description |
|---|---|---|
project |
string | The unique code identifier for your project. |
model_key |
string | The name of the model. |
modified_time |
timestamp (utc) | The time this record was generated. This is approximately the time that the database finished processing a particular export (processed_key). |
lock_time |
timestamp (utc) | When a database processor works through an export, it obtains a globally-unique lock for each model it is working on. This field represents the time that lock was obtained. The maximum modified_time for a lock_time is approximately the time the lock was released. |
application |
string | A unique identifier for an instance of a database task processor. This can be used to indicate how much work a task was able to accomplish. |
version |
string | The version of the export database code used by the processing task. |
processed_key_time |
timestamp (utc) | The file modification time of the processed export (processed_key). This is approximately the time that the MyDataHelps export service compiled the export and made it available for download. |
processed_key |
string | A unique identifier for the processed export. |
export_start_date |
timestamp (utc) |
The start date recorded in the manifest of the processed export. |
export_end_date |
timestamp (utc) | The end date recorded in the manifest of the processed export. |
excluded_participants |
list of strings | The list of participant identifiers declared as excluded participants according to the manifest of the processed export. |
configuration |
string | The configuration of this export as indicated in the manifest of the processed export. |
manifest |
map of strings | Remaining export manifest entries not otherwise recorded in this table. The keys of this map are generally the same as values of the model_key column and represent models as declared by the MDH export service. |
export_files |
list of strings | A full list of files within this processed export. Entries are listed relative to the root of the export zip. |
Ask Tab
The Ask tab is available to all projects for a limited time as a beta feature.
This tab lets you ask questions about your data and returns a table, chart, and SQL query. Use the right side panel to ask your question(s).
Click "New session" to start a new session on the Ask panel or revisit your previous sessions via the "History" dropdown at any time. All new sessions display suggested prompts to get started.
Additionally, you can run existing queries from the following dropdowns:
- Saved queries: Access your saved queries from both the Query and Ask tabs.
- Library: Access pre-built SQL queries to run.
You can edit the generated SQL directly from the SQL view, and click "Run" to generate a new table and chart from that SQL.
Once you're satisfied with your query, you can:
- Download CSV: Download the current results as a CSV file.
- Save query: Saves the current query as a new query, which will be available on both the Query and Ask tabs.
External Connection Tab
There are two ways to connect your project's export database to an external data analysis application such as PowerBI, Tableau, RStudio, or Jupyter Notebooks:
- If you need persistent access to the database, you can use a Service Account and custom code to facilitate automated data processes.
- If you only need short-term or occasional access, or are unable to maintain custom code, you can use an AWS IAM profile with ODBC or JDBC Amazon Athena libraries.
For specific instructions on how to create an external connection, navigate to the External Connection tab at the top of the Export Explorer tab within your project and select the connection method you prefer.
Troubleshooting
See Export Explorer: Troubleshooting article for more details on troubleshooting the Export Explorer.