Condition

Overview

The Condition resource represents clinical conditions, problems, diagnoses, or other events that have risen to a level of clinical concern. This resource is central to clinical documentation and care planning workflows.

Important: Always validate Condition resource support and available operations by retrieving the current CapabilityStatement from /metadata before implementing integrations.

Resource Schema

The Condition resource follows the HL7 FHIR R4 Condition specification with Netsmart-specific extensions.

Key elements include:

clinicalStatus - Active, recurrence, relapse, inactive, remission, resolved
verificationStatus - Unconfirmed, provisional, differential, confirmed, refuted, entered-in-error
category - Problem list item, encounter diagnosis, health concern
severity - Severity of the condition
code - Identification of the condition (ICD-10, SNOMED CT)
subject - Patient with the condition
encounter - Encounter when condition was first asserted
onset - When the condition started
recordedDate - When condition was recorded

Example Condition Resource

{
  "resourceType": "Condition",
  "id": "12345",
  "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",
      "display": "Encounter Diagnosis"
    }]
  }],
  "severity": {
    "coding": [{
      "system": "http://snomed.info/sct",
      "code": "24484000",
      "display": "Severe"
    }]
  },
  "code": {
    "coding": [{
      "system": "http://hl7.org/fhir/sid/icd-10-cm",
      "code": "E11.9",
      "display": "Type 2 diabetes mellitus without complications"
    }]
  },
  "subject": {
    "reference": "Patient/12345"
  },
  "encounter": {
    "reference": "Encounter/67890"
  },
  "onsetDateTime": "2023-06-15",
  "recordedDate": "2024-01-15"
}

Supported Profiles

This API supports the following FHIR profiles:

HL7 FHIR R4 Condition

Operations

info

Support for the different types of Conditions may vary by CareRecord. Please consult your target solution's documentation for more information.

The General Purpose FHIR R4 Patient resource supports the following standard operations. However, support varies by the targeted CareRecord or solution.

CareRecord / Solution	Create	Read	Update	Search
GEHRIMED	-	Yes	-	Yes
myAvatar	Yes	Yes	Yes	Yes
myEvolv	-	Yes	-	Yes
myUnity	-	Yes	-	Yes
Referral Manager	-	-	-	-

Search

This resource supports a combination of standard and custom search parameters in addition to the common parameters.

Standard Parameters

Name	Type	Description
category	token	Category of the Condition. Possible values are: pregnancy, encounter-diagnosis, health-concern (to obtain the "Health Concern" segment of the CCD), and problem-list-item.
encounter	reference	Unique identifier of the encounter.
onset-date	date	Date related onsets (dateTime and Period) of Condition.
patient	reference	Unique identifier of the patient.
recorded-date	date	Assessment/Recorded Date of Condition

Custom Parameters

Name	Type	Description
end	date	Deprecated. Use `recorded-date` parameter with `le` prefix instead.
ids	string	This is use to request a list of Conditions by their id. Must be used with the `category` parameter and cannot be used with other parameters.
practitioner	id	Unique identifier of the Practitioner.
start	date	Deprecated. Use `recorded-date` parameter with `ge` prefix instead.

Search Examples

The POST method is recommended as it keeps health information out of the URL.

Production
Preview

Search by Patient and Condition Category
curl -X POST https://fhir.netsmartcloud.com/v4/Condition/_search \
    -H "Authorization: {Bearer Token}" \
    -H "Accept: application/fhir+json" \
    -H "Content-Type: application/x-form-urlencoded" \
    -d "patient=Patient/234" \
    -d "category=encounter-diagnosis"

Search by IDs
curl -X POST https://fhir.netsmartcloud.com/v4/Condition/_search \
    -H "Authorization: {Bearer Token}" \
    -H "Accept: application/fhir+json" \
    -H "Content-Type: application/x-form-urlencoded" \
    -d "category=encounter-diagnosis" \
    -d "ids=98765"
    -d "ids=45678"

Search by Patient and Condition Category
curl -X POST https://fhirtest.netsmartcloud.com/v4/Condition/_search \
    -H "Authorization: {Bearer Token}" \
    -H "Accept: application/fhir+json" \
    -H "Content-Type: application/x-form-urlencoded" \
    -d "patient=Patient/234" \
    -d "category=encounter-diagnosis"

Search by IDs
curl -X POST https://fhirtest.netsmartcloud.com/v4/Condition/_search \
    -H "Authorization: {Bearer Token}" \
    -H "Accept: application/fhir+json" \
    -H "Content-Type: application/x-form-urlencoded" \
    -d "category=encounter-diagnosis" \
    -d "ids=98765"
    -d "ids=45678"

Error Handling

For information about error responses when working with Condition resources, see Common Errors.

Common Condition-related errors include:

Missing required patient reference
Invalid clinical or verification status codes
Unsupported condition categories
Invalid diagnosis codes or terminology systems

Integration Patterns

Problem List Management

Retrieve active conditions for clinical decision support:

# Get patient's active problem list
curl -X GET "https://fhir.netsmartcloud.com/v4/Condition?patient=12345&category=problem-list-item&clinical-status=active" \
    -H "Authorization: Bearer {token}" \
    -H "Accept: application/fhir+json"

Encounter Diagnosis Tracking

Link conditions to specific encounters:

# Get encounter diagnoses
curl -X GET "https://fhir.netsmartcloud.com/v4/Condition?encounter=67890&category=encounter-diagnosis" \
    -H "Authorization: Bearer {token}" \
    -H "Accept: application/fhir+json"

Care Planning Integration

Conditions drive care plan development:

# Get conditions with related care plans
curl -X GET "https://fhir.netsmartcloud.com/v4/Condition?patient=12345&_revinclude=CarePlan:addresses" \
    -H "Authorization: Bearer {token}" \
    -H "Accept: application/fhir+json"

Clinical Decision Support

Conditions inform medication and treatment decisions:

# Get conditions by onset date range
curl -X GET "https://fhir.netsmartcloud.com/v4/Condition?patient=12345&onset-date=ge2024-01-01" \
    -H "Authorization: Bearer {token}" \
    -H "Accept: application/fhir+json"

Relationships to Other Resources

The Condition resource connects to many other clinical resources:

Patient - The individual with the condition
Encounter - Clinical encounters where conditions are diagnosed
CarePlan - Care plans addressing specific conditions
Goal - Treatment goals related to conditions
MedicationRequest - Medications prescribed for conditions
Procedure - Procedures performed to treat conditions
Observation - Clinical observations supporting diagnoses
Practitioner - Healthcare providers diagnosing conditions

Support

For questions about Condition resource implementation or clinical workflow integration, contact Netsmart support through your designated support channels.

Overview​

Resource Schema​

Example Condition Resource​

Supported Profiles​

Operations​

Search​

Standard Parameters​

Custom Parameters​

Search Examples​

Error Handling​

Integration Patterns​

Problem List Management​

Encounter Diagnosis Tracking​

Care Planning Integration​

Clinical Decision Support​

Relationships to Other Resources​

Support​