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.


The status of publicly available FHIR servers is monitored using UptimeRobot at If you would like a publicly available FHIR server added to the UptimeRobot status page, email [Sean McIlvenna[1]].


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.

  • - 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 (
    • 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 - FHIR Reference Server
    • R4 Official v4.0.1 -
      • Test client interface:
      • Supports the FHIR R4 Official (v4.0.1) version
      • Supports all resource types and standard operations, including batch, validate and json/xml patch, excluding 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 -
      • Test client interface:
      • Supports the FHIR STU3 Official (v3.0.2) version
      • Supports all resource types and standard operations, including validate and json/xml patch, excluding transaction; search supports chained parameters; support for conditional read/delete, create/update return preference and _summary parameter
    • DSTU2 Official v1.0.2 -
      • Test client interface:
      • Supports the FHIR DSTU2 Official (v1.0.2) version
      • Supports all resource types and operations, including validate, excluding transaction; support for conditional read, create/update return preference
  • Telstra Health - 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
  • 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:
  • - CSIRO's Ontoserver - STU3 (FHIR 3.0.1)
  • - 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
  • - CSIRO's Ontoserver - R5 (FHIR 5.0.0)
    • As for the R4 server
  • (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 -
    • Supports STU3
    • General purpose server supporting all resources, most search parameters, xml & json
    • Tech stack: Scala, PostgreSQL, Kubernetes
  • Phast's Standard Terminology Services STS -
    • 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

  • No labels


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

    Shouldn't it replace this one?

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