# Retrieve a patient's imaging data

You can use this API action to access a patient’s imaging and related metadata from a Picture Archiving and Communications System (PACS) server.

If you’re looking for a provider’s interpretation of imaging, [retrieve a patient’s diagnostic results](/fhir-api-actions/results-and-vitals/retrieve-a-patients-diagnostic-results) instead.

## Use cases

This API action may be a good fit for your organization if you perform any of these use cases:

- Access the original imaging for a patient (e.g., MRI, CT scan, X-ray).
- Find related metadata for a particular image (e.g., study date, study description, size, dimensions, modality).
- Complete AI learning or processing. 

## Supported systems

You can use this API action with the Redox FHIR API.

Your connection's system can return results with their own FHIR or query-based API.

## Things you need to know

<details>
<summary>DICOM terminology</summary>

In case you need a refresher, an imaging study contains results for one patient. 

There’s likely an order for a patient to complete a study. A <u>study</u> defines the type of imaging procedure to be performed, as well as the date, time, and location. 

A study contains one or more series. A <u>series</u> represents each time the patient undergoes some kind of scan. 

A series comprises one or more <u>instances</u> of the 3D image that’s captured. There are several instances to make up one 3D image.

To put it all together: Instances make up a series for a study being completed for an individual patient. Every time a patient undergoes imaging for a study, a new series is created.

</details>

<details>
<summary>Integration between PACS and EHR systems</summary>

The level of integration between a PACS server and an EHR system can vary widely. So, we recommend having a solid understanding of what data you need (e.g., provider interpretation, image, metadata). Then, work with your connection to understand where the data is stored or how you can access it.

</details>

<details>
<summary>Different message types</summary>

Keep in mind that PACS servers may behave differently or use different message types from the DICOM standard. We recommend working with your connection to determine what message types to expect. 

The message types your connection uses determine how your system interacts with a PACS server. You may need to get creative, but we may be able to abstract some of the complexity away for you by translating imaging data to FHIR. First, define your needs and how to meet them with your connection. Then, talk with your Redox technical account manager to see how we can implement your unique use case.

</details>

> **What's next? **
>
> Does this API action seem like a good fit for your unique workflow? Let your Technical Account Manager know! To start development, download the resource schema noted in the related action step. Then decide which data elements you need.
>
> If you’re new to Redox, [use the Quickstart guide](/quickstart-for-redox) to dive in. If you’re not engaged with our sales team yet, [talk to a Redoxer](https://redoxengine.com/forms/contact-us/) to get started.