# DICOM

## Interactive labeling models

Medical 3D volumes (CT/MRI) can have hundreds of slices per plane. After DICOM data is imported to Supervisely, slices are generated in 3 planes: axial, sagittal and coronal. Even though segmentation is done on 2D images, you always know each slice's location in the 3D volume. In Supervisely DICOM labeling tool you can label volume slices as usual 2D images with the help of interactive segmention models.

<figure><img src="https://github.com/user-attachments/assets/073e1cca-1b12-4820-9240-14cc506f0ca7" alt=""><figcaption></figcaption></figure>

Interactive segmentation models like SAM, RITM and ClickSeg can significantly reduce annotation time - a single slice can be labeled in just few clicks:

{% embed url="<https://github.com/user-attachments/assets/4981345f-1043-42df-b111-f360c00e2a5e>" %}

This process is repeated for each plane, but not every slice needs to be annotated - you can label only key slices and use [Volume Interpolation](https://ecosystem.supervisely.com/apps/volume-interpolation) app which reconstructs the object across other slices, with the ability to preview and edit in 3D.

## Volume interpolation

The Volume Interpolation app uses an [ITK-based implementation](https://github.com/KitwareMedical/ITKContourInterpolation) of morphological contour interpolation. Interpolation is done by first determining correspondence between shapes on adjacent segmented slices by detecting overlaps, then aligning the corresponding shapes, generating a transition sequence of one-pixel dilations, and taking the median as a result.

{% embed url="<https://github.com/user-attachments/assets/75c58ce7-28e6-41e1-9494-0dab021e0187>" %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.supervisely.com/labeling/overview/dicom.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.