Condition

Overview

The Condition resource provides information about a clinical condition, problem, diagnosis, or other event, situation, issue, or clinical concept that has risen to a level of concern.

Use Cases:

• Recording patient diagnoses and health problems
• Supporting clinical decision-making and care planning
• Tracking condition status and progression over time
• Meeting regulatory requirements for condition documentation

Relationships:

• Patient: References the individual who has the condition
• Encounter: May be linked to the clinical encounter when the condition was identified
• Practitioner: May reference healthcare providers involved in diagnosis or care
• Provenance: Tracks the source and history of condition information

Resource Schema

Key Fields:

Field	Type	Description	Required
id	string	Unique identifier for the resource	Yes
patient	Reference(Patient)	Who has the condition	Yes
clinicalStatus	CodeableConcept	Clinical status (active, recurrence, relapse, inactive, remission, resolved)	No
verificationStatus	CodeableConcept	Verification status (unconfirmed, provisional, differential, confirmed, refuted, entered-in-error)	No
category	CodeableConcept[]	Category of condition (problem-list-item, encounter-diagnosis)	No
severity	CodeableConcept	Severity of the condition	No
code	CodeableConcept	Identification of the condition	No
bodySite	CodeableConcept[]	Anatomical location	No
encounter	Reference(Encounter)	Encounter created as part of	No
onset[x]	dateTime/Age/Period/Range/string	When condition first manifested	No
abatement[x]	dateTime/Age/Period/Range/string/boolean	When condition resolved	No
recordedDate	dateTime	Date record was first recorded	No

JSON Example:

{
    "resourceType": "Condition",
    "id": "f47ac10b-58cc-4372-a567-0e02b2c3d479",
    "meta": {
        "lastUpdated": "2022-08-19T13:58:00.000+00:00"
    },
    "clinicalStatus": {
        "coding": [
            {
                "system": "http://terminology.hl7.org/CodeSystem/condition-clinical",
                "code": "active",
                "display": "Active"
            }
        ]
    },
    "verificationStatus": {
        "coding": [
            {
                "system": "http://terminology.hl7.org/CodeSystem/condition-ver-status",
                "code": "confirmed",
                "display": "Confirmed"
            }
        ]
    },
    "category": [
        {
            "coding": [
                {
                    "system": "http://terminology.hl7.org/CodeSystem/condition-category",
                    "code": "encounter-diagnosis",
                    "display": "Encounter Diagnosis"
                }
            ]
        }
    ],
    "code": {
        "coding": [
            {
                "system": "http://snomed.info/sct",
                "code": "44054006",
                "display": "Diabetes mellitus type 2"
            }
        ]
    },
    "patient": {
        "reference": "Patient/a1b2c3d4-e5f6-7890-abcd-ef1234567890"
    },
    "onsetDateTime": "2020-01-15T10:30:00.000Z",
    "recordedDate": "2022-08-17T12:00:00+00:00"
}

Operations

The Certified API Condition resource supports the following operations. However, support varies by the targeted CareRecord or solution.

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

Read: Retrieves a specific Condition resource by its unique identifier.

• Endpoint: GET /Condition/{id}

Search

Search for conditions using various criteria.

GET Method

Use GET for simple searches with parameters in the query string.

Production

GET /Condition?parameter=value

Preview

GET /Condition?parameter=value

POST Method

Use POST for complex searches with form-encoded parameters.

Production

POST /Condition/_search

Preview

POST /Condition/_search

info

Not all Netsmart solutions support Condition search. See supported operations table above and consult your target solution's documentation for more information.

Search Parameters

Patient-based Search:

Parameter	Type	Required	Description	Example
patient	reference	Yes	REQUIRED Who has the condition?	patient=value
abatement-date	date	No	Date-related abatements (dateTime and period)	abatement-date=value
body-site	token	No	Anatomical location, if relevant	body-site=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
encounter	reference	No	Encounter created as part of	encounter=value
onset-date	date	No	Date related onsets (dateTime and Period)	onset-date=value
recorded-date	date	No	Date record was first recorded	recorded-date=value
severity	token	No	The severity of the condition	severity=value
verification-status	token	No	unconfirmed	verification-status=value
_count	number	No	Number of resources to return per page	_count=value
_offset	number	No	Number of resources to skip	_offset=value
_revinclude	special	No	Include Provenance resource(s) that reference the matched search results. Allowed: "Provenance:target"	_revinclude=value
_sort	string	No	Sort order for results	_sort=value

ID-based Search:

Parameter	Type	Required	Description	Example
_id	string	Yes	The ID of the resource	_id=value
_revinclude	special	No	Include Provenance resource(s) that reference the matched search results. Allowed: "Provenance:target"	_revinclude=value

Examples

Read Examples:

Production

Read Condition by ID

curl -X GET https://fhir.netsmartcloud.com/provider/patient-access/v2/{tenant-id}/Condition/456 \
    -H "Authorization: Bearer {token}" \
    -H "Accept: application/fhir+json"

Preview

Read Condition by ID

curl -X GET https://fhirtest.netsmartcloud.com/provider/patient-access/v2/{tenant}/Condition/456 \
    -H "Authorization: Bearer {token}" \
    -H "Accept: application/fhir+json"

Search Examples:

Production

Search by Patient

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

Search by Patient and Clinical Status

curl -X POST https://fhir.netsmartcloud.com/provider/patient-access/v2/{tenant-id}/Condition/_search \
    -H "Authorization: Bearer {token}" \
    -H "Accept: application/fhir+json" \
    -H "Content-Type: application/x-www-form-urlencoded" \
    -d "patient=Patient/123" \
    -d "clinical-status=active"

Preview

Search by Patient

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

Search by Patient and Clinical Status

curl -X POST https://fhirtest.netsmartcloud.com/provider/patient-access/v2/{tenant}/Condition/_search \
    -H "Authorization: Bearer {token}" \
    -H "Accept: application/fhir+json" \
    -H "Content-Type: application/x-www-form-urlencoded" \
    -d "patient=Patient/123" \
    -d "clinical-status=active"

Integration Patterns

Common Workflows:

• Retrieve all conditions for a patient during care planning
• Filter active conditions for clinical decision support
• Include provenance data to track condition information sources
• Cross-reference with encounters to understand diagnosis context

Related Resources:

• Patient - Individual who has the condition
• Encounter - Clinical encounter when condition was identified
• Practitioner - Healthcare provider involved in diagnosis
• Provenance - Source and history tracking

Error Handling

For detailed error codes and handling procedures, see the Error Handling Guide.

Supported Profiles

This resource supports the following FHIR profiles as defined in the CapabilityStatement:

• US Core Condition Encounter Diagnosis Profile
• US Core Condition Problems and Health Concerns Profile
• Base FHIR R4 Condition Resource