Search for a patient with demographics

If you want to locate a patient's record in an EHR system but you don't have a patient identifier, you can search for a patient with demographics instead. Typically, you can use this for: 

  • tying patient records from your system to the patient’s record in the relevant EHR;
  • filling the gaps in demographics you have for a specific patient by using a few data points to locate a more comprehensive set of data; or
  • searching for a patient in a large integration network like the Carequality Interoperability Framework.

Search with patient identifier or demographics?

There are two ways to locate a patient in an EHR system: with demographics or with an identifier. So how do you know which to use and when?

Using the patient demographics:

  • 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 patient identifier:

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

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

It's possible that your connection's system can't 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 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 data on demand service, which stores the connection's data so that you can query from Redox "on demand." Learn more about data on demand.

Things you need to know

Action steps

  • 1
    Search for a patient with demographics
    required

This table has notes about how to use parameters for this API action specifically, but it's not exhaustive. Refer to the resource schema for more details.

Query parameter
Required
Notes
given
Y
When searching by demographics, you must include the patient's given name (typically first name)—along with any other demographics you want to include—for the search to be successful.
family
Y
When searching by demographics, you must include the patient's family name (typically last name)—along with any other demographics you want to include—for the search to be successful.
birthdate
Y
When searching by demographics, you must include the patient's date of birth—along with any other demographics you want to include—for the search to be successful.

Depending on the EHR system, you may receive one result per search, a list of results, or no results at all. 

Query Response
Open dropdown
Open dropdown