# microsoft/fhir-server

A service that implements the FHIR standard

Repository: https://github.com/microsoft/fhir-server
Canonical: https://ross.abutalabs.com/products/fhir-server
Language: TSQL
License: MIT
License Family: permissive
Last push: 2026-08-26T18:26:37+00:00

## Health v2 (maintenance only)
Score: 95/100 (v2, computed 2026-09-03T02:39:23.370411+00:00)
- activity 99, release rhythm 87, longevity 100
- inputs: {"age_days": 2932, "days_push": 7, "days_rel": 10, "gap_med": 6, "n_releases_24m": 130}
- flags: none
- formula: round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10)

## Adoption (not part of the score)
Stars 1377, forks 590 (observed 2026-08-28T04:04:33.378999+00:00)

## What it is
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
- artifact type: service
- maturity: active
- function: http-server, auth, security
- domain: healthcare, apis, cloud-computing, security
- platform: dotnet, cloud, self-hosted
- tags: fhir, hl7-fhir, healthcare-interoperability, azure, clinical-data, phi, cosmos-db, rbac, rest-api, azure-ad, web-server, docker

## Member repositories
- microsoft/fhir-server (main) score 95

## Provenance
- Observed fields: from GitHub, fetched 2026-08-28T04:04:33.378999+00:00.
- Health v2: computed from the inputs above; adoption is never an input.
- Inferred fields (summary, facets, guidance): AI-extracted, prompt v1, taxonomy v1, on 2026-08-30T04:40:26.779062+00:00, confidence not recorded.
  - readme: https://github.com/microsoft/fhir-server (fetched 2026-08-28T04:04:33.378999+00:00, sha e77f8f2d0f57)
- Data as of 2026-08-30T08:39:29.467469+00:00.