# Retrieve a patient's diagnoses

You can use this API action to access a patient’s diagnoses, as documented by a specific organization. The EHR system returns a patient’s general diagnoses, problems, or health concerns.  

> **Prerequisite: Having a patient identifier**
>
> To use this API action, you must know the patient identifier. If you don’t have one, [search for a patient with demographics](/fhir-api-actions/patients/search-for-a-patient-by-demographics) to locate an appropriate identifier first.

## Use cases

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

- Provide patient education for specific conditions.
- Offer targeted services to relevant patients.

## Supported systems

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

> **Talk to a Redoxer**
>
> It’s also possible to use the Redox Data Model API for this API action. [Talk to a Redoxer](https://redoxengine.com/forms/contact-us/) to learn about your options.

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

## Things you need to know

<details>
<summary>Organization-specific</summary>

You can only search and receive data from one organization for one patient. If you want a comprehensive list for a patient from multiple organizations, you must perform this API action for every organization you’re interested in receiving data from. 

</details>

<details>
<summary>Diagnosis codes</summary>

Diagnoses are specific to patient encounters. The diagnosed condition is usually provided in International Classification of Diseases (ICD-10) codes. 

Patient problems may come from patient encounters or health concerns reported by the patient outside of a visit. Problems are typically provided in SNOMED codes and can potentially span several encounters. Any reported health concerns aren't specific to a code set and can be anything defined by the EHR system.

</details>

<details>
<summary>Status of conditions</summary>

It’s possible to get a list of patient diagnoses that's missing the onset period, recorded date, or verification status. These fields aren’t required in the response, so it may be difficult to understand where the patient's at in their patient journey. For example, you may not know:

- how recently the patient was diagnosed;
- whether a treatment plan has been made or accepted;
- whether any treatment has already been performed; or
- whether the patient has completed treatment already.

</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.