FHIR Testing 2026

Acknowledgement

The given structure of this track is mainly based on HL7 International's Connectathon Patient Track definition.

Short Description

Automated testing of FHIR Servers with new open source tools provided by HL7 Austria.

Long Description

The goal of this track is to gain experience with automated FHIR testing, using the new open source tool set “TestFhiry” provided by HL7 Austria and developed by FH OÖ Hagenberg. It consists of two components, a tool for automated on-premise testing (called “TestFhiry Tester”) based on FHIR TestScript Resources and a tool for creating such test artifacts (called “TestFhiry Tinker Tool”).

This track is marked as experimental, since both tools were published at the beginning of 2026 and are considered beta versions.

The overall goal of this track is to be able to create and adapt test scripts and test data using the Tinker Tool and to use those test artifacts for automated testing with the Tester Tool. However, there are already test scripts prepared for FHIR Server, based on the HL7 Austria FHIR Core IG, in order to enable a quick start.

Optional goal:

Using the import feature of the Tester Tool to work with TestScript that participants brought with them, e.g. from other FHIR IGs or FHIR Server testing sessions.

Discussion:

  • Possibilities for CI Pipeline Integration during the build process

  • Extended functionality: testing possibilities for FHIR Clients

Type

Experimental

Submitting Work Group/
Project/
Accelerator/
Affiliate/
Implementer Group  

HL7 Austria

Track Lead(s)

Reinhard Egelkraut

Support:

Laura Ziebermayr

Track Lead Email(s)

tc-fhir@hl7.at

Related Tracks

HL7 AT FHIR Core IG Track 2026 – HL7 Austria (in case the basics are required)

FHIR Version

FHIR R4 & R5

Specification(s) this track uses

Official implemenation support by HL7 for Testing FHIR

Artifacts of focus

TestScript:

Date / Time

Monday March 2nd, 09:00am-17:00pm CET

Test Servers / Tools

TestFhiry Tester: GitHub - HL7Austria/HL7-AT-TestFhiry-TestRunner

TestFhiry Tinker Tool: GitHub - HL7Austria/HL7-AT-TestFhiry-TinkerTool

Expected participants

In general this track is open for all participants, vendors of FHIR Servers or FHIR Solutions would benefit the most.

But even if you are completely new to FHIR you may pay us a visit to get familiar with the concepts of FHIR Testing.

Track Details

System Roles

FHIR Server/Solutions

  • System under test by the automated test tool

Pre-Requisites (depending on use case)

  • TestFhiry Tester

    • FHIR Server/Solution to run the automated tests against

  • TestFhiry Tinker Tool

    • None

Preparations

Ideally, participants should be familiar with the FHIR TestScript Resource

Example Instances

are part of the github repositories

Scenarios

The following test scenarios are examples that are based on the profiles of the HL7 AT FHIR Core IGs. If participants are interested in other FHIR IGs, the corresponding test scenarios can be addressed as well.

Level 1: Basic test run

Creation of a TestScript Resource (or using a prepared one) that covers

  • Create AT Core Patient resource(s)
    system submits resources showing citizenship extension, citizenship extension, and address extensions

  • Update an existing AT Core Patient resource(s)
    system submits updated resources showing citizenship extension, citizenship extension, and address extensions

  • Search for AT Core Patient resource(s)
    system submits a properly formatted Search request for AT Core Patient resource(s) using parameters such as (along or in combination)

Level 2: Advanced Tests

Creation of a TestScript Resource (or using a prepared one) that covers additionally

  • Delete an existing AT Core Patient resource(s)
    system submits a delete request for specific AT Core Patient resource(s)

  • Complete workflow showing Create, Update, Read, read History, vRead, Search and Delete of an AT Core Patient resource in the same testscript

Level 3: Discussions

Down the rabbit hole 🐇

We are happy to follow any topic requiring a deep dive into technical/semantic/organisational/etc. discussions.

Suggested general topics

  • Possibilities for CI Pipeline Integration during the build process

  • Extended functionality: testing possibilities for FHIR Clients

Furthermore we’d like to verify the following topics with the participants

Tinker Tool:

  • Check Usability

  • Double check the input via the UI with the resulting TestScript JSON File

  • Check if the version handling between R4/R5 is correct (incl. preparations for R6)

  • Potential other Features

Tester Tool:

  • Folder structure vs. download features

  • Verification of the download features with existing IGs

  • Verification of the Fixtures
    focus on references between Fixtures (e.g. Patient to Organization)
    Fixture Delete process needs improvement
    creation of new Fixtures

  • Profile handling

  • Implementation of tests for DELETE of resources

Security and Privacy considerations

Do not submit personal data (in particular, social insurance numbers and the like). Development and Test clusters require authentication, but are not encrypted and hardened like a production instance would be - use only the provided pseudo certificates.