πŸ’₯ IMPROVEMENTS πŸ’₯

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


Qnaire Response Inbox Updates πŸ“š

InputHealth provides a feature to send out Pre-Visit-Qnaires prior to an appointment. Previously, the default provider inbox for Qnaire responses was set to the practitioner associated with the appointment.

With this update, we now provide the option to select a specific provider inbox for Qnaire responses. On the appointment dialogue field, under Pre-Visit-Qnaire, you will see a new icon enabling you to select a specific inbox.

If no inbox is selected, the Qnaire response will be sent to the default provider inbox (assigned practitioner).

Read this help article, Attaching Pre-Visit Qnaires to Appointments, to find out how to change the default provider inbox per Appointment type.

Recurring Appointment Updates πŸ”

Earlier this year, InputHealth introduced a new feature, Creating Recurring Appointments. We have now further improved this feature by adding the ability to mass-edit all appointments in a recurring series.

Changes made to the appointment interval, appointment reminders, or template (e.g. notes), will automatically apply to all future events.

For general information about how to create and edit recurring appointments, please visit our help page, here.


πŸ› πŸ”¨ 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.

  • Fixed calendar view on mobile, for patients completing and signing Qnaire.


πŸ‘¨β€πŸ’» 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 December 16th, 2020

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?