Skip to main content
Off-schedule release notes 2025

2025

Updated yesterday

New CHR versions are released on a regular bi-weekly schedule. However, there are times where a fix is released prior to the next scheduled release. These off-schedule release fixes are documented here and are not included in the main release notes, unless it is an improvement.

Fixes and improvements

February 2025

Version 25.3.2 - February 14, 2025

  • When managing incoming referrals from the Referrals dashboard, you can now sucessfully fax waitlisted notification lettters to referring providers using the Send a Waitlisted letter Required action.

  • You can add Date, Text, Draw, and Picture follow-up question types in response to patient answers in Qnaires again.

Version 25.3.1 - February 12, 2025

  • When working with a patient's case template, you can now select and update case data points again.

Version 25.2.6 - February 8, 2025

  • When creating a WorkSafeBC bill from an encounter with a linked appointment, the system saves the form without any errors and auto-populates the Start Time and Finish Time fields in the billing item again.

Version 25.2.4 - February 3, 2025

  • For users in UBC facilities, when accessing patient charts with incorrectly formatted allergen types (created in or before 2016) you no longer see a server error. You can now access these patient charts as expected.

January 2025

Version 25.2.3 - January 31, 2025

  • You can add previously completed Qnaire responses to encounters even if the Qnaires have subsequently been deleted.

Version 25.2.2 - January 29, 2025

  • PEI: The user-specific insured payment setting Fill start time from the linked appointment is now off by default. Start times in billing items no longer automatically populate based on the linked appointment time.

Version 25.1.3 - January 16, 2025

  • When adding or updating certain patient information in the Patient Data section of a patient's chart, you can search for and select items from a dropdown list again, instead of scrolling through a long list of checkboxes.

Did this answer your question?