We are postponing this release to Tuesday, Nov 12th, to make sure our partners have enough time to adapt to some of our changes. We have also released additional documentation on how to keep a seamless login experience when using our white label apps here:

https://documenter.getpostman.com/view/14212272/2s8Yt1r9B8#1beb92b7-68f6-432d-b50d-5dab9fb966eb

Note we are also disabling/blocking TLS 1.2 and below. According to our logs, no customers will be impacted by this change should we implement it in this upcoming release. We'll be releasing an update to this note to accommodate that.

On Monday, Nov 4th, we will be releasing a few notable changes that might require updates to your existing integration. Additionally we will be upgrading our server infrastructure which will cause service disruption for up to three hours according to our deployment window.

• [Action Required] Consolidation of White-Label URLs: We will consolidate all our white-labeled URLs under the same domain: https://patient.mdintegrations.com. As a result, message.mdintegrations.com and onboarding.mdintegrations.com domains will automatically redirect to the primary domain.

While we expect very few partners to be affected by this change, we recommend all partners to review existing CSP (Content Security Policy) rules, as some configurations may block different domains from loading. Please ensure that https://patient.mdintegrations.com is whitelisted to avoid disruptions.

• [Action Required] New type field for files: On our previous deploy we introduced a new type field to be sent when creating files. This new field will help categorize documents associated with a patient’s encounter and help our AIs to better understand their context.

While this field is optional, we recommend you check the Create File API documentation and start sending it. For partners using our white label products, this change will be transparent to you.

• [Service Disruption] Server Upgrade and API Improvements: We are introducing additional servers to handle patient/encounter creation and partner authentication as a way to enhance our API's ability to withstand issues resulting in service unavailability for our partners.

While this update should be transparent for most partners, some may experience authentication issues, which may invalidate existing session tokens ahead of their expiration time. If after the migration your API returns authentication issues, generating new access tokens (via v1/partner/auth/token) solves the issue.

• [UX Change] Changes to Patient Authentication Process for Workflows We will no longer generate pre-authenticated URLs for workflows like: messaging, file upload, driver's license request, AV intro video upload, etc. This is a security enhancement to avoid possible session hijack attacks accessing the authenticated URL on public networks.

Instead patients will be redirected to the 2FA screen where they will be asked to input an OTP. For partners generating links via the API, an OTP will be generated together with the URL so it can be exposed to the patient. For partners that use our email notifications, the OTP will be sent together with the link and no additional change will be required.

Additional changelogs, if any, will be released on on the week prior to the deploy with changes to internal products.