# Retrieve a signed provider note

You can use this API action to review a list of related documents when searching for a provider’s note for a patient.

> **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:

- Read notes to pre-populate a patient’s progress in the EHR system (e.g., natural language processing).
- Perform follow-up services after a patient visit.
- Use notes for charging for durable medical equipment.

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

> **Using data on demand**
>
> Your connection's system may not support a query-based data exchange, but they may still be willing to provide results with a push-based method.
>
> However, we understand that you may not want to store all that data. Maybe you don't need _all_ the possible results and just want to query for what you want when you need it. If so, you can use this API action via our <u>data on demand</u> service, which stores the connection's data so that you can query from Redox "on demand." [Learn about data on demand](/basics/data-exchange-with-redox/data-on-demand).

## Things you need to know

<details>
<summary>Patient-specific notes</summary>

You can only search and receive signed provider notes from one organization for one patient. However, different clinicians might author notes for the same patient or encounter in the same EHR system. So you could receive multiple notes for one patient from one encounter. But one retrieve call is for one patient. 

If you want to retrieve notes for multiple patients, you must perform this API action for every patient you’re interested in receiving data for.

</details>

<details>
<summary>Document codes</summary>

Documents contain a Logical Observation Identifiers, Names, and Codes (LOINC) to define the type of document.

Sometimes an EHR system uses non-standard codes as well, so you may need to account for EHR-specific codes for document types. Work with your connection to understand which document types you should retrieve.

</details>

<details>
<summary>Document format</summary>

Like the code variation, there’s probably variation in how documents are formatted. Work with your connection to understand the expected format for the document type you’re retrieving. You must configure your system to receive the anticipated format.

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