An open-source FHIR server developed in C#, supporting multiple FHIR versions for healthcare data interoperability.
Spark is an open-source FHIR server developed in C# that implements a major part of the FHIR specification for healthcare data interoperability. It allows developers to set up and run a FHIR-compliant server to manage and exchange healthcare data electronically. The project supports multiple FHIR versions, including R4, STU3, and DSTU2, and is tested during HL7 WGM Connectathons.
Healthcare software developers, system integrators, and organizations needing a FHIR-compliant server for electronic health record (EHR) systems, health data exchanges, or interoperability projects.
Developers choose Spark for its robust implementation of FHIR standards, ease of deployment via Docker or NuGet, and its open-source nature, which allows customization and avoids vendor lock-in compared to proprietary FHIR solutions.
Firely and Incendi's open source FHIR server
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Compatible with R4, STU3, and DSTU2 FHIR versions, providing flexibility for different healthcare standards and legacy systems, as evidenced by separate branches and Docker setups.
Offers pre-configured Docker images and docker-compose examples for quick setup and self-hosting, simplifying deployment with commands provided in the README.
Available as NuGet packages, allowing developers to embed and customize the FHIR server within .NET applications easily, with a Quickstart Tutorial for guidance.
Tested during HL7 WGM Connectathons, ensuring compliance and reliability with FHIR specifications for interoperability, building trust in real-world scenarios.
DSTU2 is no longer maintained, and there's no support for FHIR R5, which might not meet the needs of projects requiring the latest or fully supported standards.
Heavily reliant on .NET and C#, making it less accessible for teams using other programming languages or frameworks without significant integration effort.
Requires self-hosting via Docker or .NET servers, lacking built-in cloud scaling or managed service options, which adds operational overhead for deployment and maintenance.