> ## Documentation Index
> Fetch the complete documentation index at: https://docs.blis.app/llms.txt
> Use this file to discover all available pages before exploring further.

# Result conflicts

> Delta checks and High/Low range flags on accession results

bLIS flags results that need review when they change sharply from a subject's prior value, or when a finalized numeric result is outside a configured range. These flags appear on the accession test list. There is no separate conflicts dashboard or resolve workflow — you review them as part of normal result review.

## Delta checks

Delta checks compare a new result to the subject's most recent prior finalized result for the **same result spec**. If the check fails, bLIS records a delta conflict and shows a badge on the accession.

The check runs when you enter a result and again when you finalize it. Reflex repeat results do not get their own delta check. Instrument-entered results are still saved when a delta fails; auto-validation is blocked so a tech must review the result.

### Numeric delta checks

For numeric result specs, configure one or both thresholds under **Admin** → **Test specs** → result spec **Details** → **Delta checks**:

* **Percent change threshold** — flag when the percent change exceeds this value
* **Absolute change threshold** — flag when the absolute difference exceeds this value

If both are set and both would fail, the percent check is used.

When a numeric delta fires, the result shows a red triangle badge with the change (for example `+50.0` or `+50.0%`). Hover the badge or open result details to see the previous value and a link to the prior accession.

### Qualitative delta checks

For text (categorical) result specs, you can opt in to flag any change from the prior finalized value.

1. Go to **Admin** → **Test specs**
2. Open the test and select the text result spec
3. Under **Delta checks**, select **Flag when the result changes**
4. Save

When enabled, a different selected value from the prior finalized result shows a red **Discrepant** badge. Hover or open result details to see the previous result and the accession it came from. Matching values do not create a conflict.

This option applies only to text results, not free text or numeric.

## High and Low range flags

When a numeric result is finalized and falls outside a configured range for that result spec, bLIS shows a yellow **High** or **Low** badge on the accession. The same flags can appear on reports.

Configure ranges on the result spec **Ranges** tab (**Admin** → **Test specs**). Ranges can be scoped by sex and age. Mark reference ranges with **Is reference** — those are also used when deciding whether an instrument result can auto-validate.

Range flags are created at finalization. They are informational; there is no separate resolve action.

## Double-entry mismatches

Double-entry is not stored as a result conflict. If a second entry does not match the first, bLIS blocks the save and shows a **Result Validation Conflicts** dialog so you can correct the value. Exact match is required — there is no tolerance setting.

You can turn off double-entry per result spec with **Disable double entry** on the **Details** tab.

## Instrument errors

Instrument errors (error codes and messages from the analyzer) appear on the accession **Instrument** tab. They are separate from delta and High/Low flags.