Introducing longer retry windows for batch eligibility checks
You can now change how long Stedi retries failed checks in a batch using the new maxRetryHours property of the Batch Eligibility Check API endpoint.
Batch eligibility checks let you run multiple eligibility checks asynchronously in a dedicated pipeline, separate from your real-time checks.
If a check in a batch fails due to payer connectivity issues, Stedi automatically retries the check over a specific time window. Stedi doesn’t charge for these failed checks.
Previously, Stedi retried failed checks for up to 8 hours. You can now extend that window to up to 24 hours.
Set a custom retry window for batch checks
Use the Batch Eligibility Check endpoint’s optional maxRetryHours request body property to set how long Stedi should retry checks in a batch that failed due to payer connectivity.
You can set any integer between 8 and 24 hours (inclusive). If you don’t specify a value, the default remains 8 hours.
For example:
curl --request POST \
--url https://manager.us.stedi.com/2024-04-01/eligibility-manager/batch-eligibility \
--header 'Authorization: <api-key>' \
--header 'Content-Type: application/json' \
--data '{
"items": [
...
],
"maxRetryHours": 24 // Retry failed checks for up to 24 hours
}'
Note: You can also set a retry window for batch checks you submit through CSV upload. See Introducing longer retry windows for batch CSV eligibility checks.
When to use batch eligibility checks
Use real-time eligibility checks for checks that need results in seconds, like when a patient is at the front desk. For bulk checks that aren’t time sensitive, like monthly refreshes, use batch checks. They handle queuing and retries over longer periods for you.
For details, see How and why to move to batch eligibility checks.
Get started
Need help setting up batch eligibility checks? Reach out and schedule a consultation.
We’ll help you design a scalable workflow that fits your needs.