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 only set a customer retry window for batch eligibility checks submitted using the Batch Eligibility Check API endpoint.

When to use batch eligibility checks

For most use cases, we recommend using real-time eligibility checks for both one-off checks, like when a patient is at the front desk, and bulk checks, like monthly refreshes. It’s a simple, flexible setup.

If you’re thinking of writing custom code to manage queuing or retries for your bulk eligibility runs, consider using batch checks.

For details, see When to use 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.