Enhancements
Expanded Stripe Payment Gateway Options
The Stripe payment gateway has been enhanced to support additional payment methods beyond standard debit cards, credit cards, and bank payments. This update was needed to provide more flexible payment options for users and to support a wider range of client payment preferences.
As part of this update, additional Stripe-supported payment methods such as Amazon Pay, Klarna, Cash App Pay, and other available merchant options will be tested and supported where applicable. This helps improve the checkout experience and gives users more ways to complete payments smoothly.
DoseSpot Patient Mapping in Support Portal
The DoseSpot patient mapping workflow has been improved in the Support Portal. Previously, the new Support Portal did not include a DoseSpot Patient ID field, making it difficult for support teams to confirm whether a patient had been successfully mapped with DoseSpot.
With this update, when patient details are submitted again or updated, the system will attempt to map the patient with DoseSpot. Once the mapping is successful, the DoseSpot Patient ID will be visible in the Support Portal. This gives support teams better visibility into the patient’s DoseSpot mapping status.
RxAve Patient Mapping in Support Portal
RxAve patient mapping has been enhanced to make mapping status clearer and easier to manage from the Support Portal. This update was needed so support teams can quickly identify patients who are not mapped with RxAve and take action directly from the portal.
A mapping status icon has been added for patients who are not mapped with RxAve, similar to the DoseSpot mapping flow. A Sync button has also been added so support users can manually sync the patient with RxAve. If an error occurs during mapping, the system will display the error message, making it easier to troubleshoot and resolve mapping issues.
DoseSpot Integration Updates
Several technical updates have been implemented to improve the reliability, synchronization, and usability of the DoseSpot integration.
The DoseSpot Single Sign-On URL has been optimized by removing redundant query parameters from the authentication request. This helps ensure a cleaner and more stable SSO flow for providers.
Webhook handling has also been enhanced so the platform can receive and process important DoseSpot events, including provider profile status updates and other relevant system notifications. This helps keep provider and integration data more accurately synchronized between DoseSpot and the platform.
Pharmacy mapping has been improved at the patient level. The system now supports assigning a primary pharmacy to a patient, allowing the prescription workflow to use the correct pharmacy more consistently. If a primary pharmacy is not assigned, the workflow will either continue with the existing mapped pharmacy or prompt the provider to select or map a pharmacy within the DoseSpot iFrame.
Additional updates have also been made to improve access token handling for WellSync and the main API workflows. This helps prevent authorization-related errors and improves the stability of prescription-related API requests.
Bug Fixes
Support Portal SLA Calculation
An issue was fixed in the Support Portal where SLA was not calculating or reflecting correctly on the consult listing page, even when SLA was enabled for a service.
This has now been corrected so SLA values are calculated and displayed properly for applicable services. This helps support teams track consult timelines more accurately from the consult listing page.
An issue was fixed in the Patient Portal account creation flow where registered emails selected from browser suggestions were not being validated properly.
Patient Portal Email Validation During Account Creation
Previously, if a user manually typed an already registered email, the system correctly displayed a validation message showing that the email already existed, along with a Login button. However, when the same email was selected from the browser’s autofill or suggestion dropdown, the system showed a green tick mark and incorrectly indicated that the email was available.
The issue only appeared after the user clicked Continue, and even then, the Login button was not shown. This forced the user to restart the flow or manually go back to log in with the existing account.
The validation flow has now been corrected, so emails selected from browser suggestions are validated immediately. If the email is already registered, the system now displays the correct validation message along with the Login option, making the account creation and login flow smoother for returning users.
