Filter criteria allow you to further define which participants should belong in a specific segment or for which participants a schedule should trigger. There are several types to choose from, and within many of the criteria types, there are specific values to further define.
Additionally, when defining filter criteria, you may combine criteria using “and” and “or” logic, or reverse the meaning by selecting “not.” The table below lists each criteria type, and the following sections explore each type in more detail.
| Criteria Type | Filtering Capability |
|---|---|
| Identifier |
Filter based on Participant Identifier or Secondary Identifier. |
| Demographic Field |
Filter based on the values for specific demographic fields, such as Age or State. |
| Custom Fields | Filter based on the values for specific custom fields, e.g., SurgeryDate or Cohort. |
| Is Enrolled | Filter for participants who are enrolled in the project, meaning they have created a MyDataHelps account and completed the enrollment survey for the project. |
| Enrollment Date | Filter based on the enrollment date of the participant, e.g., participants enrolled on or before December 31, 2022. |
|
Filter based on the creation date of the participant, where creation date is when the participant information first appears in MyDataHelps/Designer. |
|
| Filter based on the invitation status of the participant, if applicable. | |
| Filter based on a survey answer, which is created any time a participant completes a survey, e.g., participants who answered that they would like to receive notifications. | |
| Survey Task | Filter based on a survey task, which is created when a survey is delivered to a participant, e.g., participants who have an Incomplete Baseline Survey task. |
| Filter based on the platform the participants uses, e.g., participants who utilize the iOS platform. | |
| Filter for participants based on their linked accounts, where a linked account could be a provider, health plan, or device manufacturer. | |
| Filter for participants based on their Fitbit characteristics, such as device type, battery, last sync date, or device version. |
Identifier
The Identifier criteria type allows you to filter either based on Participant Identifier (PID) or Secondary Identifier.
If you have an external list of PIDs you’d like to filter for, you can select the “In” option, and paste the list into a text box.
Demographic & Custom Fields
The Demographic Field criteria type allows you to filter based on the following demographic information:
- Age
- Gender
- Name (First, Middle, Last)
- Phone
- Address (Street, City, State, Postal Code)
- Preferred Language
For example, you may wish to filter for participants who are 65 years or older.
Similar to filtering on demographic information, you can also filter on custom fields. The options available will depend on what custom fields you have previously configured for your project. For example, if you had a custom field for participant cohort, you could filter for participants in a specific cohort.
Enrollment, Creation, and Invitation Status
The Enrollment and Creation criteria types allow you to filter based on when the participant was created in MyDataHelps and if/when they enrolled. The Invitation Status criteria type allows you to filter for participants based on their invitation status.
In some cases the Creation Date will be the same as the Enrollment Date (e.g., enroll by search or complete a new participant survey). However, if the participant is added to MyDataHelps Designer by the study team before enrolling (e.g., enroll via invitation), they may differ.
For example, you could filter for participants who have been invited (invitation status is “Pending”) but not enrolled.
Survey Answer and Survey Task
Survey Answers are generated when a participant completes a survey. Once submitted, the responses are available in MyDataHelps Designer. Survey Tasks, however, are created when a survey is delivered to a participant (via schedule, custom field actions, or manually), and the purpose is to track the delivery, due date, and status of the survey.
Survey Answer criteria evaluate for specific details around the survey response, while Survey Task criteria focus more on the logistics of the survey delivery.
Survey Answer
The Survey Answer criteria type allows you to filter based on the following details:
- Answer: Looks for any survey answer matching the conditions specified.
- Result Identifier: Looks for the survey question matching the conditions specified. This is helpful to include if looking for an answer to a specific question within a Form Step. If the survey question is in a Question Step, the result identifier will have the naming convention: Question_Step Identifier. If the question is in a Form Step, this will have the naming convention: Question_Form Item Identifier.
- Step Identifier: Looks for the survey step identifier matching the conditions specified.
- Timestamp: The time the survey was submitted according to the participant’s device.
- Inserted Date: The date the system received the survey answer.
- Surveys: Looks for any answer submitted for the survey(s) specified.
If you do not specify the “Surveys” criteria, all existing survey answers will be evaluated (for example, this could mean Baseline survey, Mood survey, and any others completed by participants). Make sure to be as specific as necessary when defining criteria!
Oftentimes, you will want to combine the criteria above. For example, you could look for all participants who submitted a mood survey within the last week.
The Survey Task criteria is not able to filter on submission date, so Survey Answer criteria can be used as a proxy to determine whether a participant has submitted a survey within a certain timeframe (or at all).
When filtering based on a Survey Answer, you will want to use a combination of filter criteria to pinpoint the precise survey and step. For example, you could filter for a response of “Yes” on the Mood survey step that asks about whether the participant would like to be followed up with.
Survey Task
The Survey Task criteria type allows you to filter based on the following details:
- Surveys: Looks for any survey tasks associated with the survey specified.
- Task Status: Looks for any survey tasks with the status specified.
- Creation Date: The date the survey task was delivered to the participant.
- Due Date: The date the survey task is due.
If you do not specify the “Surveys” criteria, all existing survey tasks will be evaluated (for example, this could mean Baseline survey, Mood survey, and any others delivered to participants). Make sure to be as specific as necessary when defining criteria!
The criteria mentioned above can be combined. For example, you could look for all participants with an incomplete Baseline Survey that is due within the next week.
App Platform
The App Platform criteria type allows you to filter based on the platform the participants uses, either by evaluating any device the participant has signed in on or the most recent device they signed in on. You can filter on the following details:
- Platform: Looks for the platform type that was signed into, e.g., Android, iOS, or Web.
- Property: Looks for the platform property matching the conditions specified. See the tables below for a list of the properties available by platform.
- Last Usage: The date of the most recent participant login.
For example, you may wish to filter for participants who have logged into the Android or iOS platforms (meaning, they have logged in using the mobile app as opposed to web).
If viewing a specific participant, this information can be found in the Participant Viewer under Support > Devices.
Android Properties
Android properties include, but are not limited to:
- AppVersion
- DeviceType
- HardwareModel
- NativeResolution
- AndroidVersion
- AppName
- Resolution
iOS Properties
iOS properties include, but are not limited to:
- LastHealthKitFullSyncDate
- SensorKitDeviceUsageReportAuthorizationStatus
- AppVersion
- NativeResolution
- LastWatchAppLaunchTimestamp
- AppName
- WatchOSVersion
- LocationAuthorizationStatus
- NotificationAlertSetting
- WatchWristLocation
- IOSVersion
- HardwareModel
- MovementDisorderStatus
- HasPairedAppleWatch
- TextingCapability
- LocationAccuracyAuthorizationStatus
- NotificationBadgeSetting
- NotificationAuthorizationStatus
- WatchHardwareModel
- Resolution
- NotificationSoundSetting
- DeviceType
Web Properties
Web properties include, but are not limited to:
- Browser
- BrowserVersion
- OperatingSystem
- Resolution
Linked Accounts
The Linked Accounts criteria type allows you to filter for participants based on whether they’ve connected their MyDataHelps account to a provider, health plan, or device manufacturer. You can filter based on the following details:
- Providers: Looks for the specific name of the linked account (e.g., “Anthem”, “Michigan Medicine”). You can search for and select multiple providers for this criteria.
- Category: Looks for a linked account with a category of Provider, Health Plan, or Device Manufacturer.
- Status: Looks for a linked account with a Connected or Needs Reconnect.
For example, if your project has enabled EHR Sharing, you could filter for all participants with a connected provider.
Fitbit Device
The Fitbit Device criteria type allows you to filter for participants based on their Fitbit characteristics, including the following:
- Device Type: Looks for a Tracker or Scale device type.
- Battery: Looks for a device with the battery level specified (High, Medium, Low, or Empty).
- Last Sync: The last time the Fitbit device was synced to MyDataHelps.
- Device Version: Looks for a device with the version conditions specified. You must use the full product name - see Fitbit website for a complete list.
For example, you could filter for all participants whose last Fitbit sync was 10 or more days ago.