(tutorials:reporter-overview)=
# Reporter overview

SeqsLab **Reporter** is the clinical workflow module for managing samples, analyses, and signed reports. It is designed for laboratories that need a clear, auditable path from patient sample registration through analysis to final report issuance.

## What you can do in Reporter

Reporter organizes clinical work around five console areas:

| Area | Purpose |
| --- | --- |
| **Management** | View and act on samples across the four workflow swim lanes: PENDING, ANALYSIS, REVIEW, and REPORT. |
| **Add Sample** | Register a new patient, order, and biosample, including phenotype and ordering-physician information. |
| **Sample List** | Browse, search, and filter all registered samples. |
| **Dashboard** | See high-level metrics and status summaries for the laboratory. |
| **Settings** | Configure report types and other Reporter-specific options. |

The Reporter root redirects to **Management** because that is the main operational view.

## Who uses Reporter

Reporter is intended for distinct clinical roles, each responsible for a stage of the workflow. The exact permissions depend on the roles assigned to your account. Typical roles include:

| Role | Main responsibility |
| --- | --- |
| **ReporterDataEntryOperator** | Register patients and samples. |
| **MedicalTechnologist** | Upload sequencing data and curate review-stage findings. |
| **BioinformaticsScientist** | Run analysis pipelines and create interpretations. |
| **LaboratorySupervisor** | Create and approve reports. |
| **MedicalDirector** | Sign out or reject final reports. |

If you are unsure which role you hold, ask your SeqsLab administrator. Do not assume an action is allowed simply because a button appears in the interface; your role may not authorize the action.

## Key concepts and terms

| Term | Meaning |
| --- | --- |
| **Individual** | The patient from whom a biosample is collected. |
| **Phenopacket** | A standardized record of the patient's phenotype and clinical information. |
| **Biosample** | The physical specimen collected for sequencing (for example, blood or tissue). |
| **Interpretation** | A curated finding about a genomic variant or result, often linked to a report. |
| **PhenopacketReport** | The final signed clinical report generated from the sample data. |
| **Assay** | The sequencing or test protocol assigned to a sample. |

## Reporter workflow at a glance

The high-level path through Reporter is:

1. Register the patient and sample ({ref}`tutorials:reporter-register-sample`).
2. Upload sequencing data and start the analysis ({ref}`tutorials:reporter-upload-and-analysis`).
3. Review and curate the analysis results ({ref}`tutorials:reporter-review-and-curation`).
4. Create, approve, sign out, or reject the report ({ref}`tutorials:reporter-reporting`).
5. Search, filter, and manage samples over time ({ref}`tutorials:reporter-operations`).

For the formal state machine and role boundaries, see {ref}`tutorials:reporter-sample-lifecycle`.

## Where to go next

- {ref}`tutorials:reporter-sample-lifecycle` to understand states and transitions.
- {ref}`tutorials:reporter-register-sample` to add your first sample.
- {ref}`security:healthcare-rbac` for the authoritative role-permission reference.