Publicly Available FHIR Servers for testing

From HL7Wiki
Revision as of 07:01, 17 October 2017 by Jwalonoski (Talk | contribs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

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):

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.

  • Vonk
    • http://vonk.furore.com
    • Supports STU3
    • Generic FHIR Server, for all types of resources, all search parameters, xml + json
    • Supports validation (for example: POST /Patient/$validate, with a Patient resource in the body).
    • This test instance runs on MongoDB and therefore can do batch but not transaction. (Transactions are supported on SQL Server.)
  • 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]]
  • [UPDATED] http://wildfhir.aegis.net/fhir3-0-1 - AEGIS WildFHIR - FHIR Release 3 (STU; v3.0.1-11917)
    • Supports the FHIR Release 3 (STU; v3.0.1-11917) official 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
    • Based on the FHIR Release 3 (STU; v3.0.1-11917) Java reference implementation; hosted on RedHat WildFly 8.1.0
    • Also available using SSL at https://wildfhir.aegis.net/fhir3-0-1
    • Test client interface: http://wildfhir.aegis.net/fhir3-0-1-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
  • [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-latest - CSIRO's Ontoserver - STU3 (FHIR 3.0.1)
  • http://ontoserver.csiro.au/dstu2_1 - CSIRO's Ontoserver - DSTU2_1 (2016May)
    • Supports Terminology Services
    • CodeSystem, ValueSet, ConceptMap read, create, update, delete, search
    • $expand, $lookup, $validate-code, $validate, $closure, $translate, and $batch
    • Specialised support for SNOMED CT, and LOINC
  • 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.

Copyright © Health Level Seven International ® ALL RIGHTS RESERVED. The reproduction of this material in any form is strictly forbidden without the written permission of the publisher.