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

# Results

> Understand how test results are entered, validated, and finalized in bLIS.

## What is a Result?

A **result** is the outcome of a test order — the measured value or finding that a test produces. Results in bLIS go through a structured pipeline to ensure accuracy before they are released.

## Result Types

bLIS supports several types of results depending on the test:

| Type          | Description                                 | Example             |
| ------------- | ------------------------------------------- | ------------------- |
| **Numeric**   | A measured numerical value with units       | Glucose: 95 mg/dL   |
| **Text**      | A value selected from a predefined list     | Blood Type: A+      |
| **Free Text** | An open-ended text entry                    | Microscopy findings |
| **HLA**       | Specialized Human Leukocyte Antigen results | HLA typing results  |

## The Result Pipeline

Results move through three stages to ensure quality:

<Steps>
  <Step title="Entry">
    A lab technician enters the result value — either manually or received automatically from a connected lab instrument. The system records when the result was entered and by whom. The system validates the input matches the expected result type (numeric, text, free text, or HLA).
  </Step>

  <Step title="Validation">
    The result is reviewed for accuracy. For tests that require double-entry validation, a second technician independently enters the same result to confirm it matches. Once validated, the result is marked as confirmed and ready for finalization.
  </Step>

  <Step title="Finalization">
    An authorized user (typically a lab manager or supervisor) approves the final result. Once finalized, the result is locked and cannot be changed without proper authorization. Finalized results are included in reports.
  </Step>
</Steps>

<Note>
  Not all tests require double-entry validation. The validation requirements are configured per test specification.
</Note>

## Related

<CardGroup cols={2}>
  <Card title="Result conflicts" icon="triangle-exclamation" href="/concepts/result-conflicts">
    Delta checks and High/Low flags on accession results.
  </Card>

  <Card title="Test Orders" icon="clipboard-check" href="/concepts/test-orders">
    Learn about the test orders that produce results.
  </Card>
</CardGroup>