Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Highlights (6.2 and 6.3)

  • New Logic Criteria: Previous Event's Adherence Snapshot CategoryEvaluate based on another event’s category

  • Using Filters for Batch Action Processing

  • Autogenerate Username Creation for Inviting Project Staff

  • Upload Videos to Enrollment and Surveys

  • Manually Updating Participant's Status

  • New Device Integration: Propeller Health Inhaler

  • Collapsable Filters

Platform-Wide Updates

...

Evaluate based on another event’s category

We added a new logic category that will allow you to build logic off of prior categorization which determines and sets a participants adherence snapshot categorycriteria option (that’s the “if” part of your rule) that allows you to evaluate based on another event’s category. An example of categories would be identifying participants who met their step goal, didn’t meet their step goal, or didn’t wear their activity tracker. This feature allows you to schedule actions such as messaging, point accruals and account credits without it being directly tied to the evaluation of the device data (in our example, steps) itself. This gives flexibility with scheduling of the actions. Visit our user guide page to learn more.

...

From the Manage Participant’s screen, you can administer actions to a single participant or a batch of participants. This includes sending notifications to participants, starting or finishing participants, and adding incidents to participant records. Previously, batch actions were limited to selecting participants per page. Now when you select check the Select All “Select All” check box at the top of the list view, you can apply batch actions to just the participants in your view, or across the entire filter. Visit our user guide page to learn more.

...

Autogenerate Username Creation for Inviting Project Staff

I don't know about you, but I have a million usernames and passwords to remember. Knowing this, W2H allows you to log in with your email, because that's one thing we can all remember. So now when you go to invite some of your study team members, we can auto-generate a username for your staff.

...

We are happy to announce that we integrated with new connected device, the Propeller Health Inhaler. This is an inhaler attachment that tracks the number of puffs a participant takes each day. Visit our user guide page to learn more.

Collapsable Filters

For example, on the participants page under manage participants we have a sidebar with filtering options for your participant data. This filter is super useful and allows you to easily find participant data based on your specifications, but sometimes we may want to hide that filter sidebar to get a larger participant page view. You can now do this by clicking the arrow in the top right corner of the filter sidebar. This feature is on all pages with filters.

...

Filters on the left side bar of listing screens provides you with a quick way to find participants, events, incidents or other relevant data in the platform. You can now collapse these filters to get a wider view of your list on the screen. Hey, we know screen real estate is at a premium these days!

...

We are busy working on:

  • Behind the scenes Developing and updating proper logging and monitoring to ensure the lights are on all the timethis lean, mean, Way to Health machine is working properly

  • Making participant variables more flexible and widely available. More on this, stay tuned!

  • Preparing to add new options to our payment model for automating human subject payments

...

  • We had some code on the backend called “StageCoach.” Stagecoach is no longer a thing, so we decided to delete any stagecoach-related code.

  • Updated the API and code for lottery enrollment steps

  • Fixed some bugs for new enrollment account creation regarding validating a cell phone number

  • We updated our Javascript build tools to the latest version

  • New enrollment survey completion page will now only show if you have a confirmation page created

  • Refactor: Move notification code out of PluginStudyUser into a service object

  • Our password complexity tool was not validating passwords with 4/5 bars, so we fixed that

  • Create /health.json endpoint in WTH core site exposing health of subcomponents of the system and Expose health of worker queues in health.json

  • Code cleanup of Payment stuff to make integrating new payment partners less scary

  • Allow users to update notification defaults if choosing Profile config that doesn't match current defaults

  • Prevent invalid configuration state for Notification Defaults and Account Creation fields