A quantity- or range-valued use context assigned to the test script

A use context type and quantity- or range-based value assigned to the test script

A use context type and value assigned to the test script

A type of use context assigned to the test script

A use context assigned to the test script

The test script publication date

URL contained in TestPlan.dependency.reference

The description of the test script

Whether the TestPlan is experimental

An identifier for the test plan

Intended jurisdiction for the test script

Computationally friendly name of the test script

Name of the publisher of the test script

Reference to the runner for the test case

URL contained in TestPlan.scope.reference

The current status of the test plan

The human-friendly name of the test script

The uri that identifies the test plan

The business version of the test script

An external identifier for the test report

The test report generation date

The reference to a participant in the test execution

The result disposition of the test execution

The current status of the test report

The name of the testing organization

The test script executed to produce this report

The artifact under test

The artifact conformance testing expectation

A quantity- or range-valued use context assigned to the test script

A use context type and quantity- or range-based value assigned to the test script

A use context type and value assigned to the test script

A type of use context assigned to the test script

A use context assigned to the test script

The test script publication date

The description of the test script

Whether the TestScript is experimental

External identifier for the test script

Intended jurisdiction for the test script

Computationally friendly name of the test script

The artifact phase of testing

Name of the publisher of the test script

The artifact under test and conformance testing expectation

The artifact under test and phase of testing

The current status of the test script

TestScript required and validated capability

The human-friendly name of the test script

The uri that identifies the test script

The business version of the test script

A plan for executing testing on an artifact or specifications

A summary of information based on the results of executing a TestScript.

A structured set of tests against a FHIR server or client implementation to determine compliance against the FHIR specification.

Enforces the minimum information set for the test script metadata required by HL7 and other organizations that share and publish test scripts

The type of direction to use for assertion.

The type of manual completion to use for assertion.

The type of operator to use for assertion.

The type of response code to use for assertion.

The type of count.

The TestPlan test case assertion type.

The TestPlan test run script language.

The status of the TestPlan.

The results of executing an action.

The type of participant.

The reported execution result.

The current status of the test report.

This value set defines a set of codes that are used to indicate the supported operations of a testing engine or tool.

The allowable request method or HTTP operation codes.

The expectation of whether the test must pass for the system to be considered conformant with the artifact.

The phase of testing for this artifact.

The type of direction to use for assertion.

The type of manual completion to use for assertion.

The type of operator to use for assertion.

The type of response code to use for assertion.

The type of count.

The TestPlan test case assertion type.

The TestPlan test run script language.

The status of the TestPlan.

The results of executing an action.

The type of participant.

The reported execution result.

The current status of the test report.

The allowable request method or HTTP operation codes.

The expectation of whether the test must pass for the system to be considered conformant with the artifact.

The phase of testing for this artifact.

This test plan describes a manual test that a given observation can be read from the server using POSTMan. The user is instructed in the documentation to perform a POSTMan get with the $id in the URL and the Accept header, and compare with the expected output.

TestScript example resource showing use of origin and destination for multisystem support. The single origin will execute a Patient read against the two destination systems using user defined dynamic variables. The test engine will wait at each operation action with a defined origin and destination for the origin test system to send the expected FHIR operation to the destination test system. Once the expected request and response is observed, the test engine will continue with the test execution.

This is the test script the 1st Terminology Services Connectathon

This is a subset of the full terminology ecosystem tests

TestScript example resource with setup to delete if present and create a new instance of a Patient; and single test definition to read the created Patient with various asserts.

TestScript example resource the demonstrates the use of the artifact-effectivePeriod extenstion. There is a single test for a Patient read operation. The effective period range represents the period of use for the FHIR R4 v4.0.1 specification starting from its release date on Oct 30, 2019 with no expiration.

TestScript example resource with setup to delete if present and create a new instance of a Patient then update that Patient to create a minimum history; and single test definition to get the history of that Patient with various asserts.

TestScript example resource showing the use of the common element to reuse actions within the test element. Each test will perform a Patient read operation utilizing user defined dynamic variables that will hold the Patient resource id values.

TestScript example resource with ported Sprinkler basic read tests R001, R002, R003, R004. The read tests will utilize user defined dynamic variables that will hold the Patient resource id values.

TestScript example resource with simple Patient search test. The read tests will utilize user defined dynamic variables that will hold the Patient search parameter values.

TestScript example resource with setup to delete if present and create a new instance of a Patient; and single test definition to update that Patient with various asserts.