Enhancements
Support Portal Announcement Feature
We have added a new Announcement section in the Support Portal to make platform-wide communication easier and more structured. This enhancement was needed so important updates such as maintenance notices, operational announcements, provider instructions, or client-specific messages can be shared directly within the system instead of relying only on external communication channels.
Super Admins can now create announcements for client admins, providers, specific provider groups, all users, or users under specific clients. Each announcement can include a title, description, image-supported content, start date and time, and expiry date and time. When the targeted user logs into their respective portal, the announcement appears as a pop-up.
Users can either close the announcement or mark it as read. If they close it, the announcement will continue to appear within the active timeframe. If they mark it as read, it will not appear again as a pop-up. A notification icon has also been added across the portals so users can view announcements later, even after marking them as read.
Client Admin Announcement Capability
Client Admins can now create announcements for users registered under their clinic. This enhancement was needed to allow clinics to communicate directly with their own user base without depending on the Super Admin team for every clinic-level update.
Client-created announcements include title, description, image-supported content, start date and time, and expiry date and time. These announcements are also visible to the Super Admin, which allows the team to maintain a record of what was sent, when it was sent, and the duration for which it remained active.
Provider Portal Prescription Pop-Up Functionality
We have added prescription-related pop-up functionality in the Provider Portal. This enhancement was needed to ensure providers receive the right instructions at the correct step of the prescribing workflow, especially when prescription guidance differs by client, tenant, or service.
When a provider clicks on prescribe and selects the prescription method, such as RxAve, Pharmacy.js, or DoseSpot, the system can now display a pop-up configured from the Support Portal. This helps providers review important prescription-related information before completing the prescribing process.
Tenant-Level and Service-Specific Pop-Up Configuration
The prescription pop-up can now be configured either at a generic tenant level or at a service-specific level. This enhancement was needed because some instructions apply to all consults under a client, while others apply only to a specific service.
If a generic pop-up is configured for a client, it will appear for all consults under that tenant. If a service-specific pop-up is configured, it will appear only for that selected service. This gives the team more flexibility in managing provider-facing instructions.
Admin Portal Branding Controls
We have improved branding controls in the Admin Portal by adding the option to remove uploaded favicons and logos. Previously, users could upload a favicon or logo, but there was no direct option to remove it once added.
This update gives admins better control over branding assets and allows them to update or clear portal branding when needed.
Admin Portal Account and Client Status Management
We have added additional account management controls in the Admin Portal. This enhancement was needed to give admins more flexibility in managing users and client access.
Admins can now delete providers, admins, and group admins. A client active/inactive status option has also been added. If a client is marked inactive, users trying to access links under that clinic will see an appropriate inactive-client message instead of continuing through the portal.
Framework Updates Across Portals
Framework-related updates have been completed across all portals, followed by verification of important UI and functional areas. This enhancement was needed to ensure that frontend version updates do not impact existing workflows, portal rendering, or user experience.
The team reviewed tables, images, URL redirection, and tenant-specific patient portal rendering to confirm that the updates did not create visual, navigation, or layout issues.
Bug Fixes
Service Master Template Pagination Issue
We fixed an issue in the Support Portal where Service Master Templates from the first page were appearing again on the second page. This caused duplicate visibility and made it difficult for users to review templates accurately.
The pagination behavior has now been corrected so each page displays the appropriate templates without repeating records from previous pages.
Lab Workflow and Lab Configuration Issues
We fixed issues related to lab workflows and lab configuration stability. In the follow-up flow with Access Lab and future lab workflows, consult statuses were being updated incorrectly during certain actions and events. This caused the follow-up flow to behave inconsistently.
We also fixed an issue where adding, updating, or removing a service action event caused lab configuration to reset. This was important to resolve because lab requisition email templates and lab settings were getting removed after workflow changes.
The flow has now been corrected so follow-up consult statuses remain aligned with the intended lab workflow, and lab configurations remain intact when service action events are added, updated, or removed.
Patient Portal “User Not Found” Login Issue
We fixed a Patient Portal login issue related to email capitalization. In some cases, users who registered with an uppercase first letter in their email were unable to log in again after completing a consult and logging out. Even after using Forgot Password successfully, the portal still showed a “User not found” error.
A similar issue occurred when users registered with a lowercase email but entered the first letter in uppercase while logging in. OTP was sent successfully, but after OTP submission, the same “User not found” error appeared.
The login handling has now been updated so email capitalization does not prevent the system from recognizing the user. This improves login reliability and prevents unnecessary access issues for returning users.
