refill_risk=true to any prescriptions request and each prescription comes back with a nested refill_risk object.
It’s a forward-looking check, not a status. A prescription can be perfectly valid today and still be at risk, because the license covering it expires before the patient is due for their next fill.
Ask for the assessment
The
refill_risk object is omitted entirely unless you pass the parameter. Don’t write code that expects it on every prescription response.Reading the result
at_risk is the field to alert on. It’s true when the covering license is missing today, or expires before the predicted next fill.
When at_risk is true, reasons tells you which:
The assessment also returns
predicted_next_fill_date, last_fill_date, days_supply_used, relevant_states, covering_licenses, earliest_covering_expiration, days_until_next_fill, and days_until_license_expiry — enough to build a prioritized worklist rather than a flat alert.
When it doesn’t apply
applicable: false means Blend skipped the assessment, and not_applicable_reason says why:
cancelled— the prescription is cancelledrx_expired— the prescription has already expiredno_fills_remaining— nothing left to fillno_prescriber— no prescriber attachedno_relevant_states— no state could be determined to check against
Fixing what it finds
The remedy is almost always to update the prescriber’s state license. Add or renew one withPOST /prescribers/{prescriber_id}/qualifications, or manage licenses directly in the Blend Dashboard under Prescribers. Blend also monitors prescriber credentials on your behalf — see does Blend track prescriber license status for me?
Get prescriptions
refill_risk=trueGet a prescription
refill_risk=trueCreate a license/qualification
Add a state license
Get a prescriber's details
Current licenses and credentials