FHIR

Page tree


Introduction

This page lists FHIR servers that are publicly available for testing. These are public services provided by volunteers and HL7 makes no representations concerning their safety or reliability.

In order to avoid spam etc., the servers are generally password protected. A contact is provided to get a password.

BTW: List of publicly available test data (some of these test servers preload some of this data):

For servers specifically for Connectathons see Connectathon Test Servers.

Status

The status of publicly available FHIR servers is monitored using UptimeRobot at https://stats.uptimerobot.com/9DArDu1Jo. If you would like a publicly available FHIR server added to the UptimeRobot status page, email [Sean McIlvenna[1]].

Servers

Note that these servers are testing servers. They may be sporadically unavailable, and as the FHIR specification is a moving target, they may not always implement the latest version, or do so correctly.

  • Firely Server (formerly Vonk) - .NET based FHIR Server by Firely
  •   mock.health — Hosted Synthea-based synthetic FHIR R4 sandbox
    • Hosted sandbox of synthetic patient data generated with Synthea, enriched with a Markov progression module trained on real de-identified patient                                           journeys for clinical diversity (multi-condition, realistic comorbidities).  Includes DICOM imaging, diagnostic reports, and clinical notes alongside standard resources. 
    • FHIR Version: R4 (4.0.1) and US Core 6.1 Profiles / USCDI v3                                                                                    
    • Supports SMART on FHIR v2 (standalone + EHR launch), OAuth 2.0, PKCE                                                
    • Supports Bulk Data Access ($export, system and group-level)                                                          
    • Endpoints:                                                                                                        
  • https://health-samurai.io/aidbox - Health Samurai's FHIR server as a service with free layer, register and create a new server in 1 click
    • Local development installation by Docker
    • Supports all resource types, all operations, json + xml + edn + transit + yaml, All FHIR versions
    • Based on fhirbase (https://www.health-samurai.io/fhirbase)
    • Supports SQL on FHIR
    • Implementation: PostgreSQL, JVM (clojure), Kubernetes
    • Oauth 2.0, OpenID Connect, SCIM
    • Access Policies
    • Custom Resources & First Class Extensions
    • Terminology Service
    • Extensible with Custom Operations by Aidbox SDK
  • AEGIS WildFHIR Enterprise Edition - FHIR Reference Test Server (Last Updated Sep 23, 2025)
    • R4 Official v4.0.1 - https://wildfhir4.wildfhir.org/fhir4-0-1
      • HTTPS/SSL supports TLS 1.3
      • Test client interface: https://wildfhir4.wildfhir.org/fhir4-0-1-gui
      • Supports the FHIR R4 Official (v4.0.1) version
      • Supports all resource types and standard operations, including json/xml patch, batch and transaction; search supports chained parameters, include and revinclude; support for conditional read/update/delete, create/update return preference and _summary parameter
    • STU3 Official v3.0.2 - https://wildfhir3.wildfhir.org/fhir3-0-2
      • HTTPS/SSL supports TLS 1.3
      • Test client interface: https://wildfhir3.wildfhir.org/fhir3-0-2-gui
      • Supports the FHIR STU3 Official (v3.0.2) version
      • Supports all resource types and standard operations, including json/xml patch, batch and transaction; search supports chained parameters, include and revinclude; support for conditional read/delete, create/update return preference and _summary parameter
  • AEGIS WildFHIR Community Edition - FHIR Reference Test Server (Last Updated Sep 23, 2025)
    • R4 Official v4.0.1 - https://wildfhir.wildfhir.org/r4
      • HTTPS/SSL supports TLS 1.2
      • Supports the FHIR R4 Official (v4.0.1) version
      • Supports all resource types and standard operations, including json/xml patch, batch and transaction; search supports chained parameters, include and revinclude; support for conditional read/update/delete, create/update return preference and _summary parameter
  • Telstra Health http://sqlonfhir-r4.azurewebsites.net/fhir - Telstra Health
    • Supports all resource types, but not all operations
    • .NET (C#) implementation on SQL Server Azure
    • great support for Questionnaires, and some SDC capabilities
  • http://health.gnusolidario.org:5000 GNU Health FHIR server
    • Supports read, validate and search for Patient, DiagnosticReport, Practitioner, Procedure, Observation, Condition, FamilyHistory
    • DSTU1
    • A Flask app. It's connected to the GNU Health community server database. Consequently, it's possible to create and update patients, doctors, etc. through the GNU Health frontend and the changes should be reflected on the FHIR server (indirect write support, I suppose).
    • I think our goal is to use the FHIR server as an adapter for non-GNU Health EHRs and users, since we already have synchronization between instances. But, there are other interesting possibilites, too.
    • I'm updating the code frequently and it's still in the dev stages (e.g., adding new resources frequently).
    • Documentation is here: https://en.wikibooks.org/w/index.php?title=GNU_Health/Using_the_FHIR_REST_server
  • https://r4.ontoserver.csiro.au/fhir - CSIRO's Ontoserver - R4 (FHIR 4.0.1)
    • Supports Terminology Services
    • CodeSystem, ValueSet, ConceptMap, NamingSystem, StructureDefinition, and Bundle with Read, Create, Update, Delete, Search, and Patch
    • $expand, $lookup, $validate-code, $closure, $find-matches, $translate, $preferred-id, $validate, and $batch
    • Specialised support for SNOMED CT, and LOINC
  • https://r5.ontoserver.csiro.au/fhir - CSIRO's Ontoserver - R5 (FHIR 5.0.0)
    • As for the R4 server
  • http://fhir.nestvision.com (NestVision, a Chinese medical IT company, for Chinese implementers)
    • NEST-FHIR: a free FHIR testing platform. Functionality starts with client conformance testing against a FHIR STU3 server, via any rest extensions on chrome browser, and will become a full functional testing platform later.
  • Kaji - https://kaji.healthforge.io
    • Supports STU3
    • General purpose server supporting all resources, most search parameters, xml & json
    • Tech stack: Scala, PostgreSQL, Kubernetes
  • Phast's Standard Terminology Services STS - https://jade.phast.fr/resources-server/api/FHIR/
    • Basic authentication: username = Connectathon   password = Connectathon_052020
    • FHIR R4
    • JSON and XML
    • Terminology server with terminologies SNOMED CT, LOINC, EDQM Standard Terms, all FHIR-defined code systems ...
    • Support ECL for SNOMED CT
    • Resources: CodeSystem, ValueSet, ConceptMap, NamingSystem, TerminologyCapabilities
    • interactions: read, vread, update, delete, create
    • common parameters: _tag, _profile, _security, _text, _content, _list, _format, _query, _filter
    • common search parameters: _lastUpdated, _has, _type, _id
    • common search result parameters: _sort, _count, _include, _revinclude
    • operations on CodeSystem (GET & POST): lookup, validate-code, subsumes
    • operations on ValueSet (GET & POST): expand, validate-code
    • operations on ConceptMap (GET & POST): translate, closure

  • NLM's HAPI FHIR servers (reset weekly):
  • Helios FHIR Server
  • Meld Sandbox






  • TIMS Biomed
    • Published by the TIMS group. Provides a unique set of ontologies/terminologies/vocabularies, with unique features such as text search and SSSOM-formatted mappings.
    • CodeSystems loaded: ICD10CM, RxNorm, SNOMED-CT, Mondo, HPO, CompLOINC, OMOP vocabularies
    • More information: https://www.timsbiomed.org/terminology-server/



  • atollee HealthFireKit™ (R4, R5, R6 ready) & FHIR-nativ Agnostic Terminology

    Key Benefits

    • Modular Plugin Architecture
      The world’s only modular, fully FHIR®-compliant toolkit with plugin architecture—your foundation for future-proof digital health projects. For example, interfaces, logic, processes, and agents can be added or removed via plugins—precisely to meet requirements and system resources.

    • Comprehensive Developer Tools & Monitoring
      From instant, lightweight prototyping to professional, custom, and auditable applications—not just ideal for development with AI co-pilots..

    • Next-generation Web Technology
      Built from the ground up against the FHIR® specification—lightweight, fast, and scalable; built edge-first in TypeScript.

    • Maintainable Architecture
      Event Sourcing, CQRS, and Domain-Driven Design—clear responsibilities and durable code.

    • Auditable Plug-ins & MCP-Ready
      Standardized interfaces for agents, apps, and logic—transparent, secure, and fully traceable.

    • Enterprise-Grade Security
      RBAC/ABAC, OAuth 2.0, plus plugins for Keycloak, Ory, and more.

    • much more

    🔗 Request your trial access: https://atollee.com/en/PlaygroundOpenAPI




  • No labels

4 Comments

  1. Francois Macary

    Sept 29, 2019

    Actually Sandy created a FHIR Test servers page for connectathon 22: Connectathon Test Servers 

    Shouldn't it replace this one?

    1. Ward Weistra

      Apr 09, 2021

      This also confused me, so I added links between the two.

  2. Mario Hyland

    Apr 30, 2024

    Each Public Test Server listed here should include a POC - Primary Point of Contact, and preferred method of contact - Email, Text, Zulip Channel, Github repo, etc.

    We also need input from the community, if these servers appear to no longer be available (or serviceable) - suggestion: Updates to this page are appreciated, and should be made on a regular basis.  POC should plan to review/update any information at least every six months (with a comment like [Updated April 30, 2024] as one of the data points.

  3. Ray Duncan

    Nov 16, 2024

    I took a look through this list because many of the healthcare IT companies in our accelerator are looking for an open sandbox that they can use without registering with a specific EMR vendor.

    Just looking through the list and trying most of the links, many of the sandboxes are not reachable ,or company web sites that had a sandbox still exist but without a sandbox.  Links that point to an endpoint without any documentation are not very useful either, as there is no way to know what test data is available. This list needs an overhaul. 

    There are several companies offering free FHIR servers for download on this list. That is also useful, but involves a lot more work than accessing an existing sandbox with preloaded data. Those could be broken out into a separate list.



Morty Proxy This is a proxified and sanitized view of the page, visit original site.