Sidra Data Platform (version 2025.06: Enigmatic Espinaredo)¶

Released on June 13, 2025

The ring of FHIR...

This release brings a completely new connector for FHIR (Fast Healthcare Interoperability Resources) files, as well as improvements to all existing connectors and core platform services. It also delivers substantial stability and performance enhancements to Sidra’s reverse ETL engine, Sync, reducing operational friction for large-scale data distribution.

Additionally, we continue progressing with our platform-wide upgrade to .NET 8, ensuring Sidra remains aligned with the latest long-term support technologies and is well-positioned for the years to come.

New Connector for FHIR Files¶

This release introduces a new connector for FHIR files, providing native support for ingesting FHIR-compliant JSON documents. This is a foundational step toward enabling data interoperability in the healthcare and insurance sectors. The connector is fully compatible with Sidra’s metadata model and supports automated ingestion of structured FHIR resources such as Patients, Encounters, Observations, and more.

Sidra’s FHIR Files connector is designed to scan and process each JSON file as a collection of standardized FHIR resources, leveraging the embedded resourceType fields to route and catalog each item into its corresponding Entity. This approach ensures schema flexibility while maintaining consistency with Sidra’s core metadata-driven ingestion pipeline. Full documentation and examples are available in the FHIR Files Connector Guide.

Connectors Tech Update¶

All Sidra connectors — including plugins for SQL Server, Azure SQL, Snowflake, SAP HANA, Oracle, DB2, and MySQL — along with the Connector Toolkits, have been fully upgraded to .NET 8. This transition brings performance enhancements, greater maintainability, and alignment with Microsoft’s latest Long-Term Support (LTS) framework, ensuring long-term compatibility within the Azure ecosystem.

In addition, we have standardized the internal folder structure of all connectors to match our modern service layout conventions. This streamlines the development process and simplifies future updates.

We recognize this change may affect partners developing custom connectors, and we are actively reaching out to help them adapt to the updated structure.

Improved Sync jobs¶

We’ve enhanced the performance and reliability of Reverse ETL (Sync) jobs. The following improvements are included:

Internal optimizations to reduce processing time during incremental sync operations.
Increased timeout settings for Data Product Sync job queries, preventing failures in large datasets.

These improvements reduce bottlenecks in data movement and improve stability for production sync workloads.

Data Quality Service Tech Upgrade¶

The Data Quality service has been fully migrated to .NET 8, aligning it with the rest of the modernized Sidra platform. This upgrade delivers performance benefits and ensures long-term support while simplifying the development of future enhancements.

Improvements to Infrastructure Updates¶

We’ve made key improvements to how Sidra handles infrastructure updates and service installation flows:

When updating an existing Data Product, Sidra will now skip infrastructure re-deployment if only the Docker images need updating. This change reduces downtime and avoids unnecessary reconfiguration.
The installation flow for services like Data Quality and API Builder now follows an event-driven deployment model, simplifying orchestration and improving transparency.
These services are now deployed into the Managed Resource Group, reducing complexity and aligning infrastructure layout across environments.

Issues Resolved in Sidra 2025.06¶

These are the issues resolved during this release in Sidra:

Fixed an issue in the Core UI where tooltips for available services were not rendering correctly. #9333
Fixed an exception triggered when retrieving related entities via API. #9209
Fixed a data type mapping issue where tinyint columns from Azure SQL or SQL Server were incorrectly interpreted in the DSU. #9365
Fixed an issue where a failed deployment without infrastructure triggered an unnecessary infrastructure deployment for the Data Product. #9364
Fixed a bug that caused an unnecessary infrastructure deployment for the Data Product after a failed deployment with no infrastructure configured. #9364

Coming Soon¶

We’re already hard at work on the next release of Sidra. Here’s a preview of what’s coming:

Supervisor UI Redesign
A major visual and usability upgrade of the Supervisor interface is underway, bringing a more intuitive and responsive experience to platform administrators.
New DSU Management Service
We’re introducing a dedicated service for managing Data Storage Units (DSUs), decoupling logic from the core and enabling more flexible, scalable infrastructure management.
.NET 8 and Event-Driven Installation Rollout
Our platform-wide upgrade to .NET 8 continues, along with further adoption of the event-based installation model for all services — reducing complexity and improving observability.
Databricks LTS Version Upgrade
Sidra’s Databricks environments will be upgraded to the latest Long-Term Support (LTS) version to ensure compatibility, improved performance, and alignment with Databricks’ roadmap.

Stay tuned — the next version of Sidra will bring both architectural improvements and quality-of-life enhancements across the board.

We Want Your Feedback¶

Your ideas make Sidra better. For suggestions, issues, or questions, please reach out to us at [email protected].