---
title: Release Notes - 8.8.3
slug: portal-sub/release-notes-883
docTags: 
createdAt: 2026-03-04T12:03:21.618Z
---

### Feb. 1, 2023

## Enhancements

### Global

**Support button added to Profile title bar (Ticket 95535)***Misc*A new Support button has been added in the top-right corner of the Profile title bar to easily access Intrahealth solutions, forums and to create new tickets.

**Profile Portal API password recovery enhancement***Portals&#xA0;*&#x54;he Profile Patient/Provider Portal API was changed to support password recovery enhancements.

**Profile Portal API password reset enhancement***Portals&#xA0;*&#x54;he Profile Patient/Provider Portal API was changed to support password reset enhancements.

**Patient portal registration web page created***Portals&#xA0;*&#x41; new web page has been created which allows an invited patient to create their own username and password with which to log into Profile Patient Portal and Accession.

**Forgot Password added in Profile and Accession Patient***Portals&#xA0;*&#x46;unctionality added to allow patients who have an email address in Profile to reset their own Profile Patient Portal/Accession password securely without having to contact the clinic.

**Patient portal registration***Portals*Profile can now send a message to patients when they are enabled to access Profile Patient Portal and Accession which contains a link for them to create their own username and password.

## Changes

### Global

**Increased scanning of uploaded files in the New Encounter functionality in Profile***Encounters*

**Send messages to multiple patients in Control Centre***Messages*The ability to send messages to multiple patients has been added to Control Centre/Aero & Accession Settings view.

**Increased scanning of uploaded files in the Ask A Question functionality in Profile***Portals&#xA0;*

**Increased XSS protections in Accession Messages view***Portals&#xA0;*

**Increased scanning of uploaded files in the Ask A Question functionality in Accession***Portals*

**Increased authorization security features added for Profile Portal and Accession***Portals*Login attempt throttling and 2FA token lifespan have been added for Profile Patient/Provider Portal and Accession. Profile Patient/Provider Portal and Accession users can use 2FA PINs within a limited short period of time and limited amount of attempts.

### Canada

### British Columbia

**Default CDX stylesheet updated***Messages*We have updated the default CDX stylesheet (a presentation layer) to its latest version, which includes bug fixes from CDX.

**\[CDX] External POS created if not found by Clinic ID search***Messages*Profile wasn’t able to handle receiving a CDX transaction from a location that doesn’t exist in the database or isn’t properly linked in the database.   Now, the external POS is created automatically if it isn’t found by the Clinic ID search and automatically linked to the external provider.

**Antenatal form printing issue (Ticket 106534)**

*Obstetrics*In the Additional Information area of the Antenatal form, when a patient had a really long name or multiple names, part of the name was cut off in the printout of the form. This has been fixed.

### New Brunswick

**Profile Portal & Accession Provider showing multiple English entries***Portals*Several instances of English words were showing within the French Profile Profile Provider Portal & Accession Provider area. This has been changed.

## Defect Fixes

### Global

**Unable to print Intervention report***Care Plans, Printing*The Printing progress dialog box displayed without end when printing the Intervention report from the Care Plans view and the report didn’t print. This has been fixed.

**Intermittent Profile crashes (Ticket 104560)***Documents, Forms*Profile was intermittently crashing, likely in relation to updating Group Policies in Windows.  This has been fixed.

**Privacy statement display issue***Email*When nothing was displayed in the Privacy Statement field in the Email Templates tab of Internet preferences, the default privacy statement still displayed in the email.  This has been fixed.  

**Email API service issue***Email*Appointment reminders were sent using the SMTP service even though Email API was selected in the Email tab of Internet preferences. This has been fixed.

**Privacy statement change issue***Email*When the privacy statement text was modified in the Email Templates tab of Internet preferences, the new text didn’t display in the privacy statement in an email. This has been fixed.

**Exception error when sending fax to new recipient***Faxing*An exception error would sometimes occur after clicking the Send to New Recipient(s) icon, which creates a duplicate fax to send. This has been fixed.

**eSignature capture display issue in form***Forms*The signature form control in Form Builder forms did not fully capture the complete eSignature box, so signatures would be cut off at the beginning and the end. This has been fixed.

**Admitting patients issue with Patient Movements via COM Interface (Ticket 100007)***Misc*There was an issue where patients could not be admitted with Patient Movements using our COM Interface. This has been fixed. 

**Issue running dynamic groups from scheduled task (Ticket 94638)***Misc*Previously, a scheduled task was able to run a dynamic patient group and create a static group as a result, but this stopped working in Profile 8.5. This has been fixed.

**Incorrect label used for Items***Patient*After changing the Type from Patient to Item in a New Patient window, the second field was labelled First Names instead of Attention.  This has been fixed.

**Error when opening an Alter Patient/Organization window (Ticket 102676)***Patient*An Access Violation error occurred when opening an Alter Patient/Organization window. This has been fixed.

**Search issue using PTNT\_SOURCEREF after duplicate patient merge (Ticket 104921)***Patient*When a patient file was imported into Profile from another source, the patient could be searched using PTNT\_SOURCEREF. After being merged with a duplicate patient where it was not the Master patient, the patient couldn’t be searched using PTNT\_SOURCEREF anymore. This has been fixed.

### Canada

**Billing filter Presentation options issue (Ticket 84127)***Financial*For the Billing filter Presentation options, users were unable to enable the Description column. This has been fixed.

**Display issue when adding participants to patient conversations (Ticket 100895)***Messages*In the Patient Items view, when adding participants to patient conversations, participant names were not displaying or displaying in the right message. Refreshing could correct the issue, but not always.  This has been fixed.

**Results display issue (Tickets 108957, 108932, 108715)***Results*Some results with RTF content were not being displayed in the Results tab. This has been fixed.

### British Columbia

**Antenatal Observations date sort order issue (Ticket 99958)***Forms*When trying to sort by date in Antenatal Observations, it was sorting alphanumerically.  This has been fixed.

**HDC integration fix***Misc*The data included into the HDC incremental export was incomplete. This has been fixe&#x64;*.*

### New Brunswick

**SMS French response keywords issue (Ticket 101256)***Messages*SMS French response keywords for START and STOP were not triggering corresponding Profile EMR triggers to check the Communicate by SMS Mobile checkbox or uncheck it. This has been fixed.

**\[Accession Patient] Past Appointments view display issue**The Past Appointments view in Accession Patient was not accurately displaying recurring appointments.  This has been fixed.

**\[Accession Patient] Email about Profile-modified appointments in English**Email to patients about Profile-modified Accession Patient appointments was displaying English text.  This has been fixed.

### Australia

**Medicare claiming error with Invalid URI message (Tickets 107420, 106967)***Financial*Since Medicare updated to PRODA, multiple sites were getting the error Invalid URI: The format of the URI could not be determined. When this happened, Medicare transactions (e.g., Claiming, Patient Verification, etc.) were not possible. This has been fixed.



