Retrieve a patient's diagnoses

You can use this action if you want 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. Typically, you can use this for:

  • Offering patient education for specific conditions; or
  • Offering targeted services to relevant patients.

Patient identifier required

To use this API action, you must know the patient identifier. If you don’t, you must locate the appropriate identifier first. Learn how to search for a patient with demographics.

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 to learn about your options if you want to use alternative integration methods.

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

Special considerations

Organization-specific

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

Codes

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 are not specific to a codeset and can be anything defined by the EHR system.  

Status of conditions

It’s possible that you may 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 is 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. 

Action steps

Prerequisites

The following Actions must be completed before attempting the steps below.

Steps

  • 1
    Retrieve a patient's diagnoses
    required

Request parameters

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.

Parameter
Required for this action
Notes
patient.identifier
Y
You must include the patient's resource.id. If you don't have this, you can find it using a search for a patient with demographics.
category
Y
Set to problem-list-item.

Returned results

The response contains one or more conditions for an individual patient. You can find the total number of included medications in the total array for FHIR® responses.

Query/Response
Open dropdown
Open dropdown