Condition

Overview

The Condition resource represents clinical conditions, problems, diagnoses, or other events that have risen to a level of concern. This includes both active and resolved conditions that are important for patient care and clinical decision-making.

Resource Schema

Key fields in the Condition resource:

{
  "resourceType": "Condition",
  "id": "example-condition-123",
  "clinicalStatus": {
    "coding": [
      {
        "system": "http://terminology.hl7.org/CodeSystem/condition-clinical",
        "code": "active"
      }
    ]
  },
  "verificationStatus": {
    "coding": [
      {
        "system": "http://terminology.hl7.org/CodeSystem/condition-ver-status",
        "code": "confirmed"
      }
    ]
  },
  "category": [
    {
      "coding": [
        {
          "system": "http://terminology.hl7.org/CodeSystem/condition-category",
          "code": "encounter-diagnosis"
        }
      ]
    }
  ],
  "code": {
    "coding": [
      {
        "system": "http://snomed.info/sct",
        "code": "44054006",
        "display": "Diabetes mellitus type 2"
      }
    ]
  },
  "subject": {
    "reference": "Patient/123456"
  },
  "onsetDateTime": "2020-01-15"
}

Operations

The Condition resource supports Read and Search operations. Support varies by CareRecord solution.

CareRecord / Solution	Read	Search
GEHRIMED	✅	✅
myAvatar	✅	✅
myEvolv	✅	✅
myUnity	✅	✅
TheraOffice	✅	✅

Read

Retrieves a specific Condition resource by ID.

HTTP Method: GET
URL: /Condition/{id}

Examples

Production

curl -X GET https://fhir.netsmartcloud.com/uscore/v1/Condition/123456 \
    -H "Authorization: Bearer {token}" \
    -H "Accept: application/fhir+json"

Preview

curl -X GET https://fhirtest.netsmartcloud.com/uscore/v1/Condition/123456 \
    -H "Authorization: Bearer {token}" \
    -H "Accept: application/fhir+json"

Search

Retrieves Condition resources matching specified criteria.

HTTP Method: GET or POST
URL: /Condition or /Condition/_search

Search Parameters

Patient-based Search:

Parameter	Type	Required	Description	Example
patient	reference	Yes	REQUIRED Who has the condition	patient=value
category	token	No	The category of the condition	category=value
clinical-status	token	No	The clinical status of the condition	clinical-status=value
code	token	No	Code for the condition	code=value
onset-date	date	No	Date related onsets (dateTime and Period)	onset-date=value
page	string	No	Zero-based page index	page=value
_revinclude	special	No	Include Provenance resource(s) that reference the matched search results. Allowed: "Provenance:target"	_revinclude=value

ID-based Search:

Parameter	Type	Required	Description	Example
category	token	No	The category of the condition	category=value
clinical-status	token	No	The clinical status of the condition	clinical-status=value
code	token	No	Code for the condition	code=value
onset-date	date	No	Date related onsets (dateTime and Period)	onset-date=value
page	string	No	Zero-based page index	page=value
_revinclude	special	No	Include Provenance resource(s) that reference the matched search results. Allowed: "Provenance:target"	_revinclude=value

Examples

POST Method (Recommended)

Production

Search by Patient

curl -X POST https://fhir.netsmartcloud.com/uscore/v1/Condition/_search \
    -H "Authorization: Bearer {token}" \
    -H "Accept: application/fhir+json" \
    -H "Content-Type: application/x-form-urlencoded" \
    -d "patient=Patient/123"

Preview

Search by Patient

curl -X POST https://fhirtest.netsmartcloud.com/uscore/v1/Condition/_search \
    -H "Authorization: Bearer {token}" \
    -H "Accept: application/fhir+json" \
    -H "Content-Type: application/x-form-urlencoded" \
    -d "patient=Patient/123"

GET Method

Production

Search by Patient

curl -X GET https://fhir.netsmartcloud.com/uscore/v1/Condition?patient=Patient/123 \
    -H "Authorization: Bearer {token}" \
    -H "Accept: application/fhir+json"

Preview

Search by Patient

curl -X GET https://fhirtest.netsmartcloud.com/uscore/v1/Condition?patient=Patient/123 \
    -H "Authorization: Bearer {token}" \
    -H "Accept: application/fhir+json"

Integration Patterns

Common Workflows

1. Problem List - Retrieve all active conditions for a patient
2. Diagnosis History - Search for specific conditions or by category
3. Clinical Decision Support - Use condition data for care planning

Relationships to Other Resources

The Condition resource relates to:

• Patient - Subject of the condition
• Encounter - Healthcare encounter when condition was diagnosed
• Practitioner - Who diagnosed or manages the condition
• CarePlan - Care plans addressing the condition
• Procedure - Procedures related to treating the condition

Error Handling

For common errors and troubleshooting guidance, see Common Errors.

Supported Profiles

Profiles supported by this resource (as defined in the CapabilityStatement):

• HL7 FHIR R4 Condition
• US Core Condition Encounter Diagnosis
• US Core Condition Problems and Health Concerns