FHIR Connectathon 11 Testing - Track 2 - Terminology Services

Conventions Used

The execution of the TestScript resources contained in this folder are constrained by the following conventions:

Fixtures - All resource reference values can be either url paths or local local file system paths. The convention for these TestScript resources use local file system paths where the execution engine is expected to resolve this path based on the following:
- Leading '/' character - this is resolved as an absolute path based on a known root path
- No leading '/' character - this is resolved as a relative path based on the location of the TestScript resource file

FHIR Connectathon 11 Testing - Orlando, FL - January 2016

Track 2 - Terminology Services

The TestScript resources in this folder represent a conversion** of the TestScript originally used at the 1st Terminology Services Connectathon held in Washington, February 2014.

The original single TestScript has been separated into four (4) separate TestScript definitions - one for each original test suite. In addition, each of those TestScripts have two variations based on whether the FHIR client or server assigns the resource id of the required ValueSet resources created in the setup.

FHIR Resource ID Assigned by the Client

TestScript Name	Description
track2-terminology-ts-suite1-client-id	Terminology test suite 1 where the FHIR client assigns the ValueSet resource id in the setup.
track2-terminology-ts-suite2-client-id	Terminology test suite 2 where the FHIR client assigns the ValueSet resource id in the setup.
track2-terminology-ts-suite3-client-id	Terminology test suite 3 where the FHIR client assigns the ValueSet resource id in the setup.
track2-terminology-ts-suite4-client-id	Terminology test suite 4 where the FHIR client assigns the ValueSet resource id in the setup.

FHIR Resource ID Assigned by the Server

TestScript Name	Description
track2-terminology-ts-suite1-server-id	Terminology test suite 1 where the FHIR server assigns the ValueSet resource id in the setup.
track2-terminology-ts-suite2-server-id	Terminology test suite 2 where the FHIR server assigns the ValueSet resource id in the setup.
track2-terminology-ts-suite3-server-id	Terminology test suite 3 where the FHIR server assigns the ValueSet resource id in the setup.
track2-terminology-ts-suite4-server-id	Terminology test suite 4 where the FHIR server assigns the ValueSet resource id in the setup.

The main reasons for this separation are:

The new DSTU-2 TestScript definition no longer contains the <suite> element. Without the <suite> element as a grouping mechanism it made more sense to to break up the tests into separate TestScripts.
The overall separation of the original suite of tests into separate TestScript resources allows for a finer execution control.
The <setup> from the original TestScript definition has been replcated to each of the new TestScript resource in order to follow industry best practices of each TestScript remaining independently executable.

** This representation of the Terminology Services tests is not meant to be diffinitive and complete. This is one example of how these tests can be defined in the current DSTU-2 format of the TestScript resource. Constructive feedback, suggestions and critisms are welcome.

Richard Ettema, AEGIS.net
richard.ettema@aegis.net