The FHIR R4 DiagnosticReport resource represents the results of diagnostic testing performed on a patient, typically by a laboratory, imaging facility, or other diagnostic provider. It includes detailed findings, the tests performed, and may include interpretations or recommendations based on the results.
Health Gorilla exposes DiagnosticReport as part of its FHIR R4 API to support patient-centric access to laboratory, imaging, and other diagnostic results.
Use Cases
- Retrieving diagnostic reports for lab results
- Supporting clinical decision-making with test results
- Generating and sharing diagnostic summaries
- Tracking patient progress via diagnostic reports
Scope and Behavior
This documentation describes the FHIR R4 API interface for DiagnosticReport. 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 DiagnosticReport 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, DiagnosticReport is most commonly accessed as part of patient record retrieval workflows, where diagnostic data may be aggregated from connected clinical sources and normalized for longitudinal review. This resource supports laboratory result review, imaging interpretation access, and diagnostic summary workflows.
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:
diagnosticreport.readfor GETdiagnosticreport.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 |
status | Filters by diagnostic report status | registered, partial, final | token |
category | Filters by diagnostic report category | laboratory, imaging | token |
code | Filters by diagnostic test or observation performed | LOINC codes | token |
date | Filters by diagnostic report date | ge2024-01-01, le2024-12-31 | date |
Commonly Returned Resource Attributes
| Attribute | Description | Example Values | FHIR Data Type |
|---|---|---|---|
subject | Reference to the patient for whom the diagnostic report is issued | Patient/{id} | Reference(Patient) |
status | Current status of the diagnostic report | final | code |
code | Type of diagnostic test or observation performed | LOINC codes | CodeableConcept |
issued | Date and time when the report was issued | 2024-02-12T12:34:56Z | dateTime |
category | Category of the diagnostic report | laboratory | CodeableConcept[] |
result | Observations associated with the diagnostic report | Observation/{id} | Reference[] |
conclusion | Summary of findings or interpretations of the report | Free text | string |
Notifications
The FHIR R4 API does not provide direct resource-change subscriptions for DiagnosticReport. Changes to diagnostic report information may surface through broader notification workflows, depending on enabled Health Gorilla products and configuration.
Error Handling
All DiagnosticReport operations follow standard Health Gorilla error handling, including use of FHIR OperationOutcome for structured responses. For more information, go to: Error Handling.