Understand this story
On November 17, 2026, Databricks launched an OpenSharing-based integration that connects AWS HealthLake's FHIR data directly as a shared catalog, without export pipelines or data copying, and can be uniformly governed by Unity Catalog. Users can query this data in notebooks and dashboards, and can also ask questions in natural language through Genie One, for example, "What is the monthly trend of average A1C?" The system generates SQL and returns tables and charts. The integration works through a custom OpenSharing server running on a Databricks App, using temporary Lake Formation credentials to resolve Iceberg snapshots and presign data files, with the Databricks compute side reading directly from S3. The integration has now been published along with the official Databricks blog.
AI-generated from public reports
Latest development · Report
Querying clinical data in natural language: Databricks connects AWS HealthLake through OpenSharing and…Developments
1 confirmed developments
Databricks connects AWS HealthLake with Unity Catalog using OpenSharing
Source:Databricks Blog
Reports and discussion timeline
Browse reports and discussion by time. Their evidence levels remain distinct.
Nov 17
Databricks BlogFirst-party
Querying clinical data in natural language: Databricks connects AWS HealthLake through OpenSharing and…
With OpenSharing, Databricks connects FHIR data from AWS HealthLake directly as a shared catalog, with no export pipeline or data copying required, and it can be governed centrally by Unity Catalog. Users can query this data in notebooks and dashboards, and can also ask questions in natural language through Genie One—for example, "What is the monthly trend of average A1C?"—and the system generates SQL and returns tables and charts. The integration uses a custom OpenSharing server running on a Databricks App to resolve Iceberg snapshots with temporary Lake Formation credentials and presign data files, and the Databricks compute side reads directly from S3.