All Collections
CHR Releases
CHR Release Notes 2021
CHR Release Notes - version 21.05
CHR Release Notes - version 21.05

June 2, 2021

Updated over a week ago

💥 IMPROVEMENTS 💥

1. Cloning a billing item from the past in unsigned Encounters

We have added a functionality to clone past billing items for insured billing directly from within unsigned Encounters. To select and clone a past billing item, click the icon next to the Insured Billing button in the unsigned Encounter.

As previously, you can also clone past billing items under Start/Open > Insured Billing > New Payment, with a click on the icon on the right-hand side of Add Fee Item.

2. Patient Portal Payment page

For clinics that have Stripe integrated, we have added the ability for patients to make payments through the Patient Portal. Any private billing items that are created for a patient but have not been paid (no payment made), will automatically be shown in the Patient Portal. Patients will need to directly access the Patient Portal, login, and then navigate to the Billing page to view the details of the private billing items to make a payment.

For more details on payments through Patient Portal, please refer to this help article.

Please reach out to your account manager or our Support team if you would like to enable the Stripe integration and/or Patient Portal for your clinic.


🐛 🔨 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.

  • We have fixed an issue where overnight appointments were not properly displayed on the schedule. Appointments spanning two days will now be shown on the schedule as expected.


Scheduled time of update: Evening of June 2, 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?