> ## Documentation Index
> Fetch the complete documentation index at: https://docs.encord.com/llms.txt
> Use this file to discover all available pages before exploring further.

# SDK DICOM Basics

This page outlines the basic principles of using the Encord SDK to work with DICOM files.

## Getting started

1. Make sure you have installed all prerequisites and the Encord SDK. If you haven't done so, all the instructions you need to do so are [here](/sdk-documentation/getting-started-sdk/installation-sdk).

2. Ensure you have a public - private key pair to authenticate with Encord. To learn more about authentication in Encord see our documentation [here](/sdk-documentation/general-sdk/authentication-sdk).

<Tip>You can find instructions on creating a public-private key pair in the Encord platform [here](/platform-documentation/General/general-access-keys). </Tip>

## Common entities used when working with DICOM

The following table shows how to refer to various DICOM-related entities when using the Encord SDK.

| **Entity**        | **Name in the SDK**  | **Notes**                                                                                                                                                                                                                                        |
| ----------------- | -------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| Dataset           | `dataset_hash`       | Corresponds to the Dataset ID.                                                                                                                                                                                                                   |
| Data Unit         | `data_hash`          | Corresponds to the data unit's ID.                                                                                                                                                                                                               |
| Project           | `project_hash`       | Corresponds to the Project's ID.                                                                                                                                                                                                                 |
| Ontology          | `ontology_hash`      | Corresponds to the Ontology's ID. Learn how to work with Ontologies [here](/sdk-documentation/ontologies-sdk/ontologies).                                                                                                                        |
| Study ID          | `study_uid`          | Corresponds to the [Study ID as defined in the DICOM standard](https://dicom.innolitics.com/ciods/mr-image/general-study/0020000d). Learn how to work with DICOM metadata [here](/sdk-documentation/dicom-sdk/sdk-dicom-metadata).               |
| Series ID         | `series_uid`         | Corresponds to the [Series ID as defined in the DICOM standard](https://dicom.innolitics.com/ciods/mr-image/general-series/00081250/0020000e). Learn how to work with DICOM metadata [here](/sdk-documentation/dicom-sdk/sdk-dicom-metadata).    |
| Patient ID        | `patient_id`         | Corresponds to the [Patient ID as defined in the DICOM standard](https://dicom.innolitics.com/ciods/rt-plan/patient/00101002/00100020). Learn how to work with DICOM metadata [here](/sdk-documentation/dicom-sdk/sdk-dicom-metadata).           |
| DICOM Instance ID | `dicom_instance_uid` | Corresponds to the [DICOM Instance ID as defined in the DICOM standard](https://dicom.innolitics.com/ciods/rt-structure-set/sop-common/00080018). Learn how to work with DICOM metadata [here](/sdk-documentation/dicom-sdk/sdk-dicom-metadata). |
| Frame Width       | `width`              | Corresponds to the [columns attribute as defined in the DICOM standard](https://dicom.innolitics.com/ciods/rt-dose/image-pixel/00280011). Learn how to work with DICOM metadata [here](/sdk-documentation/dicom-sdk/sdk-dicom-metadata).         |
| Frame Height      | `height`             | Corresponds to the [rows attribute as defined in the DICOM standard](https://dicom.innolitics.com/ciods/rt-dose/general-image/00880200/00280010). Learn how to work with DICOM metadata [here](/sdk-documentation/dicom-sdk/sdk-dicom-metadata). |

<Tip> The hash for any entity can be seen and copied by selecting the entity in the Encord platform, as shown below for an ontology. </Tip>

> <img src="https://storage.googleapis.com/docs-media.encord.com/static/img/ontology-id-highlighted.png" width="500" />

## DICOM metadata

Please see our [tutorial on DICOM metadata](/sdk-documentation/dicom-sdk/sdk-dicom-metadata) to learn how to view metadata pertaining to a series, or individual slices.

## Uploading DICOM data to Encord

To upload DICOM data to Encord:

1. [Create a dataset](/sdk-documentation/datasets-sdk/sdk-create-and-view-datasets).
2. Upload data from [your local machine](/sdk-documentation/index-sdk/sdk-upload-data#upload-local-data-to-an-existing-folder), or register data [from private cloud storage](/sdk-documentation/getting-started-sdk/sdk-register-data-aws).

<Note>To add data from a cloud server, a JSON file specifying the files to be added is required. [Click here](/platform-documentation/Curate/add-files/index-register-cloud-data#json-format) to learn more.</Note>

<Tip>You can also use the Encord platform to [create a dataset, and add data to the dataset](/platform-documentation/Annotate/annotate-datasets/annotate-datasets).</Tip>