A set of tests that are executed by some runner to test the functionality of a tool in the FHIR ecosystem

The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes.

Within the context of the FHIR RESTful interactions, the resource has an id except for cases like the create and conditional update. Otherwise, the use of the resouce id depends on the given use case.

The metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content might not always be associated with version changes to the resource.

A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content. Often, this is a reference to an implementation guide that defines the special rules along with other profiles etc.

Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of its narrative along with other profiles, value sets, etc.

The base language in which the resource is written.

Language is provided to support indexing and accessibility (typically, services such as text to speech use the language tag). The html language tag in the narrative applies to the narrative. The language tag on the resource may be used to specify the language of other presentations generated from the data in the resource. Not all the content has to be in the base language. The Resource.language should not be assumed to apply to the narrative automatically. If a language is specified, it should it also be specified on the div element in the html (see rules in HTML5 for information about the relationship between xml:lang and the html lang attribute).

IETF language tag for a human language

An absolute URI that is used to identify test tests.

The identifier that is used to identify this version of these tests. Version must use SemVer

A natural language name identifying the tests. This name should be usable as an identifier for the module by machine processing applications such as code generation.

General description of these teats.

URL of documentation that explains how a runner would read these tests, and use them to actually test out a tool.

A script in a format understood by the runner that provides additional details about the execution of the test cases. The script provided depends on the definition of the runner; some runners do not cater for scripts, while others need a script.

A mode that can be passed to a runner running these these tests, that affects test content and influences how the tests are executed or evaulated (or even if they run)

The code by which the mode is identified when passed to runner

Description of what this mode does / why it was defined. This should explain to a tester when they should use the mode

A parameter passed to the runner when executing tests. Which parameters are valid, and how exactly the parameter is used are used depends on the definition of the runner

Name of parameter

The value of the parameter. If the value is an Expression, the definition of the runner describes what kind of expressions are allowed and the features/capabilities that they can make use of

If this mode is not passed to the runner, then this parameter will not be used

The scope indicates what kind of systems these test cases are intended to test

A reference to what is being tested

Description of what the scope is does / what is being tested

Another set of test cases that must be passed before these test cases are meaningful to execute. These test cases prove functionality that these tests require to execute

The test cases.

Description of what this mode does / why it was defined. This should explain to a tester why the

A suite of tests that all share a common set up, and can be executed as a group

The name by which this suite is known by in the test system. The name must be unique in the amongst the suites

Description of what this suite does / why it was defined. This should explain to a tester what they should know when deciding which tests to run

If this mode is not passed to the runner, then this suite will not be run

The resources used in the tests in this suite. How exactly they are used depends on the definition of the runner

A name that identifies this resource. The runner definition defines whether there must be a name, and what names there are

A file containing a resource used in the tests

Filename is relative to the folder/directory containing this TestCases

An inline resource used in the tests. How exactly it is used depends on the definition of the runner.

If this mode is not passed to the runner, then this resource will not be used

A parameter passed to the runner when executing tests. Which parameters are valid, and how exactly the parameter is used are used depends on the definition of the runner

An actual test in the test suite

The name by which this test is known by in the test system. The name must be unique in the suite

Description of what this test does / why it was defined. This should explain to a tester what they should know when looking at failing test results

A code that identifies the operation executed for this test. One of the codes defined in the definition of the runner

If this mode is not passed to the runner, then this test will not be run

The resources used when executing this test. How exactly they are used depends on the definition of the runner.

Resources expected as output from this test. Often, but not always, these resources are Matchetype resources. How exactly it is used depends on the definition of the runner. How exactly it is used depends on the definition of the runner, but the expectation is that these are the expected output, to which the actual output is compared

An assertion to run on the output of the test

Resources expected as output from this test. Often, but not always, these resources are Matchetype resources

Resources expected as output from this test. Often, but not always, these resources are Matchetype resources. How exactly it is used depends on the definition of the runner

The severity of the assertion

Resources expected as output from this test. Often, but not always, these resources are Matchetype resources. How exactly it is used depends on the definition of the runner

A human readable description of the assertion.

A nested set of tests

A set of tests that are executed by some runner to test the functionality of a tool in the FHIR ecosystem

An absolute URI that is used to identify test tests.

The identifier that is used to identify this version of these tests. Version must use SemVer

A natural language name identifying the tests. This name should be usable as an identifier for the module by machine processing applications such as code generation.

General description of these teats.

URL of documentation that explains how a runner would read these tests, and use them to actually test out a tool.

A script in a format understood by the runner that provides additional details about the execution of the test cases. The script provided depends on the definition of the runner; some runners do not cater for scripts, while others need a script.

A mode that can be passed to a runner running these these tests, that affects test content and influences how the tests are executed or evaulated (or even if they run)

The code by which the mode is identified when passed to runner

Description of what this mode does / why it was defined. This should explain to a tester when they should use the mode

A parameter passed to the runner when executing tests. Which parameters are valid, and how exactly the parameter is used are used depends on the definition of the runner

Name of parameter

The value of the parameter. If the value is an Expression, the definition of the runner describes what kind of expressions are allowed and the features/capabilities that they can make use of

If this mode is not passed to the runner, then this parameter will not be used

The scope indicates what kind of systems these test cases are intended to test

A reference to what is being tested

Description of what the scope is does / what is being tested

Another set of test cases that must be passed before these test cases are meaningful to execute. These test cases prove functionality that these tests require to execute

The test cases.

Description of what this mode does / why it was defined. This should explain to a tester why the

A suite of tests that all share a common set up, and can be executed as a group

The name by which this suite is known by in the test system. The name must be unique in the amongst the suites

Description of what this suite does / why it was defined. This should explain to a tester what they should know when deciding which tests to run

If this mode is not passed to the runner, then this suite will not be run

The resources used in the tests in this suite. How exactly they are used depends on the definition of the runner

A name that identifies this resource. The runner definition defines whether there must be a name, and what names there are

A file containing a resource used in the tests

Filename is relative to the folder/directory containing this TestCases

An inline resource used in the tests. How exactly it is used depends on the definition of the runner.

If this mode is not passed to the runner, then this resource will not be used

A parameter passed to the runner when executing tests. Which parameters are valid, and how exactly the parameter is used are used depends on the definition of the runner

An actual test in the test suite

The name by which this test is known by in the test system. The name must be unique in the suite

Description of what this test does / why it was defined. This should explain to a tester what they should know when looking at failing test results

A code that identifies the operation executed for this test. One of the codes defined in the definition of the runner

If this mode is not passed to the runner, then this test will not be run

The resources used when executing this test. How exactly they are used depends on the definition of the runner.

Resources expected as output from this test. Often, but not always, these resources are Matchetype resources. How exactly it is used depends on the definition of the runner. How exactly it is used depends on the definition of the runner, but the expectation is that these are the expected output, to which the actual output is compared

One or more assertions that can be executed against the output of the tests. These may be used with matchetypes to make rules about content the matchetypes leave open

An assertion to run on the output of the test

Resources expected as output from this test. Often, but not always, these resources are Matchetype resources

Resources expected as output from this test. Often, but not always, these resources are Matchetype resources. How exactly it is used depends on the definition of the runner

The severity of the assertion

Resources expected as output from this test. Often, but not always, these resources are Matchetype resources. How exactly it is used depends on the definition of the runner

A human readable description of the assertion.

A nested set of tests

A set of tests that are executed by some runner to test the functionality of a tool in the FHIR ecosystem

The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes.

Within the context of the FHIR RESTful interactions, the resource has an id except for cases like the create and conditional update. Otherwise, the use of the resouce id depends on the given use case.

The metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content might not always be associated with version changes to the resource.

A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content. Often, this is a reference to an implementation guide that defines the special rules along with other profiles etc.

Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of its narrative along with other profiles, value sets, etc.

The base language in which the resource is written.

Language is provided to support indexing and accessibility (typically, services such as text to speech use the language tag). The html language tag in the narrative applies to the narrative. The language tag on the resource may be used to specify the language of other presentations generated from the data in the resource. Not all the content has to be in the base language. The Resource.language should not be assumed to apply to the narrative automatically. If a language is specified, it should it also be specified on the div element in the html (see rules in HTML5 for information about the relationship between xml:lang and the html lang attribute).

IETF language tag for a human language

An absolute URI that is used to identify test tests.

The identifier that is used to identify this version of these tests. Version must use SemVer

A natural language name identifying the tests. This name should be usable as an identifier for the module by machine processing applications such as code generation.

General description of these teats.

URL of documentation that explains how a runner would read these tests, and use them to actually test out a tool.

A script in a format understood by the runner that provides additional details about the execution of the test cases. The script provided depends on the definition of the runner; some runners do not cater for scripts, while others need a script.

A mode that can be passed to a runner running these these tests, that affects test content and influences how the tests are executed or evaulated (or even if they run)

The code by which the mode is identified when passed to runner

Description of what this mode does / why it was defined. This should explain to a tester when they should use the mode

A parameter passed to the runner when executing tests. Which parameters are valid, and how exactly the parameter is used are used depends on the definition of the runner

Name of parameter

The value of the parameter. If the value is an Expression, the definition of the runner describes what kind of expressions are allowed and the features/capabilities that they can make use of

If this mode is not passed to the runner, then this parameter will not be used

The scope indicates what kind of systems these test cases are intended to test

A reference to what is being tested

Description of what the scope is does / what is being tested

Another set of test cases that must be passed before these test cases are meaningful to execute. These test cases prove functionality that these tests require to execute

The test cases.

Description of what this mode does / why it was defined. This should explain to a tester why the

A suite of tests that all share a common set up, and can be executed as a group

The name by which this suite is known by in the test system. The name must be unique in the amongst the suites

Description of what this suite does / why it was defined. This should explain to a tester what they should know when deciding which tests to run

If this mode is not passed to the runner, then this suite will not be run

The resources used in the tests in this suite. How exactly they are used depends on the definition of the runner

A name that identifies this resource. The runner definition defines whether there must be a name, and what names there are

A file containing a resource used in the tests

Filename is relative to the folder/directory containing this TestCases

An inline resource used in the tests. How exactly it is used depends on the definition of the runner.

If this mode is not passed to the runner, then this resource will not be used

A parameter passed to the runner when executing tests. Which parameters are valid, and how exactly the parameter is used are used depends on the definition of the runner

An actual test in the test suite

The name by which this test is known by in the test system. The name must be unique in the suite

Description of what this test does / why it was defined. This should explain to a tester what they should know when looking at failing test results

A code that identifies the operation executed for this test. One of the codes defined in the definition of the runner

If this mode is not passed to the runner, then this test will not be run

The resources used when executing this test. How exactly they are used depends on the definition of the runner.

Resources expected as output from this test. Often, but not always, these resources are Matchetype resources. How exactly it is used depends on the definition of the runner. How exactly it is used depends on the definition of the runner, but the expectation is that these are the expected output, to which the actual output is compared

An assertion to run on the output of the test

Resources expected as output from this test. Often, but not always, these resources are Matchetype resources

Resources expected as output from this test. Often, but not always, these resources are Matchetype resources. How exactly it is used depends on the definition of the runner

The severity of the assertion

Resources expected as output from this test. Often, but not always, these resources are Matchetype resources. How exactly it is used depends on the definition of the runner

A human readable description of the assertion.

A nested set of tests