...
Alert: An automatically generated message sent to the study team that can be set up to monitor for rapid or extreme changes in a participant's data that may be of clinical significance or a sign of an adverse event.
Alert Message: Messaging event (formerly known as an 'encounter') that is sent to a participant based on their notification preference and is visible on the participant dashboard.
...
Commit number: A link to the code revision in our code versioning tools, e.g. r8849.
Completed: A status for an event (formerly known as an 'encounter') in which the participant or study staff fulfill the requirements of the encounter event (i.e. sync Fitbit, fill out a survey, etc.) and it closes out immediately or at the end of the encounter windowevent window (formerly known as an 'Encounter Window').
Compliant: A status for an event (formerly known as an 'encounter') that is both complete and meets specific parameters built in feedback, like a goal or target.
...
Device: a source of participant data that can come from one of two origins, (1) a tangible device, such as a pedometer or wireless scale, or (2) a non-Qualtrics survey, such as pre-commitment, goal selection, or Twilio bi-directional.
Device Upload: an event (formerly known as an 'encounter') type that looks for participant data from a specified device source and runs feedback based on a participant's completion or compliance, often linked to a target, on the encounterevent.
Disable Feedback: Turns off automatically generated feedback to a participant or partner on an individual or study level. Feedback will be marked as applied even though none of it is actually evaluated. When feedback is reenabled, the participant will not receive feedback. See Pause Feedback.
Event (formerly known as an 'Encounter'): represents a specific action a participant or the system needs to complete, like a lottery, or taking a medication.
Event Window (formerly known as an 'Encounter Window'): the duration of time in which an event (formerly known as an 'encounter') must be completed.
Enrollment Block: A time-bound set of encounters within events (formerly known as an 'encounters') within enrollment.
Enrollment Step: a step a participant must compete during the enrollment process.
Feedback: Configurable actions that the system takes in response to an event (formerly known as an 'encounter')
Feedback Consequence: an action the system takes after evaluating the specified criteria, such as sending a message or paying a participant.
...
Frontend: Interactive participant-facing website comprised of the welcome screen, enrollment and participant dashboard
Filter Events (formerly known as an 'Filter Encounters'): a page in the admin site where admin user can search for and edit encounters event (formerly known as an 'encounter')s (e.g. reapplying feedback)
...
Incident: There are 2 types of incidents. They can be automatically generated by WTH for issues with a device event (formerly known as an 'encounter') or a participant, or added manually by study staff to document relevant information on a particular participant.
...
Local environment: A version of WTH running on a developer's computer. Code can be changed here quickly, but it needs to be saved ("committed") to our code repository and deployed to a server before it's visible to any users.
Lottery: a type of event (formerly known as an 'encounter') that represents a lottery winning for participants.
...
Notification: Any message sent from Way to Health. Could be manually or automatically generated, and sent to a participant or RC.
Office Visit: A type of event (formerly known as an 'encounter') that enables a survey that is only visible to and able to be manually completed by study staff, which is unlike a survey encounter that event that a participant can view and complete.
...
Provider: A study staff permission that restricts a user's access to only a group of participants assigned to an Access Group to which they have permission to see. A provider can view participant information, events (formerly known as an 'encounters'), transactions, and data only for those in their assigned Access Group. A provider cannot view Manage Study and therefore typically only supports study management.
RC (Research Coordinator): Member of the study team who aids in study enrollment, maintains study platform, and acts as a point of contact for study participants.
Round Up: An event (formerly known as an 'encounter') that looks at previous encounters for events for completion and/or compliance and then applies feedback to the participant
...
Transaction: represents a payment to a participant generated by feedback that must be approved by the study staff.
Schedule: Composition of encounters event (formerly known as an 'encounter')s that is unique for each study arm.
Skipped: An event (formerly known as an 'encounter') status for when an encounter window event window has ended, but the encounter was event was not completed.
Staging: The server environment that replicates the production environment as closely as possible, often used for testing.
...
Survey: A series of questions a participant must answer, provided via integration with Qualtrics. Surveys can be administered either during enrollment or the intervention period, and can be completed by the participant himself or on the backend by study staff.
Survey Lookback: An event (formerly known as an 'encounter') type that evaluates a participant's response to an previously administered survey and sends feedback based on the various response choices. This allows you to send tailored feedback only to the participants for which the information is relevant.
...
Ummon: the scheduler tool for WayToHeath background tasks
Variable: In an event (formerly known as an 'encounter') message, a variable auto-populates unique information about a specific participant or encounterevent.