Focused work account · Cigna Supplemental Benefits / Evernorth
Production fallback
Give enrollment a fallback before it fails
The new benefit used an API to publish enrollment to a claims-administration partner. Testing made me question how that path would behave during an outage, so I proposed a second way to deliver the same enrollment.
Technical product management; partner integration and resilience
My contribution
I worked with the partner on an existing file-processing capability and coordinated SFTP connectivity and enrollment-file generation as a fallback.
What the work delivered
Production support used the backup to publish memberships when the API was unavailable.
01
The risk I noticed
During testing for the new benefit, I saw enough integration issues to question the reliability of a new API spanning two organizations. The customer needed enrollment to reach the claims-administration partner even when that service was unavailable.
02
A practical second path
I discussed fallback options with the partner and learned it already supported traditional file processing. I proposed using that capability during API failure, and the teams set up SFTP connectivity and enrollment-file generation.
03
Used in production
Production support used the fallback during subsequent outages to publish memberships. The second delivery path gave the team a practical way to continue enrollment when the API was unavailable.