Release Notes - version 20.28

January 28, 2021

Updated over a week ago


A list of all the cool things we have added to our platform!

Custom inbox for Qnaire responses (now for group visits) 📚

We have previously developed a functionality to assign custom inboxes for Qnaire responses for appointments and appointment types. You are now able to use the same functionality for group visits and group visit templates.

Please refer to this help article Scheduling Group Visits for more details on how to change the default provider inbox (receiver of the completed Qnaire) for group visits or group visit templates.

Failure Message for Reminders 📫

Reminder messages on appointments will now tell you why they failed. If you navigate to the appointment and look at the list of reminders, you can hover over the failed icon to get more information as to why it did not send.

In the example above, the appointment was still in a status of 'provider_requested' better known as Confirmation Required.

🐛 🔨 BUG FIXES 🐛 🔨

Below is a list of bugs we have identified and fixed in this release. Should you want any more detail on the issues below, please feel free to message us.

  • Previously when editing lab files in the inbox, the date on file would automatically update to the date the file was edited. We have removed this automatic change to ensure that the original date of the file stays visible.

  • We have fixed a very recent issue with Group Visits. You are again able to attach pre-visit Qnaires to group visits.

👨‍💻 Known/Residual Bugs 👩‍💻

This is a list of known bugs that we have not quite gotten to but haven't forgotten about. Please reach out if you have any questions about this list.

Scheduled time of update: Evening of January 28th, 2021

No preparation is required by site users in advance of the update. All CHR update activities are managed by InputHealth via a zero-downtime rolling deployment in the CHR’s cloud infrastructure, which allows the system to operate without interruption of service during updates.

No data migration will be required as part of this update.

Did this answer your question?