Flexpa - Notice history

This incident has been resolved.

We implemented a fix and are currently monitoring the result.

This incident has been resolved. The incident impacted successful Flexpa Link authorizations.

Why did it happen?
We pushed a bug into production code related to the generation of system Patient IDs upon a successful Flexpa Link authorization. Due to a test which passed incorrectly, the bad logic was not caught in development.

How to prevent in future?
By creating re-usable test fixtures, specifically as it relates to our patient authorization model, we can make it easier for developers to avoid writing false positive test cases.

We implemented a fix and are currently monitoring the result.

This incident has been resolved.
This did not affect any customer implementations or integrations with Flexpa Link.

Why did it happen?
We promoted an environment change in MyFlexpa's dev mode, and had to complete unexpected manual steps to redeploy the MyFlexpa application.

How to prevent in future?
Improve our internal change process for updating MyFlexpa's environment configuration by removing unnecessary manual steps.

This incident has been resolved.

Why did it happen?
Flexpa released a fix to accommodate a scenario where some payer authentication flows were incompatible with Safari. However the fix, which uses cookies to handle communication between Flexpa Link and Flexpa API, introduced a bug which was undetectable in the development environment because the development environment shares the same domain across services.

How do we prevent it in the future?

• Broaden test suite across browsers. Safari, Chrome, Firefox etc.
• Test across multiple domains in the development environment

We implemented a fix and are currently monitoring the result.

We are continuing to work on a fix for this incident.