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

Identifier for the TestReport assigned for external purposes outside the context of FHIR.

A free text natural language name identifying the executed TestReport.

Not expected to be globally unique.

The current state of this test report.

The status represents where the execution is currently within the test script execution life cycle.

This element is labeled as a modifier because the status contains codes that mark the resource as not currently valid.

Ideally this is an absolute URL that is used to identify the version-specific TestScript that was executed, matching the TestScript.url.

The overall result from the execution of the TestScript.

The pass and fail result represents a completed test script execution. The pending result represents a test script execution that has not yet started or is currently in progress.

The final score (percentage of tests passed) resulting from the execution of the TestScript.

Name of the tester producing this report (Organization or individual).

Helps establish the "authority/credibility" of the TestReport. May also allow for contact.

Usually an organization, but may be an individual. This item SHOULD be populated unless the information is available from context.

When the TestScript was executed and this TestReport was generated.

Additional specific dates may be added as extensions.

A participant in the test execution, either the execution engine, a client, or a server.

The type of participant.

The uri of the participant. An absolute URL is preferred.

The display name of the participant.

The results of the series of required setup operations before the tests were executed.

Action would contain either an operation or an assertion.

An action should contain either an operation or an assertion but not both. It can contain any number of variables.

The operation performed.

The result of this operation.

An explanatory message associated with the result.

A link to further details on the result.

The results of the assertion performed on the previous operations.

The result of this assertion.

An explanatory message associated with the result.

A link to further details on the result.

Links or references providing traceability to the testing requirements for this assert.

TestScript and TestReport instances are typically (and expected to be) based on known, defined test requirements and documentation. These links provide traceability from the executable/executed TestScript and TestReport tests to these requirements.

Link or reference providing traceability to the testing requirement for this test.

A test executed from the test script.

The name of this test used for tracking/logging purposes by test engines.

A short description of the test used by test engines for tracking and reporting purposes.

Action would contain either an operation or an assertion.

An action should contain either an operation or an assertion but not both. It can contain any number of variables.

An operation would involve a REST request to a server.

The results of the assertion performed on the previous operations.

The results of the series of operations required to clean up after all the tests were executed (successfully or otherwise).

The teardown action will only contain an operation.

An action should contain either an operation or an assertion but not both. It can contain any number of variables.

An operation would involve a REST request to a server.