Publicly Available FHIR Servers for testing

Back to FHIR home page

Introduction

This page lists FHIR servers that are publically available for testing. In order to avoid spam etc, the servers are generally password protected. A contact is provided to get a password.

List

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.

• http://fhir.healthintersections.com.au/ - Grahame's test server.
  • Supports all resource types, all operations, xml + json
  • implementation details: open source - see [[1]]
  • also available using SSL at https://fhir.healthintersections.com.au/ (not operational right now)
  • see Health Intersections FHIR Server login documentation for OAuth
  • DSTU 1: http://fhir.healthintersections.com.au
  • DSTU 2: http://fhir-dev.healthintersections.com.au
  • DSTU 2 (more up-to-date) http://argonaut.healthintersections.com.au

• http://spark.furore.com - Ewout's test server (previously fhir.furore.com). The actual service endpoint is at http://spark.furore.com/fhir.
  • Supports all resource types, all operations, xml + json
  • implementation details: C# reference implementation, WebApi 2.0 library, Mongo DB for storage and search.
  • Server is running on AppHarbor, Mongo at MongoLab, and storage of binary is done on Amazon S3
  • Available in the open source - see [[2]]
  • DSTU 1: http://spark.furore.com/fhir
  • DSTU 2: http://spark-dstu2.furore.com/fhir

• http://nprogram.azurewebsites.net/ - Rik Smithies/NProgram test server
  • patient and organisation resources, read only (C#)
• http://fhir.oridashi.com.au - Brett Esler/Oridashi demo servers overview
  • read-only implementation, .NET 2.0, C#, self-host web server, SQL Server DB - legacy CIS
  • DSTU1: 'Best Practice CIS' http://demo.oridashi.com.au:8190
  • DSTU2: 'Best Practice CIS' http://demo.oridashi.com.au:8290 and http://bp.oridashi.com.au
  • DSTU1: 'Medical Director CIS' http://demo.oridashi.com.au:8191
  • DSTU2: 'Medical Director CIS' http://demo.oridashi.com.au:8291 and http://md.oridashi.com.au
  • DSTU1: 'Zedmed CIS' http://demo.oridashi.com.au:8192/
  • DSTU2: 'Zedmed CIS' http://demo.oridashi.com.au:8292/ and http://zm.oridashi.com.au
• https://fhir.smartplatforms.org - Josh Mandel / SMART Platforms
  • Open-source server in Grails (Java/Groovy) + MongoDB
  • "SMART on FHIR" Server: https://fhir-api.smartplatforms.org | https://fhir-open-api.smartplatforms.org | Source
  • "FHIR Starter" App Launcher https://fhir.smartplatforms.org | Source
• http://worden.globalgold.co.uk:8080/FHIR_a/hosted_demo.html Robert Worden / Open Mapping Software
  • Patient resource, read-only
  • Illustrates building a FHIR server on any existing application, any resource, by mapping to the application database
  • Tools to do this now available free, evolving
• http://fhirplace.health-samurai.io/
  • Supports all resource types, all operations, xml + json
  • Based on fhirbase (https://github.com/fhirbase/fhirbase)
  • Implementation: postgresql, clojure/FHIR-Java (https://github.com/fhirbase/fhirplace)

• http://fhirtest.uhn.ca/ - HAPI / University Health Network test server
  • Supports all resource types and operations
  • Has query builder UI which can be used to facilitate testing
  • Endpoints:
    • DSTU1: http://fhirtest.uhn.ca/baseDstu1
    • DSTU2: http://fhirtest.uhn.ca/baseDstu2

• http://fhir.cerner.com - Cerner's Sandbox
  • See our developer / API documentation for the exact resource that this server support at http://fhir.cerner.com
  • Supports both open and OAuth 2 access
  • Contact us on our Google group for any issues or access to the OAuth 2 protected endpoints
  • Endpoints (open, does not require OAuth 2):
    • DSTU2 (May 2015 Ballot): https://fhir.sandboxcernerpowerchart.com/may2015/open/d075cf8b-3261-481d-97e5-ba6c48d3b41f

• http://open.epic.com/Interface/FHIR - Epic's Sandbox
  • Supports a subset of resource types, read-only
  • Runs against a functional Epic database
  • Includes online test harness for quick syntax checking
  • Contact open@epic.com for more information

• http://wildfire.aegis.net/dstu2 - AEGIS WildFHIR - DSTU 2.0 (2015Sep)
  • Recently updated to support the DSTU 2.0 (2015Sep) current QA version of FHIR
    • NOTE: Update to DSTU 2.0 (2015Sep) required a reset/removal of all existing resource data
  • Supports all resource types and operations (except transaction); better support for search; support for conditional read, create/update return preference
  • Based on the FHIR DSTU 2.0 (2015Sep) Java reference implementation; hosted on RedHat WildFly 8.1.0
  • Test client interface: http://wildfire.aegis.net/dstu2gui

• http://wildfire.aegis.net/fhir - AEGIS WildFHIR - DSTU 1.1
  • Supports all resource types and operations (except transaction); limited support for search
  • Based on FHIR DSTU 1.1 Java reference implementation; hosted on RedHat WildFly 8.1.0
  • Test client interface: http://wildfire.aegis.net/fhirgui

• http://sqlonfhir.azurewebsites.net/fhir - HealthConnex - DSTU2 (2015May)
  • DSTU-2 (2015May) May ballot version of FHIR
  • Supports all resource types, but not all operations
  • .NET (C#) implementation on SQL Server Azure
  • No support for Tags/search chaining or profiles at present
• http://sqlonfhir-dstu2.azurewebsites.net/fhir - HealthConnex - DSTU2
  • DSTU-2 (2015Sep) version of FHIR
  • Supports all resource types, but not all operations
  • .NET (C#) implementation on SQL Server Azure
  • No support for search chaining or profiles at present

• 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

• http://ontoserver.csiro.au/fhir - CSIRO's Ontoserver - DSTU2 (2015Sep)
  • Supports Terminology Services
  • ValueSet, ConceptMap read, create, update, minimal search
  • $expand, $validate-code, and $translate