> ## 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.

# Validating Results

> Learn how to review and validate test results for accuracy before finalization.

## Overview

Result validation is the quality control step where a second technician reviews entered results to confirm accuracy before they are finalized and included in reports. This double-check process helps prevent errors from reaching patients and clinicians.

<Note>
  Not all tests require validation. Whether a test needs validation depends on its configuration and your lab's standard operating procedures.
</Note>

## The Validation Process

<Steps>
  <Step title="Result Entry">
    A technician enters the initial result value (either manually or from an instrument).
  </Step>

  <Step title="Validation Review">
    A second technician reviews the result for accuracy. Depending on your lab's SOP:

    * **Visual review** — Check the entered value against the instrument output or worksheet
    * **Double entry** — Re-enter the result independently and confirm it matches
  </Step>

  <Step title="Mark as Validated">
    If the result is correct, click **Validate** to mark it as validated.
  </Step>

  <Step title="Ready for Finalization">
    Once all results in an accession are validated, they can be finalized by an authorized user.
  </Step>
</Steps>

## Who Can Validate Results?

Validation permissions vary by lab configuration:

* **Different technician required** — The validator must be someone other than the person who entered the result
* **Same technician allowed** — Some tests allow self-validation (typically simple or automated tests)
* **Auto-validation** — Some tests are automatically validated (e.g., results uploaded directly from validated instruments)

<Tip>
  If you try to validate a result you entered and get an error, this means your lab requires a different technician to perform validation for quality assurance.
</Tip>

## Double-Entry Validation

For tests that require double-entry validation:

<Steps>
  <Step title="Open the result">
    Navigate to the result that needs validation.
  </Step>

  <Step title="Enter the value">
    Type the result value based on your source (instrument printout, worksheet, etc.).
  </Step>

  <Step title="Submit">
    Click **Validate** or **Submit**.
  </Step>

  <Step title="Automatic comparison">
    bLIS compares your entry to the original. If they match, the result is validated. If they don't match, you'll see an error.
  </Step>
</Steps>

### If Values Don't Match

When your validation entry doesn't match the original:

1. **Check your source** — Verify you're reading the correct value
2. **Check the original entry** — The first technician may have made an error
3. **Investigate the discrepancy** — Determine which value is correct
4. **Notify a supervisor** — If unsure, involve a lab manager to resolve the discrepancy

<Warning>
  Never "force" a validation by changing your entry to match if you believe the original is incorrect. Instead, have a supervisor review and correct the original entry.
</Warning>

## Visual Review Validation

For tests that use visual review instead of double-entry:

<Steps>
  <Step title="Open the result">
    View the result that needs validation.
  </Step>

  <Step title="Compare to source">
    Verify the entered value matches the source document (instrument printout, manual recording, etc.).
  </Step>

  <Step title="Check for flags">
    Look for any warnings or flags that require attention.
  </Step>

  <Step title="Mark as validated">
    If correct, click **Validate**.
  </Step>
</Steps>

## Validating Instrument Results

When results come directly from connected instruments:

* **Pre-validated results** — Some instruments are configured so their results are automatically validated
* **Review-only validation** — Technician reviews the result but doesn't re-enter it
* **Manual validation required** — Even instrument results need a second technician to validate

The validation method depends on your lab's trust level in each instrument and regulatory requirements.

## What to Check During Validation

When validating results, look for:

<AccordionGroup>
  <Accordion title="Accuracy">
    Does the value match the source? Are there any transcription errors?
  </Accordion>

  <Accordion title="Plausibility">
    Is the result biologically plausible? Extremely high or low values may indicate errors.
  </Accordion>

  <Accordion title="Units">
    Are the correct units used? (mg/dL vs. g/L, etc.)
  </Accordion>

  <Accordion title="Flags and Alerts">
    Are there any system flags, warnings, or critical value alerts that need attention?
  </Accordion>

  <Accordion title="QC Status">
    Have quality control samples passed for this test run or time period?
  </Accordion>
</AccordionGroup>

## Batch Validation

For high-volume testing, you may validate multiple results at once:

1. **Filter for pending validation** — Show only results that need validation
2. **Review each result** — Check each value systematically
3. **Validate in batch** — Some systems allow selecting multiple results and validating them together
4. **Verify all are valid** — Ensure no errors or flags before batch validation

<Tip>
  Batch validation is faster but requires careful attention. If you're unsure about any result in the batch, validate it individually instead.
</Tip>

## After Validation

Once validated:

* ✅ Result is marked with validated status
* ✅ Timestamp and validator ID are recorded
* ✅ Result can now be finalized by an authorized user
* ✅ Result is one step closer to being included in a report

## Troubleshooting

<AccordionGroup>
  <Accordion title="Can't validate - wrong user">
    **Cause:** You entered the original result, and your lab requires a different technician to validate.

    **Solution:** Ask a colleague to validate the result.
  </Accordion>

  <Accordion title="Can't find results to validate">
    **Cause:** Results may already be validated or may not require validation.

    **Solution:** Check the result status. If it shows "validated" already, no action is needed.
  </Accordion>

  <Accordion title="Double-entry mismatch">
    **Cause:** Your validation entry doesn't match the original entry.

    **Solution:**

    1. Check your source document
    2. If you believe your entry is correct, notify a supervisor
    3. Don't change your entry just to make it match
  </Accordion>
</AccordionGroup>

## Best Practices

<CardGroup cols={2}>
  <Card title="Validate Promptly" icon="clock">
    Validate results soon after entry to avoid delays in reporting.
  </Card>

  <Card title="Use Original Sources" icon="file">
    Always validate against the original source (instrument printout, worksheet) not just the screen.
  </Card>

  <Card title="Question Unusual Results" icon="triangle-exclamation">
    If a result seems implausible, investigate before validating.
  </Card>

  <Card title="Document Issues" icon="comment">
    If you find errors or discrepancies, add a comment explaining what you found.
  </Card>
</CardGroup>

## Related

<CardGroup cols={2}>
  <Card title="Entering Results" icon="keyboard" href="/guides/entering-results">
    Learn how to enter initial results.
  </Card>

  <Card title="Results Concept" icon="chart-simple" href="/concepts/results">
    Understand the complete result pipeline.
  </Card>

  <Card title="Generating Reports" icon="file-pdf" href="/guides/generating-reports">
    Create reports after results are validated and finalized.
  </Card>
</CardGroup>
