The FHIR R4 Condition resource is used to document a patient's health conditions, including diagnoses, diseases, and other medical problems. It provides a structured way to record and track clinical conditions throughout a patient's care journey.
Health Gorilla exposes Condition as part of its FHIR R4 API to support patient-centric clinical data access.
Use Cases
- Retrieving a patient's active, resolved, or past medical conditions
- Adding new diagnoses to a patient's problem list
- Updating the verification or clinical status of an existing condition
- Reviewing longitudinal problem history as part of patient record retrieval workflows
Scope and Behavior
This documentation describes the FHIR R4 API interface for Condition. Health Gorilla’s platform may use additional internal services and data standards to acquire, normalize, and route clinical information. Only the FHIR R4–exposed behavior is documented here.
Health Gorilla supports a subset of the HL7 FHIR R4 Condition resource. Not all optional elements defined in the HL7 specification may be stored, indexed, or returned. Unsupported or unrecognized elements may be ignored or normalized during processing.
In Health Gorilla, Condition is most commonly accessed as part of patient record retrieval workflows, where diagnosis and problem data may be aggregated from connected clinical sources and normalized for longitudinal review. This resource supports clinical review, care coordination, and decision-making by exposing structured condition and diagnosis information alongside other patient clinical data.
Authentication
All requests to the FHIR R4 API require OAuth 2.0 authentication using a bearer token. Unauthorized requests return 401 Unauthorized responses.
Required Scopes
condition.readfor GETcondition.writefor POST, PUT, DELETE
For more information, go to: OAuth 2.0 Authentication.
Search Behavior
Searches are scoped to the authenticated tenant. The patient parameter is required for patient-scoped searches and is recommended for most search use cases.
Results are returned as a FHIR Bundle. Pagination may be applied. Use standard FHIR pagination links (Bundle.link) to retrieve additional result pages.
Note: The parameters listed below are not exhaustive and reflect commonly used fields in typical Health Gorilla workflows. Supported parameters and behavior may vary by configuration.
Frequently Used Search Parameters
| Parameter | Description | Example Values | FHIR Data Type |
|---|---|---|---|
patient | Filters by patient | Patient/{id} | Reference |
clinicalStatus | Filters by condition status | active, resolved, inactive | token |
verificationStatus | Filters by verification level | confirmed, unconfirmed | token |
category | Filters by condition category | problem-list-item, encounter-diagnosis | token |
code | Filters by diagnosis code | SNOMED CT, ICD-10 codes | token |
onset-date | Filters by onset date | ge2023-01-01 | date |
Commonly Returned Resource Attributes
| Attribute | Description | Example Values | FHIR Data Type |
|---|---|---|---|
subject | Patient associated with the condition | Patient/{id} | Reference(Patient) |
clinicalStatus | The current status of the condition | active, resolved | CodeableConcept |
verificationStatus | Certainty about the presence of the condition | confirmed, refuted, unconfirmed | CodeableConcept |
category | Category of the condition | problem-list-item, encounter-diagnosis | CodeableConcept[] |
code | SNOMED CT or ICD-10 code for the condition | 44054006 (Diabetes mellitus type 2) | CodeableConcept |
onsetDateTime | When the condition first presented | 2023-05-01 | dateTime |
abatementDateTime | When the condition resolved or was no longer present | 2023-10-01 | dateTime |
recordedDate | Date the condition was recorded | 2023-05-03 | dateTime |
asserter | Who asserted the condition | Practitioner/{id} | Reference(Practitioner) |
Notifications
The FHIR R4 API does not provide direct resource-change subscriptions for Condition. Changes to condition information may surface through broader notification workflows, depending on enabled Health Gorilla products and configuration.
Error Handling
All Condition operations follow Health Gorilla's standard error handling using FHIR OperationOutcome structures. For more information, go to: Error Handling.