May 28, 2019
Highlights (6.4 and 6.5)
Variables Re-Defined
Manual Participant Payment Processing
Survey Completion Redirect
Notifying You if Texts Don't Go Through
Customizable Email Subject Lines
Improved Labels for EPIC Flowsheets
Time as a Variable
Platform-Wide Updates
Variables Re-Defined
Variables have been upgraded to allow for more options in participant data processing and messaging.
We have combined targets, achievements, the summarizer and the averager to make one powerful variable functionality.
Fun *NEW* things you can do with upgraded variables:
Define an ordered list of variable achievements for your specific program needs:
Gold, silver, bronze
Expert, intermediate, novice
Make a Survey_Link variable which will be available in messaging outside of the actual survey event, to allow you to send survey reminders to participants who forgot to complete it with the survey link embedded in the message.
Calculate weekly averages for participant data and compare them to another week's average.
And much more!
Ask your W2H liaison for more information about adding these variables to your intervention or visit our user guide for more information and a comprehensive description of the new features.
P.S. For all live studies, your existing setup is safe and sound. This update will not affect your intervention. The new variable functionality will only be live for new studies created moving forward.
Manual Participant Payment Processing
Show me the money! We get it, for those of you paying participants off platform with Clincard or other forms of payments, tracking participant payments using point values was not ideal. We have updated our payments page in W2H to allow you to easily manage your participant payments. You can now filter and export participant payment records as well as mark payments at paid or unpaid for your teams records! Click here to learn more!
Survey Completion Redirect
If you are using surveys in W2H, you may have noticed that participants were redirected to the W2H participant portal after the completion of a survey. This was confusing for studies and clinical projects that do not use the participant portal, so we gave it the boot. Confusion averted! Now when a survey is completed, your participants will only see the confirmation message configured on the survey.
Notifying You if Texts Don't Go Through
Whether it be the wrong phone number added by accident or an issue with the carrier, we know your study team wants to be notified if your text messages don't reach your participants. So we made an automated incident triggered for undelivered text messages.
Customizable Email Subject Lines
We all get a ton of emails. It is important for your to make sure your subject lines of your participant emails stands out. You now have the ability to edit your intervention's email subject lines by event. Note: if you leave it blank, it will send the subject line configured in advanced settings.
Improved Labels for EPIC Flowsheets
For those of you using our integration with EPIC flowsheets you are aware of the manual process to send this data to EPIC through Manage Data .The labels used to be "Mark as Pending For Epic" and "Mark as Not Sent to Epic." That wording isn't very clear, so we updated it to "Send to EPIC" and "Reset EPIC Status."
P.S. if your EPIC flowsheet submission from W2H fails, we will now send you a software incident letting you know. "EPIC FAIL: A row of data fails to submit to the epic flowsheet."
Time as a Variable
Computers, hospitals and the military use military time, while most of our participants use the standard am/pm 12 hour time. So now when you store times in W2H from participants survey responses, we will convert it from military time so that you can easily use it as a variable in messaging.
Behind the Scenes
Survey conversations are being tested and will be ready for users soon!
NLP and NLU using a super cool program called Bert
Integration with PennchartX to allow for more logic actions to be built off of EPIC data
Rewrite the Event Creation form as a Vue App
Depreciated old functionality now covered by variable functionality
Code cleanup and standardization across variables
Updates to variable comparison criteria based on new variable types
Break out larger task failures into smaller things posted to Sentry
Send errors from client-side JS to Sentry
Use a stronger password hashing algorithm