This wiki has undergone a migration to Confluence found Here

Difference between revisions of "Publicly Available FHIR Servers for testing"

From HL7Wiki
Jump to navigation Jump to search
Line 10: Line 10:
 
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.
 
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.  
+
* http://fhir1.healthintersections.com.au/ and http://fhir2.healthintersections.com.au/ - Grahame's test server
 +
** DSTU 1: http://fhir1.healthintersections.com.au/
 +
** DSTU 2: http://fhir2.healthintersections.com.au/
 
** Supports all resource types, all operations, xml + json  
 
** Supports all resource types, all operations, xml + json  
 
** implementation details: open source - see [[https://github.com/grahamegrieve/fhirserver]]
 
** implementation details: open source - see [[https://github.com/grahamegrieve/fhirserver]]
** also available using SSL at https://fhir.healthintersections.com.au/ (not operational right now)
+
** also available using SSL at https://fhir1.healthintersections.com.au/  
 
** see [[Health Intersections FHIR Server login documentation]] for OAuth
 
** 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 (pre-ballot version): 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.
 
* http://spark.furore.com - Ewout's test server (previously fhir.furore.com). The actual service endpoint is at http://spark.furore.com/fhir.

Revision as of 22:25, 3 November 2015

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://wildfhir.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://wildfhir.aegis.net/dstu2gui
  • 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://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://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