This wiki has undergone a migration to Confluence found Here
<meta name="googlebot" content="noindex">

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

From HL7Wiki
Jump to navigation Jump to search
Line 100: Line 100:
  
 
* AEGIS WildFHIR
 
* AEGIS WildFHIR
−
** R4 Ballot v3.2.0 - http://wildfhir.aegis.net/fhir3-2-0
+
** R4 Ballot 1 v3.3.0 - http://wildfhir.aegis.net/fhir3-3-0
 +
*** Test client interface: http://wildfhir.aegis.net/fhir3-3-0-gui
 +
*** Supports the FHIR R4 Ballot 1 (v3.3.0-13671) version for use at the upcoming Connectathon 18 event
 +
*** Supports all resource types and standard operations, including validate and json/xml patch, excluding transaction; search supports chained parameters, include and revinclude; support for conditional read/delete, create/update return preference and _summary parameter
 +
** R4 Candidate 1 v3.2.0 - http://wildfhir.aegis.net/fhir3-2-0
 
*** Test client interface: http://wildfhir.aegis.net/fhir3-2-0-gui
 
*** Test client interface: http://wildfhir.aegis.net/fhir3-2-0-gui
−
*** Supports the FHIR R4 Ballot (v3.2.0-12888) version used for the Connectathon 17 event
+
*** Supports the FHIR R4 Candidate 1 (v3.2.0-12888) version used for the Connectathon 17 event
 
*** Supports all resource types and standard operations, including validate and json/xml patch, excluding transaction; search supports chained parameters, include and revinclude; support for conditional read/delete, create/update return preference and _summary parameter
 
*** Supports all resource types and standard operations, including validate and json/xml patch, excluding transaction; search supports chained parameters, include and revinclude; support for conditional read/delete, create/update return preference and _summary parameter
 
** STU3 v3.0.1 (official) - http://wildfhir.aegis.net/fhir3-0-1
 
** STU3 v3.0.1 (official) - http://wildfhir.aegis.net/fhir3-0-1

Revision as of 15:14, 13 April 2018

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.fire.ly
    • 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.)
  • Pyro
    • https://pyrohealth.net/
    • Pyro Server’s FHIR STU3 endpoint: https://stu3.test.pyrohealth.net/fhir
    • Implementation: Generic STU V3.0.1 FHIR Server, all resource types, .NET (C#), MS SQL
    • Supports: All search parameters (except Composite Types), _includes, _revincludes, Search chaining, Conditional (Create, Update, Delete), History and Transaction bundles
  • AEGIS WildFHIR
    • R4 Ballot 1 v3.3.0 - http://wildfhir.aegis.net/fhir3-3-0
      • Test client interface: http://wildfhir.aegis.net/fhir3-3-0-gui
      • Supports the FHIR R4 Ballot 1 (v3.3.0-13671) version for use at the upcoming Connectathon 18 event
      • Supports all resource types and standard operations, including validate and json/xml patch, excluding transaction; search supports chained parameters, include and revinclude; support for conditional read/delete, create/update return preference and _summary parameter
    • R4 Candidate 1 v3.2.0 - http://wildfhir.aegis.net/fhir3-2-0
      • Test client interface: http://wildfhir.aegis.net/fhir3-2-0-gui
      • Supports the FHIR R4 Candidate 1 (v3.2.0-12888) version used for the Connectathon 17 event
      • Supports all resource types and standard operations, including validate and json/xml patch, excluding transaction; search supports chained parameters, include and revinclude; support for conditional read/delete, create/update return preference and _summary parameter
    • STU3 v3.0.1 (official) - http://wildfhir.aegis.net/fhir3-0-1
      • Test client interface: http://wildfhir.aegis.net/fhir3-0-1-gui
      • Supports the FHIR Release 3 (v3.0.1-11917) version used for the Connectathon 15, 16 and 17 events
      • 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
    • STU3 Candidate v1.8.0 - http://wildfhir.aegis.net/fhir1-8-0
      • Test client interface: http://wildfhir.aegis.net/fhir1-8-0-gui
      • Supports the FHIR STU3 Candidate (v1.8.0-10528) version used for the Connectathon 14 event
      • 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
    • STU3 Ballot v1.6.0 - http://wildfhir.aegis.net/fhir1-6-0
      • Test client interface: http://wildfhir.aegis.net/fhir1-6-0-gui
      • Supports the FHIR STU3 Ballot (v1.6.0-9810) version used for the Connectathon 13 event
      • 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
    • STU3 Ballot v1.4.0 - http://wildfhir.aegis.net/fhir1-4-0
      • Test client interface: http://wildfhir.aegis.net/fhir1-4-0-gui
      • Supports the FHIR STU3 Ballot (v1.4.0-8139) version used for the Connectathon 12 event
      • 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
    • STU3 Ballot v1.2.0 - http://wildfhir.aegis.net/fhir1-2-0
      • Test client interface: http://wildfhir.aegis.net/fhir1-2-0-gui
      • Supports the FHIR STU3 Ballot (v1.2.0-7493) version used for the Connectathon 11 event
      • 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
    • DSTU2 v1.0.2 (official) - http://wildfhir.aegis.net/fhir1-0-2
      • Test client interface: http://wildfhir.aegis.net/fhir1-0-2-gui
      • Supports the FHIR DSTU 2.0 (v1.0.2-7202) version used for the Connectathon 10 event
      • Supports all resource types and operations, including validate, excluding transaction; support for conditional read, create/update return preference
  • 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.
Retrieved from "https://wiki.hl7.org/w/index.php?title=Publicly_Available_FHIR_Servers_for_testing&oldid=155924"