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

# Corrected reports

> Issue a corrected report after a final report, and classify why it was generated.

A **corrected report** replaces an earlier final report on the same accession. Use it when released results or demographics change after a final report already went out.

The PDF looks like a normal report. bLIS records that this version is corrected, stores a required reason, and can store an optional [classification](#classifications).

## When to generate one

Generate a corrected report when a final report already exists and you need to send an updated copy. Typical cases:

* A result was amended after the final report
* Subject or sample details on the report were wrong
* Tests were added or excluded after the final report

<Note>
  If the accession is already **final**, the generate action on the accession is **Generate corrected report**.
</Note>

Do not use a corrected report for the first release. That is a [final report](/concepts/reports#report-types).

## What you enter

Before you preview or send, bLIS asks for:

| Field                           | Required                                                        | Where it appears                                                          |
| ------------------------------- | --------------------------------------------------------------- | ------------------------------------------------------------------------- |
| **Reason for corrected report** | Always                                                          | Preview, report details, and audit history. Not printed on the PDF        |
| **Classification**              | Only if your lab configured categories, and optionally required | Preview, accession report list, and audit history. Not printed on the PDF |

The classification is internal. Clients do not see it on the PDF.

## Generate a corrected report

<Steps>
  <Step title="Update the accession">
    Amend the result, demographics, or tests that need to change. The previous final report stays in history.
  </Step>

  <Step title="Open report preview">
    On the accession, generate a report. Because a final report already exists, this starts a corrected report.
  </Step>

  <Step title="Enter the reason">
    Type why you are issuing the correction. You cannot preview or generate without a reason.
  </Step>

  <Step title="Choose a classification">
    If **Admin** → **Lists** has at least one active category, select one. If your lab turned on **Require a classification when generating a corrected report**, you must select one before preview.
  </Step>

  <Step title="Preview, then generate">
    Click **Preview** to review the PDF. Then **Generate** or **Generate and Send**.
  </Step>
</Steps>

You can **Edit** the reason or classification from the preview bar before you generate.

## After you generate

* The accession report list shows a **Corrected** badge
* If you chose a classification, its **code** appears next to that badge
* The previous report remains available for audit
* Integrations that send on report release, such as [iTransplant](/integrations/itransplant#resend-a-successful-send), treat the new report as a new send

## Classifications

Classifications are categories your lab defines for why a corrected report was issued. Configure them in **Admin** → **Lists**.

If the list is empty, the classification field does not appear. If it has items, you choose one when generating a corrected report. You can require a classification from that same Lists screen.

The classification is not printed on the PDF.

## Related

<CardGroup cols={2}>
  <Card title="Reports" icon="file-lines" href="/concepts/reports">
    Report types and what a report contains.
  </Card>

  <Card title="Generating reports" icon="book-open" href="/guides/generating-reports">
    Preview, generate, and send reports.
  </Card>
</CardGroup>