After downloading exported data from MyDataHelps Designer, you will have a number of data files in either Comma-Separated Value (CSV) or JSON format. Each file contains data from a single project. This article summarizes the data files and how to use them.
Data exports may contain Protected Health Information (PHI), Personally Identifiable Information (PII), and/or other health-related sensitive information, and must be transferred/stored in accordance with your organization’s security policies in order to ensure participant privacy and data security.
Table of Contents
Data Files
The following tables describe the data files, and indicate whether they are available in the JSON export, the CSV export, or both. You can select the export format in your project's data export settings.
Survey and Participant Data
File Name | JSON Available? | CSV Available? | Description |
AllParticipants | ✓ | ✓ | Information about all participants who have joined the project, including both analog and enrolled participants. |
EnrolledParticipants | ✓ | ✓ |
Information about participants who have enrolled in the project via MyDataHelps. Note: This is a legacy export, no longer available to new projects. |
SurveyResults | ✓ | ✓ |
Information about each completed survey. In the JSON export, this file includes step and question results, consent signatures, and task results. |
SurveyStepResults | see description | ✓ |
Detailed results for every step the participant completed in a survey. In the JSON export, this data is contained in the SurveyResults file. |
SurveyQuestionResults | see description | ✓ |
Detailed results for question and form step responses from completed surveys. In the JSON export, this data is contained in the SurveyResults file. |
SurveyConsentSignatureResults | see description | ✓ |
Detailed results for consent review step responses.cIn the JSON export, this data is contained in the SurveyResults file. |
SurveyTasks | ✓ | ✓ |
Lists all survey tasks delivered to participants and their completion status. |
AuxiliaryData | ✓ | ✓ |
Auxiliary data files uploaded to individual participants. |
SurveyDefinitions | ✓ | ✓ |
All versions of all surveys in the organization. |
Active Task Data
File Name | JSON Available? | CSV Available? | Description |
HolePegTest | see note below | ✓ | Detailed results from Hole Peg Test active tasks. |
RangeOfMotion | see note below | ✓ | Detailed results from Range of Motion active tasks. |
SpatialSpanMemory | see note below | ✓ | Detailed results from Spatial Span Memory active tasks. |
SurveyPSATResults | see note below | ✓ |
Detailed results from Paced Serial Addition Test (PSAT) active tasks. |
SurveyTrailmakingResults | see note below | ✓ |
Detailed results from Trailmaking active tasks. |
SurveyStroopResults | see note below | ✓ |
Detailed results from Stroop active tasks. |
SurveyNormalizedReactionTimeResults | see note below | ✓ |
Detailed results from Normalized Reaction Time active tasks. |
SurveyTappingIntervalResults | see note below | ✓ |
Detailed results from Tapping Interval active tasks. |
TimedWalk | see note below | ✓ |
Detailed results from Timed Walk active tasks. |
ToneAudiometry | see note below | ✓ |
Detailed results from Tone Audiometry active tasks. |
TowerOfHanoi | see note below | ✓ |
Detailed results from Tower of Hanoi active tasks. |
When your project uses the CSV export format for Survey Results, data for Active Tasks is exported in separate data files, organized by task type. When your project uses the JSON export format, Active Task data is included in the SurveyResults file.
Apple Device/Wearable Data
File Name | JSON Available? | CSV Available? | Description |
AppleLocationVisits | ✓ | ✓ |
Locations that participants have visited. |
HealthKitCharacteristics | ✓ | ✓ |
Participant characteristics from Apple HealthKit data that do not typically change over time, like date of birth. |
HealthKitSamples | ✓ | ✓ |
Simple quantity or category samples from Apple HealthKit data, like Heart Rate or Sleep Analysis. |
HealthKitActivitySummaries | ✓ | ✓ |
Activity summary data from Apple HealthKit data captured by the Apple Watch. |
HealthKitWorkouts | ✓ | ✓ |
Participant workout data from Apple HealthKit, if they track their workouts using an app or device. |
HealthKitWorkoutEvents | see description | ✓ |
Detailed brewdown of participant workout data. In the JSON export, this data is contained in the HealthKitWorkouts file. |
HealthKitClinicalData | ✓ |
Participant clinical data from Apple HealthKit, if they have linked Apple Health to their provider's Electronic Medical Record (EMR) system. |
FitBit Device/Wearable Data
File Name | JSON Available? | CSV Available? | Description |
FitbitProfiles | ✓ | ✓ | User profile and preferences. |
FitbitDevices | ✓ | ✓ | Devices used by participants. |
FitbitDailyData | ✓ | ✓ | Daily summary of a variety of activity and heart rate data. |
FitbitActivityLogs | ✓ | ✓ | Participant activity details. |
FitbitRestingHeartRates | ✓ | ✓ | Daily participant resting heart rates. |
FitbitSleepLogs | ✓ | ✓ | Daily summary of participant sleep patterns. |
FitbitSleepLogDetails | see description | ✓ |
Detailed breakdown of participant sleep patterns. In the JSON export, this data is contained in the FitBitSleepLogs file. |
Google Fit Device/Wearable Data
File Name | JSON Available? | CSV Available? | Description |
Google Fit | ✓ | ✓ | Health and activity data. |
Geographic Data
File Name | JSON Available? | CSV Available? | Description |
WeatherData | ✓ | ✓ | Daily weather forecast. |
AirQualityIndexData | ✓ | ✓ | Daily air quality index. |
CSV Column Names
As new fields are added to MyDataHelps Designer or to the sensor data services, those fields may be added to the data export files as well. Always use the column headers (the first line of each CSV file) to identify which fields appear in each column. The column header names will remain the same even if the column order changes or new columns are added.
Associating Data Between Files
Whether you're using JSON or CSV exports, your project data will be spread out across multiple files. Identifiers aid you in cross-referencing data between these files.
Cross-Referencing Participant Data
The participants file lists all participants. In addition to their names, birthdates, etc., the participant is given a unique Participant Identifier. You'll find this same Participant Identifier referenced in other data files - survey results, sensor data, etc.
For example, consider this sample participant data. Chris Smith has Participant Identifier 81a5ca06-6bdb-423e-9ed7-49d81aa4be2a:
ParticipantIdentifier,GlobalKey,EmailAddress,FirstName,MiddleName,LastName,Gender,DateOfBirth,SecondaryIdentifier,EnrollmentDate,EventDates 81a5ca06-6bdb-423e-9ed7-49d81aa4be2a,5be1902c-e9d9-e711-815b-b9576bf93116,chris@example.com,Chris,,Smith,,1987-08-14,,2017-12-05T18:25:59Z,{}
When we look at the survey results data, we'll see that this result entry is also from participant 81a5ca06-6bdb-423e-9ed7-49d81aa4be2a, so we know it's from Chris.
SurveyResultKey,SurveyKey,SurveyName,SurveyVersion,ParticipantIdentifier,SurveyTaskKey,Type,StartDate,EndDate,DevicePlatform,DeviceName,DeviceOSVersion,InsertedDate 73b25dbd-e9d9-e711-815b-b9576bf93116,dcbede15-67c9-e711-815a-a2abfc96a420,Consent,0,81a5ca06-6bdb-423e-9ed7-49d81aa4be2a,,Consent,2017-12-05T13:25:47-05:00,2017-12-05T13:25:58-05:00,iOS,"iPhone7,1",10.0,2017-12-05T18:25:59Z
We can also find Chris in the survey tasks data, to see which survey tasks he's been assigned and whether they're completed. This will help you measure survey adherence.
SurveyTaskKey,ParticipantIdentifier,SurveyKey,SurveyName,Status,DueDate,InsertedDate,CreatedBy,ModifiedDate
9bb25dbd-e9d9-e711-815b-b9576bf93116,81a5ca06-6bdb-423e-9ed7-49d81aa4be2a,059966f9-e3a7-e711-8159-cb0f82935acb,Medical History: Cardiovascular Diagnoses,Incomplete,2017-12-19T18:26:00Z,2017-12-05T18:26:00Z,MyDataHelps Designer Survey Scheduler,2017-12-05T18:26:00Z
Cross-Referencing Survey Data
Survey results are also linked together with cross-reference keys. The following table shows how you can associate data from different survey result files.
Survey | SurveyResult | SurveyStepResult | SurveyQuestionResult | |||
SurveyKey | ⇄ | SurveyKey | ||||
SurveyResultKey | ⇄ | SurveyResultKey | ||||
SurveyStepResultKey | ⇄ | SurveyStepResultKey | ||||
SurveyQuestionResultKey |