> For the complete documentation index, see [llms.txt](https://docs.unitlab.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.unitlab.ai/documentation/annotations/medical-annotation.md).

# Medical Annotation

Medical annotation preserves study, series, plane, slice, windowing, geometry, and clinical context. Access, specialist ownership, and data-handling controls are part of the workflow—not an afterthought.

### What this editor is designed to preserve

* Study and series identity, orientation, plane, slice, and spatial context.
* Window/level, VOI LUT, projection, slab, color map, threshold, and 3D context required for the decision.
* Specialist review and provenance for clinically sensitive labels.

![Medical annotation Workbench with synchronized views](https://292810646-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGjVLUz4wthGkGlRKM6rM%2Fuploads%2FhXscHvOycpj5QZYrQFa2%2Fmedical-workbench.png?alt=media\&token=9cb55962-10e7-46d8-a4b3-29f766e560b5)

*Synchronized medical views let specialists interpret the same finding across planes and 3D context before committing geometry and structured values.*

### Read the Workbench before annotating

Medical is a resource family inside a typeless project. Medical resources open the native medical Workbench while remaining part of the same project, ontology, workflow, queue, and release system used by other modalities.

### Synchronized DICOM and 3D context

The medical workbench supports:

* axial view;
* sagittal view;
* coronal view;
* 3D view;
* synchronized annotations across views;
* window/level values visible per view;
* contextual document content beside medical imagery;
* multiview and multi-case layout switching.

The product story is not merely “four panes.” The key operational value is that an edit can remain connected across anatomical views, reducing the context switching required to reconcile separate representations of the same study.

### Medical ontology example

An example medical ontology can contain a `spine` mask class with structured properties such as:

* coverage: Cervical, Thoracic, Lumbar, Sacrum, Coccyx;
* a conditional Record property when Sacrum is selected;
* deeper text input when Normal is selected;
* Clinical Finding options including Normal, Degenerative changes, Compression fracture, Scoliosis, and Hardware present.

This shows how geometry, anatomy, and clinical meaning can be kept separate. A mask identifies the spatial region; properties capture structured findings; conditional branches request detail only when relevant.

### Medical formats and ingestion

The SDK supports mixed upload directories containing DICOM, NIfTI, and NRRD alongside common image and document formats. DICOM slices are grouped by `SeriesInstanceUID` into one user-facing medical volume. Internal source slices, pending rows, and failed rows do not appear as separate grid items, queue tasks, or navigation entries.

### From assigned task to review

{% stepper %}
{% step %}

#### 1. Confirm the clinical data context

Verify study, series, orientation, access scope, workflow stage, and applicable Instructions.
{% endstep %}

{% step %}

#### 2. Configure diagnostic views

Set planes, synchronization, window/level, projection, slab thickness, color map, threshold, or 3D opacity as required.
{% endstep %}

{% step %}

#### 3. Navigate the study

Move through slices or frames without advancing the project item.
{% endstep %}

{% step %}

#### 4. Create the annotation

Draw the required geometry from the authoritative active panel and complete ontology values.
{% endstep %}

{% step %}

#### 5. Cross-check context

Inspect the finding across synchronized planes, 3D view, and contextual documents.
{% endstep %}

{% step %}

#### 6. Route to specialist review

Save the current state and submit through the configured clinical review or escalation stage.
{% endstep %}
{% endstepper %}

### Modality-specific quality controls

| Decision                | Production guidance                                                |
| ----------------------- | ------------------------------------------------------------------ |
| Orientation             | Confirm plane and laterality before drawing or accepting geometry. |
| Windowing               | Use the approved viewing configuration for the target finding.     |
| Cross-plane consistency | Inspect extent and boundary across synchronized views.             |
| Sensitive data          | Follow approved access, export, screenshot, and audit practices.   |

### Route the result

Ambiguous findings, unexpected study structure, unsupported data, or clinically significant disagreement require specialist escalation; do not resolve them by convenience.