> For the complete documentation index, see [llms.txt](https://docs.imerit.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.imerit.net/data/importing-assets/bundled-assets/importing-multiple-single-frame-dicom-files-as-one-multi-page-asset.md).

# Importing Multiple Single-Frame DICOM Files as One Multi-Page Asset

You may group together single-frame 2D DICOM files and upload them to Hub as a single multi-page asset, where each page is one of the DICOM files uploaded.

{% hint style="warning" %}
This functionality is only available for single-frame 2D DICOM files.
{% endhint %}

You may upload such multi-DICOM assets using the *Cloud Import* method outlined below.

## Uploading Multi-DICOM Assets

Prepare a JSON like the following, where each URL points to a DICOM you'd like to include in the asset. The order of the URLs will determine the order in which images will be presented to the annotator as pages.

The following JSON will import two assets of four DICOMs each:

```json
[
  {
    "externalId": "my-asset-external-id-1",
    "dataset": [
      "https://url.com/65c18c8b-4513-4a0a-b876-1aeb2e0908ec.dcm",
      "https://url.com/b0b70590-e4cc-42ef-8537-3ee3f7917fed.dcm",
      "https://url.com/38e11364-1ce0-417a-9e38-436468c555ce.dcm",
      "https://url.com/eff59355-03bd-447f-aa47-46028f90c2e6.dcm"
    ]
  },
  {
    "externalId": "my-asset-external-id-2",
    "dataset": [
      "https://url.com/65c18c8b-4513-4a0a-b876-123456789012.dcm",
      "https://url.com/b0b70590-e4cc-42ef-8537-234456566787.dcm",
      "https://url.com/38e11364-1ce0-417a-9e38-876345383488.dcm",
      "https://url.com/eff59355-03bd-447f-aa47-319485019239.dcm"
    ]
  }
]
```

From your project dashboard, go to the *Assets* tab and click on *Add Data*. Then, enter the *Cloud Storage* section and drag and drop your JSON on the file upload field. Then, press on *Upload*. Your multi-DICOM asset(s) will be uploaded.

If your DICOM files are in a private bucket, ensure you select the appropriate [storage integration](/data/storages.md) from the list on the left.

<figure><img src="https://3895963154-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FTcOUG6rfWxqGM0N4db2P%2Fuploads%2Fcs3Hf2tBeh7HWHyhVvl1%2Fimage.png?alt=media&amp;token=ae9a8135-7212-4b1d-bc32-9bbbf6364ecf" alt=""><figcaption></figcaption></figure>

Assets uploaded this way will have a navigation widget at the top, allowing annotators to navigate between the DICOMs.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.imerit.net/data/importing-assets/bundled-assets/importing-multiple-single-frame-dicom-files-as-one-multi-page-asset.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
