Ross ROSS = Recommend OSS · open-source software intelligence for agents

microsoft/fhir-server

A service that implements the FHIR standard observed · 2026-08-28

github.com/microsoft/fhir-server · TSQL · MIT (permissive) observed · 2026-08-28

Health v2 · maintenance only

95/100

  • Activity 99
  • Release rhythm 87
  • Longevity 100
How is this computed?

round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10) — computed 2026-09-03. Adoption (stars, forks) is never an input.

  • gap_med: 6
  • age_days: 2932
  • days_rel: 10
  • days_push: 7
  • n_releases_24m: 130

Full methodology

Adoption not part of the score

1377 stars · 590 forks observed · 2026-08-28

What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-30, confidence not recorded

FHIR Server for Azure is an open-source .NET Core implementation of the HL7 Fast Healthcare Interoperability Resources (FHIR) specification, designed to run in the Microsoft cloud. It exposes RESTful APIs for ingesting, managing, and exchanging interoperable clinical health data, with a pluggable persistence layer including a ready-to-use Azure Cosmos DB provider.

Use cases

  • deploy a FHIR server in the cloud for healthcare data interoperability
  • store and exchange clinical health data using the HL7 FHIR standard
  • self-host a FHIR REST API for patient records
  • normalize clinical data for machine learning workloads
  • manage PHI-compliant health data with role-based access control
  • integrate a FHIR service into custom healthcare applications

When to choose

  • You need a standards-compliant FHIR server optimized for the Azure ecosystem, with ARM templates and AAD/RBAC scripts for rapid provisioning
  • You need PHI-compliant storage and management of clinical health data with a globally replicated database backend
  • You want a logically layered, extensible FHIR foundation with pluggable persistence to customize for your own service

When to avoid

  • You need a full electronic health record (EHR) system rather than a FHIR data interoperability service
  • You want a server unopinionated about cloud provider and prefer not to use Azure tooling or Cosmos DB
  • You need something other than the FHIR standard for health data exchange, such as HL7 v2 messaging or DICOM imaging

Facets

service · maturity active

http-server auth security healthcare apis cloud-computing security dotnet cloud self-hosted fhir hl7-fhir healthcare-interoperability azure clinical-data phi cosmos-db rbac rest-api azure-ad web-server docker

1 source

Member repositories

RepositoryRoleHealth v2
microsoft/fhir-servermain95

For agents

markdown · JSON · MCP: product_card(name="microsoft/fhir-server")

Data as of 2026-08-30T08:39:29.467469+00:00 · Report a problem