The FHIR R4 DeviceUseStatement resource is used to capture details about the use of a medical device for a patient. It records the context, reason, and time of device usage and provides valuable information about the medical devices prescribed or used in a patient's care.
Health Gorilla exposes DeviceUseStatement as part of its FHIR R4 API to support patient-centric clinical data access related to device usage and therapy.
Use Cases
- Recording medical device usage during care
- Documenting device usage for compliance or reporting purposes
- Retrieving historical device data for clinical outcomes review
- Updating device usage information during follow-ups
- Integrating device data into longitudinal care workflows
Scope and Behavior
This documentation describes the FHIR R4 API interface for DeviceUseStatement. 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 DeviceUseStatement 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, DeviceUseStatement is most commonly accessed as part of patient record retrieval workflows, where device usage data may be aggregated from connected clinical systems and normalized for longitudinal review. This resource supports therapy tracking, device management, and clinical documentation use cases.
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
deviceusestatement.readfor GETdeviceusestatement.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 |
device | Filters by device used | Device/{id} | Reference |
status | Filters by status of device use | active, completed | token |
date | Filters by date of device use | ge2024-01-01, le2024-12-31 | date |
Commonly Returned Resource Attributes
| Attribute | Description | Example Values | FHIR Data Type |
|---|---|---|---|
subject | Patient using the device | Patient/{id} | Reference(Patient) |
device | Device being used | Device/{id} | Reference(Device) |
status | Current status of device use | active, completed | code |
reasonCode | Clinical reason for device use | SNOMED CT codes | CodeableConcept[] |
effectiveDateTime | When device use was effective | YYYY-MM-DDTHH:MM:SSZ | dateTime |
recordedOn | When the statement was recorded | YYYY-MM-DDTHH:MM:SSZ | dateTime |
source | Who reported the device usage | Practitioner/{id} | Reference |
Notifications
The FHIR R4 API does not provide direct resource-change subscriptions for DeviceUseStatement. Changes to device usage information may surface through broader notification workflows, depending on enabled Health Gorilla products and configuration.
Error Handling
All DeviceUseStatement operations follow standard Health Gorilla error handling, including use of FHIR OperationOutcome for structured responses. For more information, go to: Error Handling.
Additional Resources
HL7 FHIR DeviceUseStatement