OCI Device Data FHIR Service
Build standards-based healthcare applications on a managed FHIR server for device data. Use versioned Fast Healthcare Interoperability Resources Release (FHIR) R4 and R6 REST APIs to store, search, and manage supported healthcare resources on Oracle Cloud Infrastructure (OCI).
Build device-data applications with FHIR R4 and R6 APIs on OCI
What is OCI Device Data FHIR Service?
Healthcare teams often need to connect device observations from multiple applications and gateways without creating another bespoke clinical data layer. OCI Device Data FHIR Service provides a managed FHIR server built on OCI and Oracle Autonomous Database, helping developers work with health data from healthcare devices, applications, and third-party systems through versioned FHIR R4 and R6 APIs.
The service is designed for teams building device gateways, remote-monitoring applications, EHR extensions, middleware integrations, and operational workflows. Developers can work with supported FHIR resources while administrators retain OCI controls for authentication, authorization, networking, logging, metrics, events, and service operations.
As a healthcare or Internet of Things (IoT) application developer, you can create, read, update, delete, and search supported resources; and use version history, logical deletion, and controlled purge operations to manage data through its lifecycle.
How does OCI Device Data FHIR Service work?
First, a connector, gateway, or application maps source data to the supported FHIR resource model. The service then provides the managed validation, storage, search, lifecycle, and notification layer for those FHIR resources.
1. Map and send: Your integration maps source records to resources, such as Patient, Device, Observation, Encounter, Location, or Provenance, then sends FHIR JavaScript Object Notation (JSON) to the versioned R4 or R6 endpoint.
2. Validate and authorize: The service validates the request against FHIR and implementation requirements, applies resource- and operation-level OAuth scopes, and returns a FHIR resource, Bundle, or OperationOutcome response.
3. Store and manage: The managed FHIR server stores the resource on its OCI and Oracle Autonomous Database foundation and supports lifecycle features, such as versioning, history, logical delete, hard delete, and purge operations, where the deployment capability and policy permit them.
4. Search, subscribe, and operate: Applications search using supported parameters and receive search-result Bundles. FHIR R6 SubscriptionTopic and Subscription resources can deliver authorized Hypertext Transfer Protocol Secure (HTTPS) notifications; administrators monitor service operations through OCI controls.
NOTE: For every deployment and FHIR version, review the live Capability Statement before enabling optional resources, search parameters, interactions, or operations.
Why choose OCI Device Data FHIR Service?
Build to standards across FHIR versions
Use distinct FHIR R4 and R6 endpoints from one OCI service. Published and live capability statements identify the supported resources, interactions, operations, formats, and search parameters for each version, helping teams build version-aware customers without assuming that every R4 feature is available in R6 or vice versa.
Limit FHIR server infrastructure work
The managed server is built on OCI and Oracle Autonomous Database. Development teams can focus on data mapping, application logic, and clinical workflows while using OCI-native service operations, work requests, and monitoring.
Enable AI-powered applications
Oracle Autonomous Database 26ai is a converged, AI-native database that unifies relational, JSON, graph, and vector data alongside IoT and streaming workloads. The integrated FHIR service exposes standards-based REST APIs, enabling devices to send interoperable healthcare data directly into the database. Because FHIR data is stored natively, there is no need for a separate FHIR repository or extract, transform, and load (ETL) process. Data is immediately available for analytics, and AI, all from a single platform.
Apply precise access and delivery controls
OCI Identity and Access Management (IAM) policies govern the service infrastructure, while OCI Identity Domains OAuth scopes authorize FHIR data-plane actions by resource and operation. OCI Networking and OCI Secrets in Vault can help restrict access and protect authorization values used by outbound subscription notifications.
Enable searchable and event-ready device data
Use FHIR search parameters, modifiers, chained searches, pagination, resource history, and versioned reads to retrieve the data applications need. FHIR R6 topics and subscriptions can support near real-time workflows, while service metrics, logs, events, and work requests help administrators diagnose and operate the deployment.
Try it now
Before users and applications connect, administrators can configure the required IAM groups and policies, network access, service dependencies, and OCI Identity Domains applications and OAuth scopes. Then, they can create an instance from Developer Services in the Oracle Cloud Console, retrieve its FHIR endpoint, and call the versioned R4 or R6 base path.
Sign in to Oracle Cloud | Read the documentation
Region availability and service limits: See the documentation for the current list before planning a deployment. View the overview.
OCI Device Data FHIR Service use cases
Use the service as a standards-based FHIR layer for healthcare device and clinical data workflows. The following examples describe application patterns documented for the service.
Connecting patient data
Build patient and provider applications that receive data through vendor connectors, patient applications, or device gateways; map measurements to Device, DeviceAssociation, Observation, and Provenance resources; and make authorized data available to care teams. FHIR R6 subscriptions can notify provider systems when relevant resources change.
Clinical orders, specimens, and results
Model an order with ServiceRequest, track the associated Specimen, and record the result as an Observation. Applications can search by patient, code, category, date, device, specimen, status, and other supported parameters to assemble the workflow context.
Connected clinical devices and gateways
Represent discrete measurements, spot checks, continuous signals, waveforms, laboratory results, and near real-time location patterns with supported FHIR resources. Deterministic identifiers and Provenance can help applications trace gateway messages and avoid duplicate Observation records during retries.
Device and patient location workflows
Use Device, Encounter, and Location resources to represent equipment and patient location. Where supported, FHIR R6 subscriptions can notify approved HTTPS endpoints about relevant resource changes for operational workflows.
Device manufacturer integration
Create authorized backend integrations that search device inventory, retrieve permitted patient and device-sourced observations, and optionally receive change notifications. Resource-level scopes help limit each integration to the data and operations it requires.
Get Started with OCI Device Data FHIR Service
OCI Device Data FHIR Service is a general-purpose developer service and is not intended to provide diagnostic or treatment recommendations. Customers and partners are responsible for validating their products and solutions and ensuring compliance with any applicable regulatory requirements.