Search for a patient with identifier

If you already have an identifier for a patient, you can easily locate the patient’s record in an EHR system by searching for a patient with that identifier. Typically, you can use this for: 

  • tying patient records from your system to the patient’s record in the relevant EHR;
  • locating other patient identifiers used in different systems; or 
  • starting a search for patient’s demographics, insurance, general clinical data, test results, prescribed medications, or vaccination history.

Search with patient identifier or demographics?

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

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.

On the flip side, 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.

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

Learn more about searching with patient demographics.

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

What's next?

Does this API action seem like a good fit for your unique workflow? If so, let your Redox rep know! You can begin development by downloading the relevant resource schema (which is noted in the relevant action step below), and deciding which data elements you need. Then head over to our Quickstart guide to dive right in.

If you're not engaged with our sales team yet, talk to a Redoxer to get started.

Action steps

  • 1
    Search for a patient with identifier
    required

You can search for a patient with their unique identifier if you know which identifier type to use for the given EHR system.

For example, if you have the patient's MRN, but the EHR system uses the FHIR® resource ID, you may have to search for the patient with the MRN to locate all identifiers for this patient first; alternatively, you can search for a patient with demographics to locate the resource ID. Then, you can perform additional API actions that require the FHIR® resource ID.

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
identifier
Y
When searching by identifier, you must include the patient's unique identifier within the EHR system that you're searching. This means you must know the unique identifier for that specific system for the search to be successful.

You typically receive either one result or none. Multiple matches may be returned depending on the identifier type that you’re using (since not all patient identifiers are unique) or your integration type.

Canada URL

If you're operating in Canada, you must tweak the Redox hostname slightly. All you need to do is add a ca in that URL like this: https://api.ca.redoxengine.com.

Query Response
Open dropdown
Open dropdown