Public Test Servers - FHIR - Confluence

Public Test Servers - FHIR - Confluence
FHIR
Page tree
Browse pages
tachments (0)
Page History
Highlight Page Terms
Export Glossary terms
Page Information
Resolved comments
View in Hierarchy
View Source
Export to Word
Hide Inline Comments
Jira links
Public Test Servers
Created by
Lloyd McKenzie
, last updated by
TeamMock
on
Apr 14, 2026
10 minute read
Introduction
This page lists FHIR servers that are publicly available for testing. These are public services provided by volunteers and HL7 makes no representations concerning their safety or reliability.
In order to avoid spam etc., the servers are generally password protected. A contact is provided to get a password.
BTW: List of publicly available test data (some of these test servers preload some of this data):
Base: What is in the specification
Smart on FHIR test data
For servers specifically for Connectathons see
Connectathon Test Servers
Status
The status of publicly available FHIR servers is monitored using UptimeRobot at
. If you would like a publicly available FHIR server added to the UptimeRobot status page, email [Sean McIlvenna
[1]
].
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.
and
- Grahame's test server
Supports all resource types, all operations, xml + json
implementation details: open source - see [
[2]
supports Smart on FHIR
HSPC Sandbox
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
Firely Server
(formerly Vonk) - .NET based FHIR Server by
Firely
Demo servers
Stable
STU3
R4
R5
Read this blogpost to learn about different ways to interact with the test server:
SMART on FHIR + Bulk Data Export
See
on how to interact with the authorization server.
Functionality
Generic FHIR Server, for all types of resources, all search parameters, transactions, xml + json
Supports validation (for example: POST /Patient/$validate, with a Patient resource in the body) and many plugins.
Download your own instance and more information
Documentation
For more information, contact
server@fire.ly
mock.health
— Hosted Synthea-based synthetic FHIR R4 sandbox
Hosted sandbox of synthetic patient data generated with Synthea, enriched with a Markov progression module trained on real de-identified patient                                           journeys for clinical diversity (multi-condition, realistic comorbidities).  Includes DICOM imaging, diagnostic reports, and clinical notes alongside standard resources.
FHIR Version: R4 (4.0.1) and US Core 6.1 Profiles / USCDI v3
Supports SMART on FHIR v2 (standalone + EHR launch), OAuth 2.0, PKCE
Supports Bulk Data Access ($export, system and group-level)
Endpoints:
FHIR R4 base:
SMART configuration:
Documentation:
Self-service free tier available; contact
hello@mock.health
for support
Kodjin FHIR Server
FHIR Server for high performance with Terminology Server capabilities
Demo public endpoint (R4):
Playground console:
Documentation:
Kodjin's Functionality:
Supports all resource types and standard operations, including batch & transactions, validate and json/xml patch, search supports include and revinclude; support for conditional read/update/delete, create/update return preference and _summary parameter
Kodjin supports all standard FHIR and custom profiles & IGs (US Core, Carin4BB, etc.)
Supports profiles validations
Supports SMART on FHIR |  Bulk Export | Bulk Import operations
Provides FHIRpath validator with operation $
apply-fhirpath
HAPI FHIR Reference Server
Supports all resources and many FHIR features including Subscriptions, Terminology Services, etc.
Fully open source (Apache 2.0 License)
Project information:
Endpoints:
Web UI:
DSTU2 Endpoint:
STU3 Endpoint:
R4 Endpoint:
R5 Endpoint:
Bulk Data Reference Server
Supports
FHIR Bulk Data Access Implementation Guide
Fully open source (
Apache 2.0 License
Project information:
R4 Endpoint:
Spark FHIR Reference Server
- Open source test server originally developed by
Firely
, now maintained by
Incendi
Supports all resource types, searches, many operations, xml + json
Supports STU3, and R4
Fully open source (BSD-3 License)
Project information:
Endpoints:
R4 endpoint:
STU3 endpoint:
- Rik Smithies/NProgram test server (R5)
patient, organization, diagnostic report, medication definition resources, value set resources, read only, xml + json (C#)
DSTU 2 here
- Brett Esler/Oridashi demo servers overview
read-only implementation, C#, self-host web server, SQL Server DB - Facade on CIS
R4: 'Best Practice CIS'
R4: 'Medical Director CIS'
STU3: 'Best Practice CIS'
STU3: 'Medical Director CIS'
DSTU2: 'Best Practice CIS'
DSTU2: 'Medical Director CIS'
Open-source app launcher + HAPI-based FHIR server
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
- Health Samurai's FHIR server as a service with free layer, register and create a new server in 1 click
Local development installation by Docker
Supports all resource types, all operations, json + xml + edn + transit + yaml, All FHIR versions
Based on fhirbase (
Supports SQL on FHIR
Implementation: PostgreSQL, JVM (clojure), Kubernetes
Oauth 2.0, OpenID Connect, SCIM
Access Policies
Custom Resources & First Class Extensions
Terminology Service
Extensible with Custom Operations by Aidbox SDK
Cerner's Sandbox
See our developer / API documentation for the resources that this server supports at
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 (DSTU2):
Open -
With OAuth 2 Provider access -
With OAuth 2 Patient access -
Endpoints (R4):
Open -
With OAuth 2 Provider access -
With OAuth 2 Patient access -
- 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
AEGIS
WildFHIR Enterprise Edition - FHIR Reference Test Server (
R4 Official v4.0.1 -
HTTPS/SSL supports TLS 1.3
Test client interface:
Supports the FHIR R4 Official (v4.0.1) version
Supports all resource types and standard operations, including json/xml patch, batch and transaction; search supports chained parameters, include and revinclude; support for conditional read/update/delete, create/update return preference and _summary parameter
STU3 Official v3.0.2 -
HTTPS/SSL supports TLS 1.3
Test client interface:
Supports the FHIR STU3 Official (v3.0.2) version
Supports all resource types and standard operations, including json/xml patch, batch and transaction; search supports chained parameters, include and revinclude; support for conditional read/delete, create/update return preference and _summary parameter
AEGIS
WildFHIR Community Edition - FHIR Reference Test Server (
R4 Official v4.0.1 -
HTTPS/SSL supports TLS 1.2
Supports the FHIR R4 Official (v4.0.1) version
Supports all resource types and standard operations, including json/xml patch, batch and transaction; search supports chained parameters, include and revinclude; support for conditional read/update/delete, create/update return preference and _summary parameter
Telstra Health
- Telstra Health
Supports all resource types, but not all operations
.NET (C#) implementation on SQL Server Azure
great support for Questionnaires, and some SDC capabilities
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:
- CSIRO's Ontoserver - R4 (FHIR 4.0.1)
Supports Terminology Services
CodeSystem, ValueSet, ConceptMap, NamingSystem, StructureDefinition, and Bundle with Read, Create, Update, Delete, Search, and Patch
$expand, $lookup, $validate-code, $closure, $find-matches, $translate, $preferred-id, $validate, and $batch
Specialised support for SNOMED CT, and LOINC
- CSIRO's Ontoserver - R5 (FHIR 5.0.0)
As for the R4 server
i2b2 FHIR server - DSTU21
Supports read and search for Patient, Observation, Condition, Medication
DSTU21
demo calls see:
Connected to demo server at
- 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
Contact
Jeffrey Danford
for more information about this endpoint
Contact
Gunther Meyer
for OAuth setup
- 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
Contact
Jeffrey Danford
for more information about this endpoint
Contact
Gunther Meyer
for OAuth setup
- 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
Contact
Jeffrey Danford
for more information about this endpoint
Contact
Gunther Meyer
for OAuth setup
- 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
Contact
Jeffrey Danford
for more information about this endpoint
Contact
Gunther Meyer
for OAuth setup
- Michigan Health Information Network (open)
1000s of realistic test patient records
- CareEvolution HIEBus
DSTU2, read-write for most resources
STU3, read-write for most resources
R4, read-write for most resources
Open DSTU2 end-point:
Protected (SMART-on-FHIR) DSTU2 end-point:
Protected (SMART-on-FHIR) STU3 end-point:
Protected (SMART-on-FHIR) R4 end-point:
Supports
backend services authorization
- see
for details.
All three end points support
bulk data export
Contact
CareEvolution
if you need a login to access the protected end-point (...or for any additional information or question)
(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.
The SMART Genomics API -
FHIR STU3 v1.8
JSON and XML
The SMART Genomics API is built on top of SMART on FHIR
Open Source
Documentation:
Kaji -
Supports STU3
General purpose server supporting all resources, most search parameters, xml & json
Tech stack: Scala, PostgreSQL, Kubernetes
JPA HL7 FHIR Server -
Promotes HL7 FHIR development in Vietnam
Phast's Standard Terminology Services STS -
Basic authentication:
username
Connectathon
password
Connectathon_052020
FHIR R4
JSON and XML
Terminology server with terminologies SNOMED CT, LOINC, EDQM Standard Terms, all FHIR-defined code systems ...
Support ECL for SNOMED CT
Resources: CodeSystem, ValueSet, ConceptMap, NamingSystem, TerminologyCapabilities
interactions: read, vread, update, delete, create
common parameters: _tag, _profile, _security, _text, _content, _list, _format, _query, _filter
common search parameters: _lastUpdated, _has, _type, _id
common search result parameters: _sort, _count, _include, _revinclude
operations on CodeSystem (GET & POST): lookup, validate-code, subsumes
operations on ValueSet (GET & POST): expand, validate-code
operations on ConceptMap (GET & POST): translate, closure
NLM's HAPI FHIR servers (reset weekly):
4.7 million Observations from 2048 patients (deidentified); tag: “ri-10k”
Also has generated data and sample resources from FHIR
Helios FHIR Server
Open-source FHIR server built in Rust -
open sandbox:
- Test data is reset at 3:00 AM US Eastern every Sunday
Supports FHIR R4, R4B, R5, and will support R6 - multi-version access via the
FHIR version parameter
(e.g. fhirVersion=4.0 in the Accept header)
Full CRUD for all FHIR resource types; JSON and XML; search with chained parameters, history, versioning, batch/transaction
SQLite, PostgreSQL, Elasticsearch, and S3 - configurable for development through production analytics workloads
Includes a
FHIRPath expression engine
(CLI + HTTP server),
SQL-on-FHIR ViewDefinition processing
(CLI + HTTP server), and Python bindings (
pysof
) for analytics pipelines
SQL-on-FHIR output formats: CSV, JSON, NDJSON, Parquet; cloud storage support (S3, GCS, Azure Blob)
Helios Software
Meld Sandbox
Supports DSTU2, STU3, R4 and will support R5 in the future
Sandboxes can be created, and shared with other users
It supports SMART on FHIR applications and registration
It supports both open and closed endpoints using Oauth 2.0
Edifecs FHIR Server
Supports R4
Supports SMART on FHIR flow
Supports OAuth 2.0
Details and first steps: contact
artem.sopin@edifecs.com
to get the document
Optum:
Public Directories (Open):
UPMC (FHIR R4 Server)
(sign-up and information)
Athenahealth
Onboarding Instructions with public sandbox
List of supported FHIR APIs
Support for DSTU2 and R4
Support for SMART on FHIR (standalone and EHR launch)
KeFHIR (Kodality FHIR server)
Sandbox:
Wiki with documentation:
Open-source
May be used as
generic FHIR Server for
all types of resources
, all search parameters, xml + json
library inside your app
or as intermediary server (beta)
Supports R4; will support R5 in the future; STU1, DSTU2 and STU3 archieved
Supports validation, Oauth 2.0 and many plugins.
TIMS Biomed
Published by the
TIMS group
. Provides a unique set of ontologies/terminologies/vocabularies, with unique features such as text search and
SSSOM
-formatted mappings.
CodeSystems loaded: ICD10CM, RxNorm, SNOMED-CT, Mondo, HPO, CompLOINC, OMOP vocabularies
More information:
Whitefox AU Core FHIR Test Server
FHIR Version: R4
Profile:
AU Core v1.0.0-ballot
Preloaded Dataset (Sparked Test Data):
AU FHIR Test Data
FHIR Server Source code (Based on HAPI):
Whitefox AU Core FHIR Test Server
Articles:
From Concept To Implementation
Testing FHIR AU Implementations With Inferno A Comprehensive Guide
Endpoints:
Web UI:
FHIR Base URL:
Contact Us:
Whitefox Cloud Consulting
atollee HealthFireKit
™ (R4, R5, R6 ready) & FHIR-nativ Agnostic Terminology
Key Benefits
Modular Plugin Architecture
The world’s only modular, fully FHIR®-compliant toolkit with plugin architecture—your foundation for future-proof digital health projects. For example, interfaces, logic, processes, and agents can be added or removed via plugins—precisely to meet requirements and system resources.
Comprehensive Developer Tools &
Monitoring
From instant, lightweight prototyping to professional, custom, and auditable applications—not just ideal for development with AI co-pilots..
Next-generation Web Technology
Built from the ground up against the FHIR® specification—lightweight, fast, and scalable; built edge-first in TypeScript.
Maintainable Architecture
Event Sourcing, CQRS, and Domain-Driven Design—clear responsibilities and durable code.
Auditable Plug-ins & MCP-Ready
Standardized interfaces for agents, apps, and logic—transparent, secure, and fully traceable.
Enterprise-Grade Security
RBAC/ABAC, OAuth 2.0, plus plugins for Keycloak, Ory, and more.
much more
🔗 Request your trial access:
No labels
4 Comments
Francois Macary
Sep 29, 2019
Actually Sandy created a FHIR Test servers page for connectathon 22:
Connectathon Test Servers
Shouldn't it replace this one?
Ward Weistra
Apr 09, 2021
This also confused me, so I added links between the two.
Mario Hyland
Apr 30, 2024
Each Public Test Server listed here should include a POC - Primary Point of Contact, and preferred method of contact - Email, Text, Zulip Channel, Github repo, etc.
We also need input from the community, if these servers appear to no longer be available (or serviceable) - suggestion: Updates to this page are appreciated, and should be made on a regular basis.  POC should plan to review/update any information at least every six months (with a comment like [Updated April 30, 2024] as one of the data points.
Ray Duncan
Nov 16, 2024
I took a look through this list because many of the healthcare IT companies in our accelerator are looking for an open sandbox that they can use without registering with a specific EMR vendor.
Just looking through the list and trying most of the links, many of the sandboxes are not reachable ,or company web sites that had a sandbox still exist but without a sandbox.  Links that point to an endpoint without any documentation are not very useful either, as there is no way to know what test data is available. This list needs an overhaul.
There are several companies offering free FHIR servers for download on this list. That is also useful, but involves a lot more work than accessing an existing sandbox with preloaded data. Those could be broken out into a separate list.
Overview
Content Tools
Apps
Atlassian Confluence Community License
granted to Health Level Seven International.
Evaluate Confluence today
Atlassian Confluence
9.2.4
(Cluster node: d7c78643)
Printed by Atlassian Confluence 9.2.4
Report a bug
Atlassian News
Atlassian
{"serverDuration": 152, "requestCorrelationId": "f28d050021f127de"}