Publicly Available FHIR Servers for testing

Back to FHIR home page

Introduction

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

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

• [Base: What is in the specification]
• [Smart on FHIR test data]

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.

• http://fhir2.healthintersections.com.au/ and http://fhir3.healthintersections.com.au/ - Grahame's test server
  • DSTU 2: http://fhir2.healthintersections.com.au/
  • Current Build: http://fhir3.healthintersections.com.au/
  • Supports all resource types, all operations, xml + json
  • implementation details: open source - see [[1]]
  • supports Smart on FHIR

• HSPC Sandbox
  • http://sandbox.hspconsortium.org
  • Free DSTU2 and STU3 open sandboxes with tools for managing data. Both personal and team sandboxes available.
  • Supports both open and SMART on FHIR OAuth2 access
  • Supports app registration for SMART on FHIR apps
  • Supports all resource types, all operations
  • http://hspconsortium.org/#/
  • https://healthservices.atlassian.net/wiki/display/HSPC/Healthcare+Services+Platform+Consortium

• http://spark.furore.com - Furore's test server.
  • C# reference implementation, WebApi 2.0 library, Mongo DB for storage and search.
  • The service endpoint is at http://spark.furore.com/fhir.
  • DSTU 2
  • Supports all resource types, all operations, xml + json
  • Open source: [[2]]

• http://nprogram.azurewebsites.net/ - Rik Smithies/NProgram test server (DSTU 2)
  • patient, organisation, diagnostic report, value set resources, read only, xml + json (C#)
  • DSTU 1 here http://fhir-dstu1-nprogram.azurewebsites.net/

• http://fhir.oridashi.com.au - Brett Esler/Oridashi demo servers overview
  • read-only implementation, .NET 4.0, C#, self-host web server, SQL Server DB - legacy CIS
  • DSTU2: 'Best Practice CIS' http://demo.oridashi.com.au:8290
  • DSTU2: 'Medical Director CIS' http://demo.oridashi.com.au:8291
  • STU3: 'Best Practice CIS' http://demo.oridashi.com.au:8297
  • STU3: 'Medical Director CIS' http://demo.oridashi.com.au:8298

• 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
• https://aidbox.io/ - Health Samurai's FHIR server as a service with free layer, register and create a new server in 1 click
  • Supports all resource types, all operations, json, DSTU2
  • Based on fhirbase (https://github.com/fhirbase/fhirbase-plv8)
  • Implementation: postgresql, clojure

• 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
    • DSTU3: http://fhirtest.uhn.ca/baseDstu3

• 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
      • Open - https://fhir-open.sandboxcernerpowerchart.com/dstu2/d075cf8b-3261-481d-97e5-ba6c48d3b41f
      • With OAuth 2 - https://fhir.sandboxcernerpowerchart.com/dstu2/d075cf8b-3261-481d-97e5-ba6c48d3b41f
    • DSTU2 (May 2015 Ballot) - https://fhir-open.sandboxcernerpowerchart.com/may2015/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://wildfhir.aegis.net/fhir3-0-0 - AEGIS WildFHIR - STU 3 (v3.0.0-11684)
  • Supports the FHIR STU 3 (v3.0.0-11684) official version (QA freeze taken on 03/16/2017)
  • 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
  • Based on the FHIR STU 3 (v3.0.0-11684) Java reference implementation; hosted on RedHat WildFly 8.1.0
  • Also available using SSL at https://wildfhir.aegis.net/fhir3-0-0
  • Test client interface: http://wildfhir.aegis.net/fhir3-0-0-gui

• http://wildfhir.aegis.net/fhir1-8-0 - AEGIS WildFHIR - STU 3 Candidate (v1.8.0-10528)
  • Supports the STU 3 Candidate (v1.8.0-10528) current version of FHIR for the January 2017 Connectathon 14 event in San Antonio, TX
  • Supports all resource types and standard operations, including validate and json/xml patch, excluding transaction; improved support for search including chained parameters; support for conditional read/delete, create/update return preference and _summary parameter
  • Based on the FHIR STU 3 Candidate (v1.8.0-10528) Java reference implementation; hosted on RedHat WildFly 8.1.0
  • Also available using SSL at https://wildfhir.aegis.net/fhir1-8-0
  • Test client interface: http://wildfhir.aegis.net/fhir1-8-0-gui

• http://wildfhir.aegis.net/fhir1-6-0 - AEGIS WildFHIR - STU 3 Ballot (v1.6.0-9810)
  • Supports the STU 3 Ballot (v1.6.0-9810) current version of FHIR for the September 2016 Connectathon 13 event in Baltimore, MD
  • Supports all resource types and standard operations, including validate and json/xml patch(experimental), excluding transaction; improved support for search including chained parameters; support for conditional read/delete, create/update return preference
  • Based on the FHIR STU 3 Ballot (v1.6.0-9810) Java reference implementation; hosted on RedHat WildFly 8.1.0
  • Also available using SSL at https://wildfhir.aegis.net/fhir1-6-0
  • Test client interface: http://wildfhir.aegis.net/fhir1-6-0-gui

• http://wildfhir.aegis.net/fhir1-4-0 - AEGIS WildFHIR - STU 3 Candidate (v1.4.0-8139)
  • Supports the STU 3 Candidate (v1.4.0-8139) current version of FHIR for the May 2016 Connectathon 12 event in Montreal, QC, Canada
  • Supports all resource types and standard operations, including validate and json patch(experimental), excluding transaction; better support for search; support for conditional read, create/update return preference
  • Based on the FHIR STU 3 Candidate (v1.4.0-8139) Java reference implementation; hosted on RedHat WildFly 8.1.0
  • Also available using SSL at https://wildfhir.aegis.net/fhir1-4-0
  • Test client interface: http://wildfhir.aegis.net/fhir1-4-0-gui

• http://wildfhir.aegis.net/fhir1-2-0 - AEGIS WildFHIR - DSTU 2.1 (v1.2.0-7493)
  • Supports the DSTU 2.1 (v1.2.0-7493) current version of FHIR for the January 2016 Connectathon 11 event in Orlando, FL
  • Supports all resource types and standard operations, including validate and patch(experimental), excluding transaction; better support for search; support for conditional read, create/update return preference
  • Based on the FHIR DSTU2 (v1.2.0-7493) Java reference implementation; hosted on RedHat WildFly 8.1.0
  • Also available using SSL at https://wildfhir.aegis.net/fhir1-2-0
  • Test client interface: http://wildfhir.aegis.net/fhir1-2-0-gui

• http://wildfhir.aegis.net/fhir1-0-2 - AEGIS WildFHIR - DSTU 2.0 (v1.0.2-7202)
  • Supports the DSTU 2.0 (v1.0.2-7202) version of FHIR
  • Supports all resource types and operations, including validate, excluding transaction; support for conditional read, create/update return preference
  • Based on the FHIR DSTU 2.0 (v1.0.2-7202) Java reference implementation; hosted on RedHat WildFly 8.1.0
  • Also available using SSL at https://wildfhir.aegis.net/fhir1-0-2
  • Test client interface: http://wildfhir.aegis.net/fhir1-0-2-gui

• [DECOMMISSIONED] - AEGIS WildFHIR - DSTU 1.1

• http://sqlonfhir-dstu2.azurewebsites.net/fhir - HealthConnex - DSTU2
  • 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://sqlonfhir-stu3.azurewebsites.net/fhir - Telstra Health (HealthConnex) - Jan 2017 San Antonio Connectathon Build
  • Supports all resource types, but not all operations
  • .NET (C#) implementation on SQL Server Azure
  • Limited support for search chaining or profiles at present (and terminology is really broken)

• 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/stu3 - CSIRO's Ontoserver - DSTU2_1 (2016May)
• http://ontoserver.csiro.au/baltimore - CSIRO's Ontoserver - STU3 (FHIR 1.8.0, tracking latest HAPI dstu3 structures)
  • Supports Terminology Services
  • CodeSystem, ValueSet, ConceptMap read, create, update, delete, search
  • $expand, $validate-code, $validate, $closure, $translate, and $batch
  • Specialised support for SNOMED CT, and LOINC

• http://fhir.i2b2.org/open/ i2b2 FHIR server - DSTU21
  • Supports read and search for Patient, Observation, Condition, Medication
  • DSTU21
  • demo calls see: http://fhir.i2b2.org
  • Connected to demo server at https://www.i2b2.org/webclient/

• https://tw171.open.allscripts.com/FHIR - Allscripts Touchworks Sandbox (OAuth)
  • DSTU 2.0 (v1.0.2) version of FHIR
  • Supports the resource types required for the Common Clinical Data Set, currently read-only
  • Supports OAuth validation
  • Supports SMART on FHIR
  • Runs against Allscripts Touchworks 17.1 test server
  • Please review our developer / API documentation at https://developer.allscripts.com/Content/fhir/content/TWFHIR17_Sandbox/
  • Contact Jeffrey Danford for more information about this endpoint
  • Contact Gunther Meyerfor OAuth setup

• https://pro171.open.allscripts.com/FHIR - Allscripts Professional Sandbox (OAuth)
  • DSTU 2.0 (v1.0.2) version of FHIR
  • Supports the resource types required for the Common Clinical Data Set, currently read-only
  • Supports OAuth validation
  • Supports SMART on FHIR
  • Runs against Allscripts Professional 17.1 test server
  • Please review our developer / API documentation at https://developer.allscripts.com/content/fhir/content/Pro171_Sandbox/
  • Contact Jeffrey Danford for more information about this endpoint
  • Contact Gunther Meyerfor OAuth setup

• https://scm163cu3.open.allscripts.com/FHIR - Allscripts Sunrise Sandbox (OAuth)
  • DSTU 2.0 (v1.0.2) version of FHIR
  • Supports the resource types required for the Common Clinical Data Set, currently read-only
  • Supports OAuth validation
  • Supports SMART on FHIR
  • Runs against Allscripts Sunrise 16.3 CU3 test server
  • Please review our developer / API documentation at https://developer.allscripts.com/Content/fhir/content/SCM163CU3_Sandbox/
  • Contact Jeffrey Danford for more information about this endpoint
  • Contact Gunther Meyerfor OAuth setup

• http://twdev.open.allscripts.com/FHIR - Allscripts STU3 Sandbox (OAuth)
  • STU 3.0 (v1.8.0) version of FHIR
  • Supports the resource types required for the Common Clinical Data Set, currently read-only
  • Supports OAuth validation
  • Supports SMART on FHIR
  • Runs against Allscripts Touchworks 17.1 test server
  • Please review our developer / API documentation at https://developer.allscripts.com/fhir
  • Contact Jeffrey Danford for more information about this endpoint
  • Contact Gunther Meyerfor OAuth setup

• http://52.72.172.54:8080/fhir/home - Michigan Health Information Network (open)
  • 1000s of realistic test patient records

• https://fhir.careevolution.com/Master.Adapter1.WebClient/fhir - CareEvolution HIEBus
  • DSTU 2, mostly read-only implementation, support read-write for some resources
  • Open end-point: https://fhir.careevolution.com/apitest/fhir
  • Protected (SMART-on-FHIR) end-point: https://fhir.careevolution.com/Master.Adapter1.WebClient/api/fhir
  • Supports backend services authorization:
    • Token end point: https://fhir.careevolution.com/Master.Adapter1.WebClient/identityserver/connect/token
    • client ID: JWTClientCredentials
    • issuer: JWTClientCredentials
    • audience: https://fhir.careevolution.com/Master.Adapter1.WebClient/identityserver/connect/token
    • scope: system/*.read
    • signing certificate: https://fhir.careevolution.com/jwt.pfx with password jwt.careevolution.com
  • Contact CareEvolution if you need a login to access the protected end-point (...or for any additional information or question)

• 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.