# Search for a patient with demographics

You can use this API action to retrieve a patient's record from an EHR system with demographics. This is helpful if you don't know any of the patient's identifiers. 

> **Search with patient identifier or demographics? **
>
> You can locate a patient’s record in an EHR system with either an identifier or with demographics. So how do you know which to use and when?
>
> Using <u>patient demographics</u>:
>
> - allows you as an outsider (stay gold, Ponyboy) to search a system that you don’t have access to; and
> - locates the patient identifier if you don't have one already.
>
> This back-door alternative is fantastic if you have the patient’s info, minus the appropriate identifier. We can still help you find the right patient with a little extra time.
>
> On the flip side, using the <u>patient identifier</u>:
>
> - saves time since you only populate one field instead of a handful of demographics fields; and
> - likely locates the correct patient since identifiers are typically more unique than patient demographics.
>
> The catch is that you have to already have a patient identifier, like the MRN, on hand. If you do, we definitely recommend this option. We also recommend validating you found the right patient (because you don't ever make typos, right?) by confirming the returned patient's demographics match your patient. Once confirmed, you can start retrieving the patient’s relevant clinical data. [Learn more about searching with patient identifier](/fhir-api-actions/patients/search-for-a-patient-with-identifier).

## Use cases

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

- Tie patient records from your system to the patient’s record in the relevant EHR.
- Fill the gaps in demographics you have for a specific patient by using a few data points to locate a more comprehensive set of data.
- Search for a patient in a large integration network, like the Carequality Interoperability Framework.

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

> **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>Not your typical Google search</summary>

This is a great option for quickly locating a patient, but that _doesn't_ mean that it works like a typical Google or SQL database search. None of the fields automatically populate, nor can you only use one demographic data point. Also, the purpose is to find matches for a _specific_ patient, not a list of potential patients matching a broad set of criteria. In other words, you have to know who you’re looking for. 

You _must_ include the following to search for a patient: 

- given name 
- family name
- birthdate
- gender (not required with data on demand)

Typically, you must also include _at least one_ of the following, but these requirements differ based on the EHR system you're integrating with: 

- Social Security number (SSN)
- address
- email address
- phone number

We recommend using as much demographic information as possible, though; otherwise, you may find other patients with the same basic demographic information.

> **Fields you can't search by**
>
> For easy reference, here are some common data points that you _can’t_ use to search for a patient:
>
> - time range
> - diagnosis
> - insurance member ID
> - other insurance data points (insurance data is for entirely different resources, like `Claim`)

</details>

<details>
<summary>Matching method</summary>

There's a caveat to using as much demographic information as possible, which has to do with exact, partial, or fuzzy matching. _Spoiler alert_: it's better to use as much demographic information as possible if the connection's system does partial or fuzzy matching.

The method of matching is dependent on:

- your connection and the EHR system they use; and
- whether you use <u>data on demand</u>.

[Learn about options for patient searches and matching methods](/basics/data-exchange-with-redox/options-for-patient-searches).

</details>

<details>
<summary>Carequality Interoperability Framework</summary>

You may qualify to join Carequality if your organization employs staff that provides treatment to patients (e.g., physicians, nurses, coaches, therapists). This would allow you to search for a patient across multiple nationwide organizations without needing to connect to each organization individually. 

Using Network Onramps, you can search for a patient across multiple Carequality participants with just one search. [Learn about Network Onramps](/how-to-use-redox/interact-with-clinical-networks).

</details>

<details>
<summary>Requesting additional patient data</summary>

Once you locate a patient, you can use other API actions to gather more detailed patient data.

If your connection uses FHIR, you'll likely need the resource ID to locate patient data. If you don't have the resource ID, search for a patient with demographics to return all known patient identifiers, including the resource ID.

Alternatively, you can search with a patient identifier that you already have to request the resource ID. [Learn more about searching for a patient with an identifier](/fhir-api-actions/patients/search-for-a-patient-with-identifier).

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