DSTU2 FHIR Release 3 (STU)

This page is part of the FHIR Specification (v1.0.2: DSTU (v3.0.2: STU 2). 3). The current version which supercedes this version is 5.0.0 . For a full list of available versions, see the Directory of published versions . Page versions: R5 R4B R4 R3 R2 R3 R2

6.24 7.3 Resource TestScript - Content

FHIR Infrastructure Work Group Maturity Level : 0 2   Trial Use Compartments : Not linked to any defined compartments

TestScript is a resource that specifies a suite A structured set of tests against a FHIR server implementation to determine compliance against the FHIR specification.

The TestScript resource is used to define tests that can be executed on one or more FHIR servers. The TestScript resource would typically contain

  • a list of fixtures (required resources used in the tests)
  • setup procedures
  • a suite of thematically related tests
  • teardown procedures

For example, one TestScript might feature a set of tests focusing on searching Patients and validating the Bundle responses. The fixtures for such a test would contain a list of Patient resources that are required for the test to complete successfully. The setup procedures create the fixtures on the FHIR server being tested. A series of tests execute various search parameters and search for the fixtures in the results. The teardown procedures would then clean up (delete) the fixtures on FHIR server that were created during the setup procedures.

The purpose of the TestScript is to encode in an executable representation tests that can be used to

  1. determine whether a given FHIR server adheres to the FHIR specification and
  2. determine whether two or more FHIR servers implement capabilities in a compatible or interoperable manner.
It may not be possible to fully automate the latter goal (especially with regards to business rules that might ride on top of different implementations), however the tests should be able to determine whether two servers support the operations, value sets, profiles, and extensions to exchange Bundles of Resources (such as returned from the Patient $everything operation ).

The TestScript resource should NOT be used to represent Clinical tests, Prescriptions, or any other Healthcare related concept. The TestScript resource is an infrastructure support resource used to represent standardized tests to determine an implementation's level of adherence to the FHIR specification.

The TestScript resource relies is a part of the conformance framework; its purpose framework and is used to validate the behavior of FHIR systems, specifically their correct implementation of StructureDefinition, ValueSet, OperationDefinition, CapabilityStatement and other FHIR resources that govern system behavior. TestScript instances may be included as part of ImplementationGuides to help define and test whether the desired behavior of systems conform that choose to a set of expectations. comply with the implementation guide.

The expectations following resources represent the FHIR conformance framework that are expressed using a combination of used to express the following resources: expected behavior of a FHIR compliant system:

The TestScript resource is designed to establish testing as a first class artifact within the FHIR specification. This resource allows defining a suite of tests that can be executed on one or more FHIR servers. The TestScript resource provides an implementation agnostic description of tests that allows test execution engines to evaluate if a server implementation conforms with the FHIR specification. Providing a clear and concise test methodology for the FHIR specification through the TestScript resource helps to enable interoperability among various FHIR server and client implementations. Furthermore, the TestScript resource provides clear examples of the appropriate use of the FHIR specification through test-based documentation. The TestScript resource stands as a form of executable documentation allowing developers to examine the operations defined by the tests to understand how various RESTful API interactions and resources should be used in coordination. The tests can also be automatically executed against systems under development to determine how well the systems adhere to the specification. The TestScript resource contains: Name and description detailing the purpose of the test suite Links describing how the test suite relates to the FHIR specification A list of server interactions required to execute the test suite A list of server interactions that the test suite validates the correctness of The fixtures (required data or resources) the tests use during execution A set of operations to set up the test suite environment A list of tests each containing Name servers and description of the test Links describing how the test relates to the FHIR specification A list of server interactions required to execute the test A list of server interactions that the test validates the correctness of A list of operations that provide the execution logic of the test A list of assertions that provide the verification logic of the test A set of operations to tear down the test environment 6.24.3.2 Execution 6.24.3.2.1 Workflow Pre-Processing The TestScript execution workflow begins by determining if the test suite is appropriate for the server under test. This can be determined by evaluating if the interactions listed in the TestScript metadata "capabilities" section are supported by the server's conformance resource. If the capabilities are supported by the server, then the TestScript can be executed. Otherwise, the TestScript as a whole or a specific test within the test script may be skipped depending on where the capabilities section is defined. See How to specify metadata capabilities . If the server supports the requirements of the TestScript instance, any specified fixtures are loaded or retrieved. If the fixtures are marked as 'autocreate' then they are automatically created on the server(s) under test using 'create' operations. If any of the autocreate operations fail, then the tests in the TestScript are skipped. Setup Execution clients.

After the fixtures are loaded and autocreates are executed, then the setup section is executed to establish the test suite environment. The purpose of the setup section is typically to pre-load data (if it was not autocreated) required for the execution of the tests into the FHIR server under test. The setup operations are executed once before all the tests are run (see Operation Execution ). All operations in a setup section (including assertions) must complete successfully for the tests to be executed. If an assertion operation in the setup section fails, then execution and evaluation of the tests in the TestScript Implementers should be skipped. Technically, any operation (see the operations table for a complete listing) can be included in the setup section, but typical operations will be create, update, read, and vread. Due to the possibility that the setup actions are not required on the server under test, the TestScript execution workflow MAY provide the capability of skipping or ignoring the setup section of familiar with the TestScript. Test Execution Once setup is complete, each test is executed. Tests contain a set of operations, testing concepts and executing a test involves the evaluation of each operation listed in the test descriptions found in the order defined by the test (see Operation Execution and the list of operations ). Teardown Execution After all the tests have completed execution, the teardown section is executed. The purpose of the teardown section is to revert the Testing FHIR server under test to a pre-test clean state. This requires removing any resources or artifacts generated as part of test suite setup or test execution. Technically, any operation (see the operations table for a complete listing) can be included in the teardown section, but the most often used operation will be delete. Assertions are not supported in the teardown section. Due to the possibility that the teardown actions are not required on the server under test, the TestScript execution workflow MAY provide the capability of skipping or ignoring the teardown section of the TestScript. Post-Processing After the teardown section is executed, any fixtures that were marked 'autodelete' are removed from the server(s) under test. After before working with this final stage, the execution of the TestScript is complete. resource.

6.24.3.2.2 Fixtures

The fixtures section of the TestScript defines a set of resource instances that will be used as part of the setup, test, and teardown sections during TestScript execution. The fixtures are required for the test script to execute. Each fixture defines a resource instance by URI, and must be identified by an ID. The URI can be local or remote (i.e. another server than the one the TestScript resource resides), absolute or relative. The ID on the fixture is considered the "source" identifier of the fixture -- it is not the same thing as the This resource ID on the server where it was hosted. The "source" identifier is used to define the fixture instance within the context of the TestScript. Operations reference the ID of a fixture to uniquely identify the fixture instance the operation is using ("sourceId") or acting against ("targetId"). Once a fixture has been instantiated on a server (typically referenced by the use of a create operation), the fixture ID is mapped to the ID of the corresponding resource instance on the server. TestScript execution engines must maintain this relationship between fixture IDs and server resource IDs. The TestScript execution engine is responsible for translating the fixture IDs (whether provided to the operation as "source" or "target") to the ID of the resource on the server during execution. Using the optional "autocreate" and "autodelete" elements (missing values default to false), fixtures can be configured to automatically be created during TestScript setup and automatically deleted during TestScript teardown. This means that additional "create" and "delete" operations in the TestScript.setup and TestScript.teardown sections are unnecessary. 6.24.3.2.3 Variables testreport The variables section of the TestScript defines a set of expressions whose evaluations will be used in substitutions. These substitutions are performed in operation request headers and URL paths as well as assertion values.

Without variables, search parameters and request headers (such as If-Modified-Since) would be specified in outgoing requests as literal values. Variables allow the values to be managed externally in fixtures or dynamically in server response fixtures. They would be defined to hold path expressions against the fixtures. The path expressions would not change from one server to another but the fixture data could. Using variables allows for the same test scripts to be executed against the same servers by different clients at the same time. Each client would change the fixture data (external to the test script) to make the data unique to that client. This ensures that the same delete/create/read operations executed concurrently by one client does not interfere with those of a another client. That can be important in testing environments such as a Connectathon. It can be very useful in year-round testing against public servers as well. See Use variables for more information. 6.24.3.2.4 Operation Execution The setup, test, and teardown sections of a TestScript can contain operation elements. Operations are intended to be executed in sequence and they represent the logic defined by the TestScript. Operations define a type, sourceId, targetid, destination, responseId, contentType, and other parameters. The type of the operation aligns with a corresponding RESTful API interaction. The sourceId and targetId of an operation define the context of the fixture data the operation is acting against (see Fixtures ). The destination defines the server the operation is executed on and is only required for tests that include multiple servers. The responseId specifies a fixture ID to use to map to the server response. The contentType defines the format (XML or JSON) and the corresponding mime-type (application/xml+fhir and application/json+fhir) to use in the RESTful operation (defaulting to XML). The parameters of an operation allow providing additional data required for execution. TestScript execution engines must load the operation details and execute the operation against the server(s) under test. Operations that are expected to result in an error or exception, shall immediately be followed by one or more "assertion" operations (that test for those error conditions), otherwise the test fails. This allows for "negative" testing (for example, the test script may perform operations that should return a 4XX or 5XX HTTP response code). Test execution is halted as soon as an operation or assertion fails. If an operation or assertion fails, then the test ends in failure and the test script execution proceeds to the next test. Once all tests have completed execution, the teardown section is executed. Once teardown completes, the suite execution is complete. If any setup or test operation or assertion failed, the test script is marked in failure. Failures in teardown are ignored. 6.24.3.2.5 Assertion Execution The "assertion" evaluates the results of previous operations to determine if the server under test behaves appropriately. In order to evaluate an assertion, the request, response, and results of the most recently executed operation must always be maintained by the TestScript execution engine. The TestScript execution engine must implement the behavior of each assertion to determine if the response of the last operation meets the conditions of the assertion. If the conditions of the assertion are met execution of the test continues. If the conditions of the assertion are not met, the test being executed fails and execution of the test is halted.

Structure

Absolute URL used Logical id for this Informal name External identifier If for testing purposes, not real usage 0..1 Name of a individual Contact details Date for this version of the TestScript 0..1 string Natural language description Σ Content intends to support these contexts Scope and Usage this Test Script is for Use and/or publishing restrictions Links Required Conformance Whether or not the tests apply to more than one FHIR server A series of required setup operations before tests are executed see metadata Capabilities that are assumed to function correctly on Which server metadata I 0..1 see metadata Capabilities that are expected to function correctly on the FHIR server being tested Test metadata capability SHALL contain required or validated or both. I 0..1
Name Flags Card. Type Description & Constraints doco
. . TestScript DomainResource Describes a set of tests
Elements defined in Ancestors: id , meta , implicitRules , language , text , contained , extension , modifierExtension
. . . url Σ 1..1 uri Logical URI to reference this TestScript test script (globally unique)
. . . identifier Σ 0..1 Identifier Additional identifier for the test script
... version Σ 0..1 string Business version of the TestScript test script
. . . name Σ 1..1 string Name for this TestScript test script (computer friendly)
. . . title Σ 0..1 string Name for this test script (human friendly)
... status ?! Σ 1..1 code draft | active | retired | unknown
ConformanceResourceStatus PublicationStatus ( Required )
. . identifier . experimental ?! Σ 0..1 Identifier boolean For testing purposes, not real usage
. . experimental . date Σ 0..1 boolean dateTime Date this was last changed
. . . publisher Σ 0..1 string Name of the publisher (Organization (organization or individual)
. . . contact Σ 0..* BackboneElement ContactDetail Contact details of for the publisher
. . . description name 0..1 markdown Natural language description of the test script
. . . useContext Σ 0..* string UsageContext Context the content is intended to contact support
. . telecom . jurisdiction Σ 0..* ContactPoint CodeableConcept Intended jurisdiction for individual or publisher test script (if applicable)
Jurisdiction ValueSet ( Extensible )
. . date . purpose Σ 0..1 markdown Why this test script is defined
... copyright 0..1 dateTime markdown Use and/or publishing restrictions
. . description . origin Σ 0..* BackboneElement An abstract server representing a client or sender in a message exchange
. . . . index 1..1 integer The index of the TestScript abstract origin server starting at 1
. . useContext . . profile 0..* 1..1 CodeableConcept Coding FHIR-Client | FHIR-SDC-FormFiller
Context of Use ValueSet TestScriptProfileOriginType ( Extensible )
. . requirements . destination 0..1 0..* string BackboneElement An abstract server representing a destination or receiver in a message exchange
. . copyright . . index 0..1 1..1 string integer The index of the abstract destination server starting at 1
. . . . profile 1..1 Coding FHIR-Server | FHIR-SDC-FormManager | FHIR-SDC-FormReceiver | FHIR-SDC-FormProcessor
TestScriptProfileDestinationType ( Extensible )
... metadata I 0..1 BackboneElement Required capability that is assumed to function correctly on the FHIR server being tested
+ TestScript metadata capability SHALL contain required or validated or both.
. . . . link 0..* BackboneElement Links to the FHIR specification
. . . . . url 1..1 uri URL to the specification
. . . . . description 0..1 string Short description
. . . . capability 1..* BackboneElement Capabilities that are assumed to function correctly on the FHIR server being tested
. . . . . required 0..1 boolean Are the capabilities required?
. . . . . validated 0..1 boolean Are the capabilities validated?
. . . . . description 0..1 string The expected capabilities of the server
. . . . destination . origin 0..1 0..* integer Which origin server these requirements apply to
. . . . link . destination 0..* 0..1 uri integer Which server these requirements apply to the FHIR specification
. . . . conformance . link 1..1 0..* Reference ( Conformance uri ) Links to the FHIR specification
. . multiserver . . . capabilities 0..1 1..1 boolean Reference ( CapabilityStatement ) Required Capability Statement
. . . fixture 0..* BackboneElement Fixture in the test script - by reference (uri)
. . . . autocreate 0..1 boolean Whether or not to implicitly create the fixture during setup
. . . . autodelete 0..1 boolean Whether or not to implicitly delete the fixture during teardown
. . . . resource 0..1 Reference ( Any ) Reference of the resource
. . . profile 0..* Reference ( Any ) Reference of the validation profile
. . . variable I 0..* BackboneElement Placeholder for evaluated elements
+ Variable cannot can only contain both one of expression, headerField and or path.
. . . . name 1..1 string Descriptive name for this variable
. . . . defaultValue 0..1 string Default, hard-coded, or user-defined value for this variable
.... description 0..1 string Natural language description of the variable
.... expression 0..1 string The fluentpath expression against the fixture body
.... headerField 0..1 string HTTP header field name for source
. . . . hint 0..1 string Hint help text for default value to enter
.... path 0..1 string XPath or JSONPath against the fixture body
. . . . sourceId 0..1 id Fixture Id of source expression or headerField within this variable
. . setup . rule 0..1 0..* BackboneElement Assert rule used within the test script
. . . metadata . resource I 1..1 Reference ( Any ) Assert rule resource reference
.... param 0..* BackboneElement Rule parameter template
..... name 1..1 string Parameter name matching external assert rule parameter
..... value 0..1 string Parameter value defined either explicitly or dynamically
... ruleset 0..* BackboneElement Assert ruleset used within the FHIR server being tested test script
Setup metadata capability SHALL contain required or validated
. . . . resource 1..1 Reference ( Any ) Assert ruleset resource reference
.... rule 1..* BackboneElement The referenced rule within the ruleset
..... ruleId 1..1 id Id of referenced rule within the ruleset
..... param 0..* BackboneElement Ruleset rule parameter template
...... name 1..1 string Parameter name matching external assert ruleset rule parameter
...... value 0..1 string Parameter value defined either explicitly or both. dynamically
... setup 0..1 BackboneElement A series of required setup operations before tests are executed
. . . . action I 1..* BackboneElement A setup operation or assert to perform
+ Setup action SHALL contain either an operation or assert but not both.
. . . . . operation I 0..1 BackboneElement The setup operation to perform
+ Setup operation SHALL contain either sourceId or targetId or params or url.
. . . . . . type 0..1 Coding The setup operation code type that will be executed
TestScriptOperationCodes TestScriptOperationCode ( Extensible )
. . . . . . resource 0..1 code Resource type
FHIRDefinedType ( Required )
. . . . . . label 0..1 string Tracking/logging operation label
. . . . . . description 0..1 string Tracking/reporting operation description
. . . . . . accept 0..1 code xml | json | ttl | none
ContentType ( Required )
. . . . . . contentType 0..1 code xml | json | ttl | none
ContentType ( Required )
. . . . . . destination 0..1 integer Server responding to perform the operation on request
. . . . . . encodeRequestUrl 0..1 boolean Whether or not to send the request url in encoded format
. . . . . . origin 0..1 integer Server initiating the request
...... params 0..1 string Explicitly defined path parameters
. . . . . . requestHeader 0..* BackboneElement Each operation can have one ore or more header elements
. . . . . . . field 1..1 string HTTP header field name
. . . . . . . value 1..1 string HTTP headerfield value
. . . . . . requestId 0..1 id Fixture Id of mapped request
...... responseId 0..1 id Fixture Id of mapped response
. . . . . . sourceId 0..1 id Fixture Id of body for PUT and POST requests
. . . . . . targetId 0..1 id Id of fixture used for extracting the [id], [type], and [vid] for GET requests
. . . . . . url 0..1 string Request URL
. . . . . assert I 0..1 BackboneElement The assertion to perform
+ Only a single assertion SHALL be present within setup action assert element.
+ Setup action assert shall SHALL contain both either compareToSourceId and compareToSourceExpression, compareToSourceId and compareToSourcePath or neither.
Only a single assertion SHALL be present within setup + Setup action assert element. response and responseCode SHALL be empty when direction equals request
. . . . . . label 0..1 string Tracking/logging assertion label
. . . . . . description 0..1 string Tracking/reporting assertion description
. . . . . . direction 0..1 code response | request
AssertionDirectionType ( Required )
. . . . . . compareToSourceId 0..1 string Id of the source fixture used to compare the "sourceId/path" evaluations be evaluated
...... compareToSourceExpression 0..1 string The fluentpath expression to evaluate against the source fixture
. . . . . . compareToSourcePath 0..1 string XPath or JSONPath expression against fixture used to compare evaluate against the "sourceId/path" evaluations to source fixture
. . . . . . contentType 0..1 code xml | json | ttl | none
ContentType ( Required )
. . . . . . expression 0..1 string The fluentpath expression to be evaluated
...... headerField 0..1 string HTTP header field name
. . . . . . minimumId 0..1 string Fixture Id of minimum content resource
. . . . . . navigationLinks 0..1 boolean Perform validation on navigation links?
. . . . . . operator 0..1 code equals | notEquals | in | notIn | greaterThan | lessThan | empty | notEmpty | contains | notContains | eval
AssertionOperatorType ( Required )
. . . . . . path 0..1 string XPath or JSONPath expression
. . . . . . requestMethod 0..1 code delete | get | options | patch | post | put
TestScriptRequestMethodCode ( Required )
...... requestURL 0..1 string Request URL comparison value
...... resource 0..1 code Resource type
FHIRDefinedType ( Required )
. . . . . . response 0..1 code okay | created | noContent | notModified | bad | forbidden | notFound | methodNotAllowed | conflict | gone | preconditionFailed | unprocessable
AssertionResponseTypes ( Required )
. . . . . . responseCode 0..1 string HTTP response code to test
. . . . . . rule 0..1 BackboneElement The reference to a TestScript.rule
....... ruleId 1..1 id Id of the TestScript.rule
....... param 0..* BackboneElement Rule parameter template
........ name 1..1 string Parameter name matching external assert rule parameter
........ value 1..1 string Parameter value defined either explicitly or dynamically
...... ruleset 0..1 BackboneElement The reference to a TestScript.ruleset
....... rulesetId 1..1 id Id of the TestScript.ruleset
....... rule 0..* BackboneElement The referenced rule within the ruleset
........ ruleId 1..1 id Id of referenced rule within the ruleset
........ param 0..* BackboneElement Rule parameter template
......... name 1..1 string Parameter name matching external assert ruleset rule parameter
......... value 1..1 string Parameter value defined either explicitly or dynamically
...... sourceId 0..1 id Fixture Id of source expression or headerField
. . . . . . validateProfileId 0..1 id Profile Id of validation profile reference
. . . . . . value 0..1 string The value to compare to
. . . . . . warningOnly 0..1 boolean Will this assert produce a warning only on error?
. . . test 0..* BackboneElement A test in this script
. . . . name 0..1 string Tracking/logging name of this test
. . . . description 0..1 string Tracking/reporting short description of the test
. . . . action I 1..* BackboneElement A test operation or assert to perform
+ Test action SHALL contain either an operation or assert but not both.
. . . . . operation I 0..1 see operation The setup operation to perform
+ Test operation SHALL contain either sourceId or targetId or params or url.
. . . . . assert I 0..1 see assert The setup assertion to perform
+ Only a single assertion SHALL be present within test action assert element.
+ Test action assert shall SHALL contain both either compareToSourceId and compareToSourceExpression, compareToSourceId and compareToSourcePath or neither.
Only a single assertion SHALL be present within test + Test action assert element. response and response and responseCode SHALL be empty when direction equals request
. . . teardown 0..1 BackboneElement A series of required clean up steps
. . . . action 1..* BackboneElement One or more teardown operations to perform
Teardown action SHALL contain an operation.
. . . . . operation I 1..1 see operation The teardown operation to perform
+ Teardown operation SHALL contain either sourceId or targetId or params or url.

doco Documentation for this format

UML Diagram ( Legend )

TestScript ( DomainResource ) An absolute URL URI that is used to identify this Test Script. test script when it is referenced in a specification, model, design or an instance. This SHALL be a URL, SHOULD be globally unique, and SHOULD be an address at which this Test Script test script is (or will be) published published. The URL SHOULD include the major version of the test script. For more information see [Technical and Business Versions](resource.html#versions) url : uri [1..1] A formal identifier that is used to identify this test script when it is represented in other formats, or referenced in a specification, model, design or an instance identifier : Identifier [0..1] The identifier that is used to identify this version of the TestScript. test script when it is referenced in a specification, model, design or instance. This is an arbitrary value managed by the TestScript test script author manually and is not expected to be globally unique. For example, it might be a timestamp (e.g. yyyymmdd) if a managed version is not available. There is also no expectation that versions can be placed in a lexicographical sequence version : string [0..1] A free text natural language name identifying the TestScript test script. This name should be usable as an identifier for the module by machine processing applications such as code generation name : string [1..1] A short, descriptive, user-friendly title for the test script title : string [0..1] The status of this test script. Enables tracking the TestScript life-cycle of the content (this element modifies the meaning of other elements) status : code [1..1] « The lifecycle status of a Value Set or Concept Map. (Strength=Required) ConformanceResourceStatus PublicationStatus ! » Identifier for the TestScript assigned for external purposes outside the context of FHIR identifier : Identifier [0..1] This TestScript was A boolean value to indicate that this test script is authored for testing purposes (or education/evaluation/marketing), and is not intended to be used for genuine usage (this element modifies the meaning of other elements) experimental : boolean [0..1] The name of the individual or organization that published the Test Script publisher : string [0..1] The date this version of (and optionally time) when the test tcript script was published. The date must change if and when the business version changes, if it does, changes and it must change if the status code changes. In addition, it should change when the substantive content of the test cases change script changes date : dateTime [0..1] The name of the individual or organization that published the test script publisher : string [0..1] Contact details to assist a user in finding and communicating with the publisher contact : ContactDetail [0..*] A free text natural language description of the TestScript and its use test script from a consumer's perspective description : string markdown [0..1] The content was developed with a focus and intent of supporting the contexts that are listed. These terms may be used to assist with indexing and searching of Test Scripts for appropriate test script instances useContext : UsageContext [0..*] A legal or geographic region in which the test script is intended to be used jurisdiction : CodeableConcept [0..*] « Indicates the countries, regions, disciplines Countries and other aspects of use regions within which this artifact is targeted for use. use (Strength=Extensible) Context of Use Jurisdiction ValueSet + » Explains Explaination of why this Test Script test script is needed and why it's it has been constrained designed as it has requirements purpose : string markdown [0..1] A copyright statement relating to the Test Script test script and/or its contents. Copyright statements are generally legal restrictions on the use and publishing of the details of the constraints and mappings test script copyright : string [0..1] If the tests apply to more than one FHIR server (e.g. cross-server interoperability tests) then multiserver=true. Defaults to false if value is unspecified multiserver : boolean markdown [0..1] Reference to the profile to be used for validation profile : Reference [0..*] « Any » Contact Origin Abstract name given to an origin server in this test script. The name is provided as a number starting at 1 index : integer [1..1] The type of an individual to contact regarding origin profile the Test Script test system supports name profile : string Coding [0..1] [1..1] The type of origin profile the test system supports. (Strength=Extensible) TestScriptProfileOriginType + Destination Contact details for individual (if Abstract name given to a destination server in this test script. The name was provided) or is provided as a number starting at 1 index : integer [1..1] The type of destination profile the publisher test system supports telecom profile : ContactPoint Coding [0..*] [1..1] The type of destination profile the test system supports. (Strength=Extensible) TestScriptProfileDestinationT... + Metadata Link URL to a particular requirement or feature within the FHIR specification url : uri [1..1] Short description of the link description : string [0..1] Capability Whether or not the test execution will require the given capabilities of the server in order for this test script to execute required : boolean [0..1] Whether or not the test execution will validate the given capabilities of the server in order for this test script to execute validated : boolean [0..1] Description of the capabilities that this test script is requiring the server to support description : string [0..1] Which origin server these requirements apply to origin : integer [0..*] Which server these requirements apply to destination : integer [0..1] Links to the FHIR specification that describes this interaction and the resources involved in more detail link : uri [0..*] Minimum conformance capabilities required of server for test script to execute successfully. If server does not meet at a minimum the reference conformance definition, referenced capability statement, then all tests in this script are skipped conformance capabilities : Reference [1..1] « Conformance CapabilityStatement » Fixture Whether or not to implicitly create the fixture during setup. If true, the fixture is automatically created on each server being tested during setup, therefore no create operation is required for this fixture in the TestScript.setup section autocreate : boolean [0..1] Whether or not to implicitly delete the fixture during teardown teardown. If true, the fixture is automatically deleted on each server being tested during teardown, therefore no delete operation is required for this fixture in the TestScript.teardown section autodelete : boolean [0..1] Reference to the resource (containing the contents of the resource needed for operations) resource : Reference [0..1] « Any » Variable Descriptive name for this variable name : string [1..1] A default, hard-coded, or user-defined value for this variable defaultValue : string [0..1] A free text natural language description of the variable and its purpose description : string [0..1] The fluentpath expression to evaluate against the fixture body. When variables are defined, only one of either expression, headerField or path must be specified expression : string [0..1] Will be used to grab the HTTP header field value from the headers that sourceId is pointing to headerField : string [0..1] Displayable text string with hint help information to the user when entering a default value hint : string [0..1] XPath or JSONPath to evaluate against the fixture body. When variables are defined, only one of either expression, headerField or path must be specified or path, but not both path : string [0..1] Fixture to evaluate the XPath/JSONPath expression or the headerField against within this variable sourceId : id [0..1] Rule Reference to the resource (containing the contents of the rule needed for assertions) resource : Reference [1..1] Any RuleParam Descriptive name for this parameter that matches the external assert rule parameter name name : string [1..1] The explicit or dynamic value for the parameter that will be passed on to the external rule template value : string [0..1] Ruleset Reference to the resource (containing the contents of the ruleset needed for assertions) resource : Reference [1..1] Any RulesetRule Id of the referenced rule within the external ruleset template ruleId : id [1..1] RulesetRuleParam Descriptive name for this parameter that matches the external assert ruleset rule parameter name name : string [1..1] The value for the parameter that will be passed on to the external ruleset rule template value : string [0..1] Setup Action SetupAction Operation Server interaction or operation type type : Coding [0..1] « The allowable operation code types. (Strength=Extensible) TestScriptOperationCodes TestScriptOperationCode + » The type of the resource. See http://hl7-fhir.github.io/resourcelist.html http://hl7.org/fhir/STU3/resourcelist.html resource : code [0..1] « Either a resource or a data type. (Strength=Required) FHIRDefinedType ! » The label would be used for tracking/logging purposes by test engines label : string [0..1] The description would be used by test engines for tracking and reporting purposes description : string [0..1] The content-type or mime-type to use for RESTful operation in the 'Accept' header accept : code [0..1] « The content or mime type. (Strength=Required) ContentType ! » The content-type or mime-type to use for RESTful operation in the 'Content-Type' header contentType : code [0..1] « The content or mime type. (Strength=Required) ContentType ! » Which The server to perform where the operation on request message is destined for. Must be one of the server numbers listed in TestScript.destination section destination : integer [0..1] Whether or not to implicitly send the request url in encoded format. The default is true to match the standard RESTful client behavior. Set to false when communicating with a server that does not support encoded url paths encodeRequestUrl : boolean [0..1] The server where the request message originates from. Must be one of the server numbers listed in TestScript.origin section origin : integer [0..1] Path plus parameters after [type]. Used to set parts of the request URL explicitly params : string [0..1] The fixture id (maybe new) to map to the request requestId : id [0..1] The fixture id (maybe new) to map to the response responseId : id [0..1] The id of the fixture used as the body of a PUT or POST request sourceId : id [0..1] Id of fixture used for extracting the [id], [type], and [vid] for GET requests targetId : id [0..1] Complete request URL url : string [0..1] RequestHeader The HTTP header field e.g. "Accept" field : string [1..1] The value of the header e.g. "application/xml" "application/fhir+xml" value : string [1..1] Assert The label would be used for tracking/logging purposes by test engines label : string [0..1] The description would be used by test engines for tracking and reporting purposes description : string [0..1] The direction to use for the assertion direction : code [0..1] « The type of direction to use for assertion. (Strength=Required) AssertionDirectionType ! » Id of the source fixture used as the contents to compare be evaluated by either the "source/expression" or "sourceId/path" evaluations to definition compareToSourceId : string [0..1] The fluentpath expression to evaluate against the source fixture. When compareToSourceId is defined, either compareToSourceExpression or compareToSourcePath must be defined, but not both compareToSourceExpression : string [0..1] XPath or JSONPath expression against fixture used to compare evaluate against the "sourceId/path" evaluations to source fixture. When compareToSourceId is defined, either compareToSourceExpression or compareToSourcePath must be defined, but not both compareToSourcePath : string [0..1] The content-type or mime-type to use for RESTful operation in the 'Content-Type' header contentType : code [0..1] « The content or mime type. (Strength=Required) ContentType ! » The fluentpath expression to be evaluated against the request or response message contents - HTTP headers and payload expression : string [0..1] The HTTP header field name e.g. 'Location' headerField : string [0..1] The ID of a fixture. Asserts that the response contains at a minimumId minimum the fixture specified by minimumId minimumId : string [0..1] Whether or not the test execution performs validation on the bundle navigation links navigationLinks : boolean [0..1] The operator type defines the conditional behavior of the assert. If not defined, the default is equals operator : code [0..1] « The type of operator to use for assertion. (Strength=Required) AssertionOperatorType ! » The XPath or JSONPath expression to be evaluated against the fixture representing the response received from server path : string [0..1] The request method or HTTP operation code to compare against that used by the client system under test requestMethod : code [0..1] The allowable request method or HTTP operation codes. (Strength=Required) TestScriptRequestMethodCode ! The value to use in a comparison against the request URL path string requestURL : string [0..1] The type of the resource. See http://hl7-fhir.github.io/resourcelist.html http://hl7.org/fhir/STU3/resourcelist.html resource : code [0..1] « Either a resource or a data type. (Strength=Required) FHIRDefinedType ! » okay | created | noContent | notModified | bad | forbidden | notFound | methodNotAllowed | conflict | gone | preconditionFailed | unprocessable response : code [0..1] « The type of response code to use for assertion. (Strength=Required) AssertionResponseTypes ! » The value of the HTTP response code to be tested responseCode : string [0..1] Fixture to evaluate the XPath/JSONPath expression or the headerField against sourceId : id [0..1] The ID of the Profile to validate against validateProfileId : id [0..1] The value to compare to value : string [0..1] Whether or not the test execution will produce a warning only on error for this assert warningOnly : boolean [0..1] ActionAssertRule The TestScript.rule id value this assert will evaluate ruleId : id [1..1] ActionAssertRuleParam Descriptive name for this parameter that matches the external assert rule parameter name name : string [1..1] The value for the parameter that will be passed on to the external rule template value : string [1..1] ActionAssertRuleset The TestScript.ruleset id value this assert will evaluate rulesetId : id [1..1] ActionAssertRulesetRule Id of the referenced rule within the external ruleset template ruleId : id [1..1] Param Descriptive name for this parameter that matches the external assert ruleset rule parameter name name : string [1..1] The value for the parameter that will be passed on to the external ruleset rule template value : string [1..1] Test The name of this test used for tracking/logging purposes by test engines name : string [0..1] A short description of the test used by test engines for tracking and reporting purposes description : string [0..1] Action TestAction Teardown Action TeardownAction Contacts to assist a user An abstract server used in operations within this test script in finding and communicating with the publisher origin element contact origin [0..*] An abstract server used in operations within this test script in the destination element destination [0..*] A link to the FHIR specification that this test is covering link [0..*] Capabilities that must exist and are assumed to function correctly on the FHIR server being tested capability [1..*] The required capability must exist and are assumed to function correctly on the FHIR server being tested metadata [0..1] Fixture in the test script - by reference (uri). All fixtures are required for the test script to execute fixture [0..*] Variable is set based either on element value in response body or on header field value in the response headers variable [0..*] Capabilities that must exist and are assumed Each rule template can take one or more parameters for rule evaluation param [0..*] Assert rule to function correctly on be used in one or more asserts within the FHIR server being tested test script metadata rule [0..1] [0..*] Each rule template can take one or more parameters for rule evaluation param [0..*] The referenced rule within the external ruleset template rule [1..*] Contains one or more rules. Offers a way to group rules so assertions could reference the group of rules and have them all applied ruleset [0..*] Header elements would be used to set HTTP headers requestHeader [0..*] The operation to perform operation [0..1] Each rule template can take one or more parameters for rule evaluation param [0..*] The TestScript.rule this assert will evaluate rule [0..1] Each rule template can take one or more parameters for rule evaluation param [0..*] The referenced rule within the external ruleset template rule [0..*] The TestScript.ruleset this assert will evaluate ruleset [0..1] Evaluates the results of previous operations to determine if the server under test behaves appropriately assert [0..1] Action would contain either an operation or an assertion action [1..*] A series of required setup operations before tests are executed setup [0..1] Capabilities that must exist and are assumed to function correctly on the FHIR server being tested metadata [0..1] An operation would involve a REST request to a server operation [0..1] Evaluates the results of previous operations to determine if the server under test behaves appropriately assert [0..1] Action would contain either an operation or an assertion action [1..*] A test in this script test [0..*] An operation would involve a REST request to a server operation [0..1] [1..1] The teardown action will only contain an operation action [1..*] A series of operations required to clean up after the all the tests are executed (successfully or otherwise) teardown [0..1]

XML Template

<

<TestScript xmlns="http://hl7.org/fhir"> doco

 <!-- from Resource: id, meta, implicitRules, and language -->
 <!-- from DomainResource: text, contained, extension, and modifierExtension -->
 <
 <
 <
 <
 <</identifier>
 <
 <
 <
  <
  <</telecom>
 </contact>
 <
 <
 <</useContext>
 <
 <
 <
  <
   <
   <

 <url value="[uri]"/><!-- 1..1 Logical URI to reference this test script (globally unique) -->
 <identifier><!-- 0..1 Identifier Additional identifier for the test script --></identifier>
 <version value="[string]"/><!-- 0..1 Business version of the test script -->
 <name value="[string]"/><!-- 1..1 Name for this test script (computer friendly) -->
 <title value="[string]"/><!-- 0..1 Name for this test script (human friendly) -->
 <status value="[code]"/><!-- 1..1 draft | active | retired | unknown -->
 <experimental value="[boolean]"/><!-- 0..1 For testing purposes, not real usage -->
 <date value="[dateTime]"/><!-- 0..1 Date this was last changed -->
 <publisher value="[string]"/><!-- 0..1 Name of the publisher (organization or individual) -->
 <contact><!-- 0..* ContactDetail Contact details for the publisher --></contact>
 <description value="[markdown]"/><!-- 0..1 Natural language description of the test script -->
 <useContext><!-- 0..* UsageContext Context the content is intended to support --></useContext>
 <jurisdiction><!-- 0..* CodeableConcept Intended jurisdiction for test script (if applicable) --></jurisdiction>
 <purpose value="[markdown]"/><!-- 0..1 Why this test script is defined -->
 <copyright value="[markdown]"/><!-- 0..1 Use and/or publishing restrictions -->
 <origin>  <!-- 0..* An abstract server representing a client or sender in a message exchange -->
  <index value="[integer]"/><!-- 1..1 The index of the abstract origin server starting at 1 -->
  <profile><!-- 1..1 Coding FHIR-Client | FHIR-SDC-FormFiller --></profile>
 </origin>
 <destination>  <!-- 0..* An abstract server representing a destination or receiver in a message exchange -->
  <index value="[integer]"/><!-- 1..1 The index of the abstract destination server starting at 1 -->
  <profile><!-- 1..1 Coding FHIR-Server | FHIR-SDC-FormManager | FHIR-SDC-FormReceiver | FHIR-SDC-FormProcessor --></profile>
 </destination>
 <metadata>  <!-- 0..1 Required capability that is assumed to function correctly on the FHIR server being tested -->
  <link>  <!-- 0..* Links to the FHIR specification -->
   <url value="[uri]"/><!-- 1..1 URL to the specification -->
   <description value="[string]"/><!-- 0..1 Short description -->

  </link>
  <
   <
   <
   <
   <
   <
   <</conformance>

  <capability>  <!-- 1..* Capabilities  that are assumed to function correctly on the FHIR server being tested -->
   <required value="[boolean]"/><!-- 0..1 Are the capabilities required? -->
   <validated value="[boolean]"/><!-- 0..1 Are the capabilities validated? -->
   <description value="[string]"/><!-- 0..1 The expected capabilities of the server -->
   <origin value="[integer]"/><!-- 0..* Which origin server these requirements apply to -->
   <destination value="[integer]"/><!-- 0..1 Which server these requirements apply to -->
   <link value="[uri]"/><!-- 0..* Links to the FHIR specification -->
   <capabilities><!-- 1..1 Reference(CapabilityStatement) Required Capability Statement --></capabilities>

  </capability>
 </metadata>
 <
 <
  <
  <
  <</resource>

 <fixture>  <!-- 0..* Fixture in the test script - by reference (uri) -->
  <autocreate value="[boolean]"/><!-- 0..1 Whether or not to implicitly create the fixture during setup -->
  <autodelete value="[boolean]"/><!-- 0..1 Whether or not to implicitly delete the fixture during teardown -->
  <resource><!-- 0..1 Reference(Any) Reference of the resource --></resource>

 </fixture>
 <</profile>
 <
  <
  <
  <
  <

 <profile><!-- 0..* Reference(Any) Reference of the validation profile --></profile>
 <variable>  <!-- 0..* Placeholder for evaluated elements -->
  <name value="[string]"/><!-- 1..1 Descriptive name for this variable -->
  <defaultValue value="[string]"/><!-- 0..1 Default, hard-coded, or user-defined value for this variable -->
  <description value="[string]"/><!-- 0..1 Natural language description of the variable -->
  <expression value="[string]"/><!-- 0..1 The fluentpath expression against the fixture body -->
  <headerField value="[string]"/><!-- 0..1 HTTP header field name for source -->
  <hint value="[string]"/><!-- 0..1 Hint help text for default value to enter -->
  <path value="[string]"/><!-- 0..1 XPath or JSONPath against the fixture body -->
  <sourceId value="[id]"/><!-- 0..1 Fixture Id of source expression or headerField within this variable -->

 </variable>
 <
  <</metadata>
  <
   <
    <</type>
    <
    <
    <
    <
    <
    <
    <
    <
    <
     <
     <

 <rule>  <!-- 0..* Assert rule used within the test script -->
  <resource><!-- 1..1 Reference(Any) Assert rule resource reference --></resource>
  <param>  <!-- 0..* Rule parameter template -->
   <name value="[string]"/><!-- 1..1 Parameter name matching external assert rule parameter -->
   <value value="[string]"/><!-- 0..1 Parameter value defined either explicitly or dynamically -->
  </param>
 </rule>
 <ruleset>  <!-- 0..* Assert ruleset used within the test script -->
  <resource><!-- 1..1 Reference(Any) Assert ruleset resource reference --></resource>
  <rule>  <!-- 1..* The referenced rule within the ruleset -->
   <ruleId value="[id]"/><!-- 1..1 Id of referenced rule within the ruleset -->
   <param>  <!-- 0..* Ruleset rule parameter template -->
    <name value="[string]"/><!-- 1..1 Parameter name matching external assert ruleset rule parameter -->
    <value value="[string]"/><!-- 0..1 Parameter value defined either explicitly or dynamically -->
   </param>
  </rule>
 </ruleset>
 <setup>  <!-- 0..1 A series of required setup operations before tests are executed -->
  <action>  <!-- 1..* A setup operation or assert to perform -->
   <operation>  <!-- 0..1 The setup operation to perform -->
    <type><!-- 0..1 Coding The operation code type that will be executed --></type>
    <resource value="[code]"/><!-- 0..1 Resource type -->
    <label value="[string]"/><!-- 0..1 Tracking/logging operation label -->
    <description value="[string]"/><!-- 0..1 Tracking/reporting operation description -->
    <accept value="[code]"/><!-- 0..1 xml | json | ttl | none -->
    <contentType value="[code]"/><!-- 0..1 xml | json | ttl | none -->
    <destination value="[integer]"/><!-- 0..1 Server responding to the request -->
    <encodeRequestUrl value="[boolean]"/><!-- 0..1 Whether or not to send the request url in encoded format -->
    <origin value="[integer]"/><!-- 0..1 Server initiating the request -->
    <params value="[string]"/><!-- 0..1 Explicitly defined path parameters -->
    <requestHeader>  <!-- 0..* Each operation can have one or more header elements -->
     <field value="[string]"/><!-- 1..1 HTTP header field name -->
     <value value="[string]"/><!-- 1..1 HTTP headerfield value -->

    </requestHeader>
    <
    <
    <
    <

    <requestId value="[id]"/><!-- 0..1 Fixture Id of mapped request -->
    <responseId value="[id]"/><!-- 0..1 Fixture Id of mapped response -->
    <sourceId value="[id]"/><!-- 0..1 Fixture Id of body for PUT and POST requests -->
    <targetId value="[id]"/><!-- 0..1 Id of fixture used for extracting the [id],  [type], and [vid] for GET requests -->
    <url value="[string]"/><!-- 0..1 Request URL -->

   </operation>
   <
    <
    <
    <
    <
    <
    <
    <
    <
    <
    <
    <
    <
    <
    <
    <
    <
    <
    <

   <assert>  <!-- 0..1 The assertion to perform -->
    <label value="[string]"/><!-- 0..1 Tracking/logging assertion label -->
    <description value="[string]"/><!-- 0..1 Tracking/reporting assertion description -->
    <direction value="[code]"/><!-- 0..1 response | request -->
    <compareToSourceId value="[string]"/><!-- 0..1 Id of the source fixture to be evaluated -->
    <compareToSourceExpression value="[string]"/><!-- 0..1 The fluentpath expression to evaluate against the source fixture -->
    <compareToSourcePath value="[string]"/><!-- 0..1 XPath or JSONPath expression to evaluate against the source fixture -->
    <contentType value="[code]"/><!-- 0..1 xml | json | ttl | none -->
    <expression value="[string]"/><!-- 0..1 The fluentpath expression to be evaluated -->
    <headerField value="[string]"/><!-- 0..1 HTTP header field name -->
    <minimumId value="[string]"/><!-- 0..1 Fixture Id of minimum content resource -->
    <navigationLinks value="[boolean]"/><!-- 0..1 Perform validation on navigation links? -->
    <operator value="[code]"/><!-- 0..1 equals | notEquals | in | notIn | greaterThan | lessThan | empty | notEmpty | contains | notContains | eval -->
    <path value="[string]"/><!-- 0..1 XPath or JSONPath expression -->
    <requestMethod value="[code]"/><!-- 0..1 delete | get | options | patch | post | put -->
    <requestURL value="[string]"/><!-- 0..1 Request URL comparison value -->
    <resource value="[code]"/><!-- 0..1 Resource type -->
    <response value="[code]"/><!-- 0..1 okay | created | noContent | notModified | bad | forbidden | notFound | methodNotAllowed | conflict | gone | preconditionFailed | unprocessable -->
    <responseCode value="[string]"/><!-- 0..1 HTTP response code to test -->
    <rule>  <!-- 0..1 The reference to a TestScript.rule -->
     <ruleId value="[id]"/><!-- 1..1 Id of the TestScript.rule -->
     <param>  <!-- 0..* Rule parameter template -->
      <name value="[string]"/><!-- 1..1 Parameter name matching external assert rule parameter -->
      <value value="[string]"/><!-- 1..1 Parameter value defined either explicitly or dynamically -->
     </param>
    </rule>
    <ruleset>  <!-- 0..1 The reference to a TestScript.ruleset -->
     <rulesetId value="[id]"/><!-- 1..1 Id of the TestScript.ruleset -->
     <rule>  <!-- 0..* The referenced rule within the ruleset -->
      <ruleId value="[id]"/><!-- 1..1 Id of referenced rule within the ruleset -->
      <param>  <!-- 0..* Rule parameter template -->
       <name value="[string]"/><!-- 1..1 Parameter name matching external assert ruleset rule parameter -->
       <value value="[string]"/><!-- 1..1 Parameter value defined either explicitly or dynamically -->
      </param>
     </rule>
    </ruleset>
    <sourceId value="[id]"/><!-- 0..1 Fixture Id of source expression or headerField -->
    <validateProfileId value="[id]"/><!-- 0..1 Profile Id of validation profile reference -->
    <value value="[string]"/><!-- 0..1 The value to compare to -->
    <warningOnly value="[boolean]"/><!-- 0..1 Will this assert produce a warning only on error? -->

   </assert>
  </action>
 </setup>
 <
  <
  <
  <</metadata>
  <
   <</operation>
   <</assert>

 <test>  <!-- 0..* A test in this script -->
  <name value="[string]"/><!-- 0..1 Tracking/logging name of this test -->
  <description value="[string]"/><!-- 0..1 Tracking/reporting short description of the test -->
  <action>  <!-- 1..* A test operation or assert to perform -->
   <operation><!-- 0..1 Content as for TestScript.setup.action.operation The setup operation to perform --></operation>
   <assert><!-- 0..1 Content as for TestScript.setup.action.assert The setup assertion to perform --></assert>

  </action>
 </test>
 <
  <
   <</operation>

 <teardown>  <!-- 0..1 A series of required clean up steps -->
  <action>  <!-- 1..* One or more teardown operations to perform -->
   <operation><!-- 1..1 Content as for TestScript.setup.action.operation The teardown operation to perform --></operation>

  </action>
 </teardown>
</TestScript>

JSON Template

{
  "resourceType" : "",

{doco
  "resourceType" : "TestScript",

  // from Resource: id, meta, implicitRules, and language
  // from DomainResource: text, contained, extension, and modifierExtension
  "
  "
  "
  "
  "
  "
  "
  "
    "
    "

  "url" : "<uri>", // R!  Logical URI to reference this test script (globally unique)
  "identifier" : { Identifier }, // Additional identifier for the test script
  "version" : "<string>", // Business version of the test script
  "name" : "<string>", // R!  Name for this test script (computer friendly)
  "title" : "<string>", // Name for this test script (human friendly)
  "status" : "<code>", // R!  draft | active | retired | unknown
  "experimental" : <boolean>, // For testing purposes, not real usage
  "date" : "<dateTime>", // Date this was last changed
  "publisher" : "<string>", // Name of the publisher (organization or individual)
  "contact" : [{ ContactDetail }], // Contact details for the publisher
  "description" : "<markdown>", // Natural language description of the test script
  "useContext" : [{ UsageContext }], // Context the content is intended to support
  "jurisdiction" : [{ CodeableConcept }], // Intended jurisdiction for test script (if applicable)
  "purpose" : "<markdown>", // Why this test script is defined
  "copyright" : "<markdown>", // Use and/or publishing restrictions
  "origin" : [{ // An abstract server representing a client or sender in a message exchange
    "index" : <integer>, // R!  The index of the abstract origin server starting at 1
    "profile" : { Coding } // R!  FHIR-Client | FHIR-SDC-FormFiller

  }],
  "
  "
  "
  "
  "
  "
    "
      "
      "

  "destination" : [{ // An abstract server representing a destination or receiver in a message exchange
    "index" : <integer>, // R!  The index of the abstract destination server starting at 1
    "profile" : { Coding } // R!  FHIR-Server | FHIR-SDC-FormManager | FHIR-SDC-FormReceiver | FHIR-SDC-FormProcessor
  }],
  "metadata" : { // Required capability that is assumed to function correctly on the FHIR server being tested
    "link" : [{ // Links to the FHIR specification
      "url" : "<uri>", // R!  URL to the specification
      "description" : "<string>" // Short description

    }],
    "
      "
      "
      "
      "
      "
      "

    "capability" : [{ // R!  Capabilities  that are assumed to function correctly on the FHIR server being tested
      "required" : <boolean>, // Are the capabilities required?
      "validated" : <boolean>, // Are the capabilities validated?
      "description" : "<string>", // The expected capabilities of the server
      "origin" : [<integer>], // Which origin server these requirements apply to
      "destination" : <integer>, // Which server these requirements apply to
      "link" : ["<uri>"], // Links to the FHIR specification
      "capabilities" : { Reference(CapabilityStatement) } // R!  Required Capability Statement

    }]
  },
  "
  "
    "
    "
    "

  "fixture" : [{ // Fixture in the test script - by reference (uri)
    "autocreate" : <boolean>, // Whether or not to implicitly create the fixture during setup
    "autodelete" : <boolean>, // Whether or not to implicitly delete the fixture during teardown
    "resource" : { Reference(Any) } // Reference of the resource

  }],
  "
  "
    "
    "
    "
    "

  "profile" : [{ Reference(Any) }], // Reference of the validation profile
  "variable" : [{ // Placeholder for evaluated elements
    "name" : "<string>", // R!  Descriptive name for this variable
    "defaultValue" : "<string>", // Default, hard-coded, or user-defined value for this variable
    "description" : "<string>", // Natural language description of the variable
    "expression" : "<string>", // The fluentpath expression against the fixture body
    "headerField" : "<string>", // HTTP header field name for source
    "hint" : "<string>", // Hint help text for default value to enter
    "path" : "<string>", // XPath or JSONPath against the fixture body
    "sourceId" : "<id>" // Fixture Id of source expression or headerField within this variable

  }],
  "
    "
    "
      "
        "
        "
        "
        "
        "
        "
        "
        "
        "
        "
          "
          "

  "rule" : [{ // Assert rule used within the test script
    "resource" : { Reference(Any) }, // R!  Assert rule resource reference
    "param" : [{ // Rule parameter template
      "name" : "<string>", // R!  Parameter name matching external assert rule parameter
      "value" : "<string>" // Parameter value defined either explicitly or dynamically
    }]
  }],
  "ruleset" : [{ // Assert ruleset used within the test script
    "resource" : { Reference(Any) }, // R!  Assert ruleset resource reference
    "rule" : [{ // R!  The referenced rule within the ruleset
      "ruleId" : "<id>", // R!  Id of referenced rule within the ruleset
      "param" : [{ // Ruleset rule parameter template
        "name" : "<string>", // R!  Parameter name matching external assert ruleset rule parameter
        "value" : "<string>" // Parameter value defined either explicitly or dynamically
      }]
    }]
  }],
  "setup" : { // A series of required setup operations before tests are executed
    "action" : [{ // R!  A setup operation or assert to perform
      "operation" : { // The setup operation to perform
        "type" : { Coding }, // The operation code type that will be executed
        "resource" : "<code>", // Resource type
        "label" : "<string>", // Tracking/logging operation label
        "description" : "<string>", // Tracking/reporting operation description
        "accept" : "<code>", // xml | json | ttl | none
        "contentType" : "<code>", // xml | json | ttl | none
        "destination" : <integer>, // Server responding to the request
        "encodeRequestUrl" : <boolean>, // Whether or not to send the request url in encoded format
        "origin" : <integer>, // Server initiating the request
        "params" : "<string>", // Explicitly defined path parameters
        "requestHeader" : [{ // Each operation can have one or more header elements
          "field" : "<string>", // R!  HTTP header field name
          "value" : "<string>" // R!  HTTP headerfield value

        }],
        "
        "
        "
        "

        "requestId" : "<id>", // Fixture Id of mapped request
        "responseId" : "<id>", // Fixture Id of mapped response
        "sourceId" : "<id>", // Fixture Id of body for PUT and POST requests
        "targetId" : "<id>", // Id of fixture used for extracting the [id],  [type], and [vid] for GET requests
        "url" : "<string>" // Request URL

      },
      "
        "
        "
        "
        "
        "
        "
        "
        "
        "
        "
        "
        "
        "
        "
        "
        "
        "
        "

      "assert" : { // The assertion to perform
        "label" : "<string>", // Tracking/logging assertion label
        "description" : "<string>", // Tracking/reporting assertion description
        "direction" : "<code>", // response | request
        "compareToSourceId" : "<string>", // Id of the source fixture to be evaluated
        "compareToSourceExpression" : "<string>", // The fluentpath expression to evaluate against the source fixture
        "compareToSourcePath" : "<string>", // XPath or JSONPath expression to evaluate against the source fixture
        "contentType" : "<code>", // xml | json | ttl | none
        "expression" : "<string>", // The fluentpath expression to be evaluated
        "headerField" : "<string>", // HTTP header field name
        "minimumId" : "<string>", // Fixture Id of minimum content resource
        "navigationLinks" : <boolean>, // Perform validation on navigation links?
        "operator" : "<code>", // equals | notEquals | in | notIn | greaterThan | lessThan | empty | notEmpty | contains | notContains | eval
        "path" : "<string>", // XPath or JSONPath expression
        "requestMethod" : "<code>", // delete | get | options | patch | post | put
        "requestURL" : "<string>", // Request URL comparison value
        "resource" : "<code>", // Resource type
        "response" : "<code>", // okay | created | noContent | notModified | bad | forbidden | notFound | methodNotAllowed | conflict | gone | preconditionFailed | unprocessable
        "responseCode" : "<string>", // HTTP response code to test
        "rule" : { // The reference to a TestScript.rule
          "ruleId" : "<id>", // R!  Id of the TestScript.rule
          "param" : [{ // Rule parameter template
            "name" : "<string>", // R!  Parameter name matching external assert rule parameter
            "value" : "<string>" // R!  Parameter value defined either explicitly or dynamically
          }]
        },
        "ruleset" : { // The reference to a TestScript.ruleset
          "rulesetId" : "<id>", // R!  Id of the TestScript.ruleset
          "rule" : [{ // The referenced rule within the ruleset
            "ruleId" : "<id>", // R!  Id of referenced rule within the ruleset
            "param" : [{ // Rule parameter template
              "name" : "<string>", // R!  Parameter name matching external assert ruleset rule parameter
              "value" : "<string>" // R!  Parameter value defined either explicitly or dynamically
            }]
          }]
        },
        "sourceId" : "<id>", // Fixture Id of source expression or headerField
        "validateProfileId" : "<id>", // Profile Id of validation profile reference
        "value" : "<string>", // The value to compare to
        "warningOnly" : <boolean> // Will this assert produce a warning only on error?

      }
    }]
  },
  "
    "
    "
    "
    "
      "
      "

  "test" : [{ // A test in this script
    "name" : "<string>", // Tracking/logging name of this test
    "description" : "<string>", // Tracking/reporting short description of the test
    "action" : [{ // R!  A test operation or assert to perform
      "operation" : { Content as for TestScript.setup.action.operation }, // The setup operation to perform
      "assert" : { Content as for TestScript.setup.action.assert } // The setup assertion to perform

    }]
  }],
  "
    "
      "

  "teardown" : { // A series of required clean up steps
    "action" : [{ // R!  One or more teardown operations to perform
      "operation" : { Content as for TestScript.setup.action.operation } // R!  The teardown operation to perform

    }]
  }
}

Turtle Template


@prefix fhir: <http://hl7.org/fhir/> .doco


[ a fhir:TestScript;
  fhir:nodeRole fhir:treeRoot; # if this is the parser root

  # from Resource: .id, .meta, .implicitRules, and .language
  # from DomainResource: .text, .contained, .extension, and .modifierExtension
  fhir:TestScript.url [ uri ]; # 1..1 Logical URI to reference this test script (globally unique)
  fhir:TestScript.identifier [ Identifier ]; # 0..1 Additional identifier for the test script
  fhir:TestScript.version [ string ]; # 0..1 Business version of the test script
  fhir:TestScript.name [ string ]; # 1..1 Name for this test script (computer friendly)
  fhir:TestScript.title [ string ]; # 0..1 Name for this test script (human friendly)
  fhir:TestScript.status [ code ]; # 1..1 draft | active | retired | unknown
  fhir:TestScript.experimental [ boolean ]; # 0..1 For testing purposes, not real usage
  fhir:TestScript.date [ dateTime ]; # 0..1 Date this was last changed
  fhir:TestScript.publisher [ string ]; # 0..1 Name of the publisher (organization or individual)
  fhir:TestScript.contact [ ContactDetail ], ... ; # 0..* Contact details for the publisher
  fhir:TestScript.description [ markdown ]; # 0..1 Natural language description of the test script
  fhir:TestScript.useContext [ UsageContext ], ... ; # 0..* Context the content is intended to support
  fhir:TestScript.jurisdiction [ CodeableConcept ], ... ; # 0..* Intended jurisdiction for test script (if applicable)
  fhir:TestScript.purpose [ markdown ]; # 0..1 Why this test script is defined
  fhir:TestScript.copyright [ markdown ]; # 0..1 Use and/or publishing restrictions
  fhir:TestScript.origin [ # 0..* An abstract server representing a client or sender in a message exchange
    fhir:TestScript.origin.index [ integer ]; # 1..1 The index of the abstract origin server starting at 1
    fhir:TestScript.origin.profile [ Coding ]; # 1..1 FHIR-Client | FHIR-SDC-FormFiller
  ], ...;
  fhir:TestScript.destination [ # 0..* An abstract server representing a destination or receiver in a message exchange
    fhir:TestScript.destination.index [ integer ]; # 1..1 The index of the abstract destination server starting at 1
    fhir:TestScript.destination.profile [ Coding ]; # 1..1 FHIR-Server | FHIR-SDC-FormManager | FHIR-SDC-FormReceiver | FHIR-SDC-FormProcessor
  ], ...;
  fhir:TestScript.metadata [ # 0..1 Required capability that is assumed to function correctly on the FHIR server being tested
    fhir:TestScript.metadata.link [ # 0..* Links to the FHIR specification
      fhir:TestScript.metadata.link.url [ uri ]; # 1..1 URL to the specification
      fhir:TestScript.metadata.link.description [ string ]; # 0..1 Short description
    ], ...;
    fhir:TestScript.metadata.capability [ # 1..* Capabilities  that are assumed to function correctly on the FHIR server being tested
      fhir:TestScript.metadata.capability.required [ boolean ]; # 0..1 Are the capabilities required?
      fhir:TestScript.metadata.capability.validated [ boolean ]; # 0..1 Are the capabilities validated?
      fhir:TestScript.metadata.capability.description [ string ]; # 0..1 The expected capabilities of the server
      fhir:TestScript.metadata.capability.origin [ integer ], ... ; # 0..* Which origin server these requirements apply to
      fhir:TestScript.metadata.capability.destination [ integer ]; # 0..1 Which server these requirements apply to
      fhir:TestScript.metadata.capability.link [ uri ], ... ; # 0..* Links to the FHIR specification
      fhir:TestScript.metadata.capability.capabilities [ Reference(CapabilityStatement) ]; # 1..1 Required Capability Statement
    ], ...;
  ];
  fhir:TestScript.fixture [ # 0..* Fixture in the test script - by reference (uri)
    fhir:TestScript.fixture.autocreate [ boolean ]; # 0..1 Whether or not to implicitly create the fixture during setup
    fhir:TestScript.fixture.autodelete [ boolean ]; # 0..1 Whether or not to implicitly delete the fixture during teardown
    fhir:TestScript.fixture.resource [ Reference(Any) ]; # 0..1 Reference of the resource
  ], ...;
  fhir:TestScript.profile [ Reference(Any) ], ... ; # 0..* Reference of the validation profile
  fhir:TestScript.variable [ # 0..* Placeholder for evaluated elements
    fhir:TestScript.variable.name [ string ]; # 1..1 Descriptive name for this variable
    fhir:TestScript.variable.defaultValue [ string ]; # 0..1 Default, hard-coded, or user-defined value for this variable
    fhir:TestScript.variable.description [ string ]; # 0..1 Natural language description of the variable
    fhir:TestScript.variable.expression [ string ]; # 0..1 The fluentpath expression against the fixture body
    fhir:TestScript.variable.headerField [ string ]; # 0..1 HTTP header field name for source
    fhir:TestScript.variable.hint [ string ]; # 0..1 Hint help text for default value to enter
    fhir:TestScript.variable.path [ string ]; # 0..1 XPath or JSONPath against the fixture body
    fhir:TestScript.variable.sourceId [ id ]; # 0..1 Fixture Id of source expression or headerField within this variable
  ], ...;
  fhir:TestScript.rule [ # 0..* Assert rule used within the test script
    fhir:TestScript.rule.resource [ Reference(Any) ]; # 1..1 Assert rule resource reference
    fhir:TestScript.rule.param [ # 0..* Rule parameter template
      fhir:TestScript.rule.param.name [ string ]; # 1..1 Parameter name matching external assert rule parameter
      fhir:TestScript.rule.param.value [ string ]; # 0..1 Parameter value defined either explicitly or dynamically
    ], ...;
  ], ...;
  fhir:TestScript.ruleset [ # 0..* Assert ruleset used within the test script
    fhir:TestScript.ruleset.resource [ Reference(Any) ]; # 1..1 Assert ruleset resource reference
    fhir:TestScript.ruleset.rule [ # 1..* The referenced rule within the ruleset
      fhir:TestScript.ruleset.rule.ruleId [ id ]; # 1..1 Id of referenced rule within the ruleset
      fhir:TestScript.ruleset.rule.param [ # 0..* Ruleset rule parameter template
        fhir:TestScript.ruleset.rule.param.name [ string ]; # 1..1 Parameter name matching external assert ruleset rule parameter
        fhir:TestScript.ruleset.rule.param.value [ string ]; # 0..1 Parameter value defined either explicitly or dynamically
      ], ...;
    ], ...;
  ], ...;
  fhir:TestScript.setup [ # 0..1 A series of required setup operations before tests are executed
    fhir:TestScript.setup.action [ # 1..* A setup operation or assert to perform
      fhir:TestScript.setup.action.operation [ # 0..1 The setup operation to perform
        fhir:TestScript.setup.action.operation.type [ Coding ]; # 0..1 The operation code type that will be executed
        fhir:TestScript.setup.action.operation.resource [ code ]; # 0..1 Resource type
        fhir:TestScript.setup.action.operation.label [ string ]; # 0..1 Tracking/logging operation label
        fhir:TestScript.setup.action.operation.description [ string ]; # 0..1 Tracking/reporting operation description
        fhir:TestScript.setup.action.operation.accept [ code ]; # 0..1 xml | json | ttl | none
        fhir:TestScript.setup.action.operation.contentType [ code ]; # 0..1 xml | json | ttl | none
        fhir:TestScript.setup.action.operation.destination [ integer ]; # 0..1 Server responding to the request
        fhir:TestScript.setup.action.operation.encodeRequestUrl [ boolean ]; # 0..1 Whether or not to send the request url in encoded format
        fhir:TestScript.setup.action.operation.origin [ integer ]; # 0..1 Server initiating the request
        fhir:TestScript.setup.action.operation.params [ string ]; # 0..1 Explicitly defined path parameters
        fhir:TestScript.setup.action.operation.requestHeader [ # 0..* Each operation can have one or more header elements
          fhir:TestScript.setup.action.operation.requestHeader.field [ string ]; # 1..1 HTTP header field name
          fhir:TestScript.setup.action.operation.requestHeader.value [ string ]; # 1..1 HTTP headerfield value
        ], ...;
        fhir:TestScript.setup.action.operation.requestId [ id ]; # 0..1 Fixture Id of mapped request
        fhir:TestScript.setup.action.operation.responseId [ id ]; # 0..1 Fixture Id of mapped response
        fhir:TestScript.setup.action.operation.sourceId [ id ]; # 0..1 Fixture Id of body for PUT and POST requests
        fhir:TestScript.setup.action.operation.targetId [ id ]; # 0..1 Id of fixture used for extracting the [id],  [type], and [vid] for GET requests
        fhir:TestScript.setup.action.operation.url [ string ]; # 0..1 Request URL
      ];
      fhir:TestScript.setup.action.assert [ # 0..1 The assertion to perform
        fhir:TestScript.setup.action.assert.label [ string ]; # 0..1 Tracking/logging assertion label
        fhir:TestScript.setup.action.assert.description [ string ]; # 0..1 Tracking/reporting assertion description
        fhir:TestScript.setup.action.assert.direction [ code ]; # 0..1 response | request
        fhir:TestScript.setup.action.assert.compareToSourceId [ string ]; # 0..1 Id of the source fixture to be evaluated
        fhir:TestScript.setup.action.assert.compareToSourceExpression [ string ]; # 0..1 The fluentpath expression to evaluate against the source fixture
        fhir:TestScript.setup.action.assert.compareToSourcePath [ string ]; # 0..1 XPath or JSONPath expression to evaluate against the source fixture
        fhir:TestScript.setup.action.assert.contentType [ code ]; # 0..1 xml | json | ttl | none
        fhir:TestScript.setup.action.assert.expression [ string ]; # 0..1 The fluentpath expression to be evaluated
        fhir:TestScript.setup.action.assert.headerField [ string ]; # 0..1 HTTP header field name
        fhir:TestScript.setup.action.assert.minimumId [ string ]; # 0..1 Fixture Id of minimum content resource
        fhir:TestScript.setup.action.assert.navigationLinks [ boolean ]; # 0..1 Perform validation on navigation links?
        fhir:TestScript.setup.action.assert.operator [ code ]; # 0..1 equals | notEquals | in | notIn | greaterThan | lessThan | empty | notEmpty | contains | notContains | eval
        fhir:TestScript.setup.action.assert.path [ string ]; # 0..1 XPath or JSONPath expression
        fhir:TestScript.setup.action.assert.requestMethod [ code ]; # 0..1 delete | get | options | patch | post | put
        fhir:TestScript.setup.action.assert.requestURL [ string ]; # 0..1 Request URL comparison value
        fhir:TestScript.setup.action.assert.resource [ code ]; # 0..1 Resource type
        fhir:TestScript.setup.action.assert.response [ code ]; # 0..1 okay | created | noContent | notModified | bad | forbidden | notFound | methodNotAllowed | conflict | gone | preconditionFailed | unprocessable
        fhir:TestScript.setup.action.assert.responseCode [ string ]; # 0..1 HTTP response code to test
        fhir:TestScript.setup.action.assert.rule [ # 0..1 The reference to a TestScript.rule
          fhir:TestScript.setup.action.assert.rule.ruleId [ id ]; # 1..1 Id of the TestScript.rule
          fhir:TestScript.setup.action.assert.rule.param [ # 0..* Rule parameter template
            fhir:TestScript.setup.action.assert.rule.param.name [ string ]; # 1..1 Parameter name matching external assert rule parameter
            fhir:TestScript.setup.action.assert.rule.param.value [ string ]; # 1..1 Parameter value defined either explicitly or dynamically
          ], ...;
        ];
        fhir:TestScript.setup.action.assert.ruleset [ # 0..1 The reference to a TestScript.ruleset
          fhir:TestScript.setup.action.assert.ruleset.rulesetId [ id ]; # 1..1 Id of the TestScript.ruleset
          fhir:TestScript.setup.action.assert.ruleset.rule [ # 0..* The referenced rule within the ruleset
            fhir:TestScript.setup.action.assert.ruleset.rule.ruleId [ id ]; # 1..1 Id of referenced rule within the ruleset
            fhir:TestScript.setup.action.assert.ruleset.rule.param [ # 0..* Rule parameter template
              fhir:TestScript.setup.action.assert.ruleset.rule.param.name [ string ]; # 1..1 Parameter name matching external assert ruleset rule parameter
              fhir:TestScript.setup.action.assert.ruleset.rule.param.value [ string ]; # 1..1 Parameter value defined either explicitly or dynamically
            ], ...;
          ], ...;
        ];
        fhir:TestScript.setup.action.assert.sourceId [ id ]; # 0..1 Fixture Id of source expression or headerField
        fhir:TestScript.setup.action.assert.validateProfileId [ id ]; # 0..1 Profile Id of validation profile reference
        fhir:TestScript.setup.action.assert.value [ string ]; # 0..1 The value to compare to
        fhir:TestScript.setup.action.assert.warningOnly [ boolean ]; # 0..1 Will this assert produce a warning only on error?
      ];
    ], ...;
  ];
  fhir:TestScript.test [ # 0..* A test in this script
    fhir:TestScript.test.name [ string ]; # 0..1 Tracking/logging name of this test
    fhir:TestScript.test.description [ string ]; # 0..1 Tracking/reporting short description of the test
    fhir:TestScript.test.action [ # 1..* A test operation or assert to perform
      fhir:TestScript.test.action.operation [ See TestScript.setup.action.operation ]; # 0..1 The setup operation to perform
      fhir:TestScript.test.action.assert [ See TestScript.setup.action.assert ]; # 0..1 The setup assertion to perform
    ], ...;
  ], ...;
  fhir:TestScript.teardown [ # 0..1 A series of required clean up steps
    fhir:TestScript.teardown.action [ # 1..* One or more teardown operations to perform
      fhir:TestScript.teardown.action.operation [ See TestScript.setup.action.operation ]; # 1..1 The teardown operation to perform
    ], ...;
  ];
]

Changes since DSTU2

TestScript
TestScript.title
  • Added Element
TestScript.status
  • Change value set from http://hl7.org/fhir/ValueSet/conformance-resource-status to http://hl7.org/fhir/ValueSet/publication-status
TestScript.experimental
  • Now marked as Modifier
TestScript.contact
  • Type changed from BackboneElement to ContactDetail
TestScript.description
  • Type changed from string to markdown
TestScript.useContext
  • Type changed from CodeableConcept to UsageContext
  • Remove Binding http://hl7.org/fhir/ValueSet/use-context (extensible)
TestScript.jurisdiction
  • Added Element
TestScript.purpose
  • Added Element
TestScript.copyright
  • Type changed from string to markdown
TestScript.origin
  • Added Element
TestScript.origin.index
  • Added Element
TestScript.origin.profile
  • Added Element
TestScript.destination
  • Added Element
TestScript.destination.index
  • Added Element
TestScript.destination.profile
  • Added Element
TestScript.metadata.capability.origin
  • Added Element
TestScript.metadata.capability.capabilities
  • Added Element
TestScript.fixture.autocreate
  • Default Value "false" added
TestScript.fixture.autodelete
  • Default Value "false" added
TestScript.variable.defaultValue
  • Added Element
TestScript.variable.description
  • Added Element
TestScript.variable.expression
  • Added Element
TestScript.variable.hint
  • Added Element
TestScript.rule
  • Added Element
TestScript.rule.resource
  • Added Element
TestScript.rule.param
  • Added Element
TestScript.rule.param.name
  • Added Element
TestScript.rule.param.value
  • Added Element
TestScript.ruleset
  • Added Element
TestScript.ruleset.resource
  • Added Element
TestScript.ruleset.rule
  • Added Element
TestScript.ruleset.rule.ruleId
  • Added Element
TestScript.ruleset.rule.param
  • Added Element
TestScript.ruleset.rule.param.name
  • Added Element
TestScript.ruleset.rule.param.value
  • Added Element
TestScript.setup.action.operation.destination
  • Default Value "0" removed
TestScript.setup.action.operation.origin
  • Added Element
TestScript.setup.action.operation.requestId
  • Added Element
TestScript.setup.action.assert.compareToSourceExpression
  • Added Element
TestScript.setup.action.assert.expression
  • Added Element
TestScript.setup.action.assert.requestMethod
  • Added Element
TestScript.setup.action.assert.requestURL
  • Added Element
TestScript.setup.action.assert.rule
  • Added Element
TestScript.setup.action.assert.rule.ruleId
  • Added Element
TestScript.setup.action.assert.rule.param
  • Added Element
TestScript.setup.action.assert.rule.param.name
  • Added Element
TestScript.setup.action.assert.rule.param.value
  • Added Element
TestScript.setup.action.assert.ruleset
  • Added Element
TestScript.setup.action.assert.ruleset.rulesetId
  • Added Element
TestScript.setup.action.assert.ruleset.rule
  • Added Element
TestScript.setup.action.assert.ruleset.rule.ruleId
  • Added Element
TestScript.setup.action.assert.ruleset.rule.param
  • Added Element
TestScript.setup.action.assert.ruleset.rule.param.name
  • Added Element
TestScript.setup.action.assert.ruleset.rule.param.value
  • Added Element
TestScript.teardown.action.operation
  • Min Cardinality changed from 0 to 1
TestScript.contact.name
  • deleted
TestScript.contact.telecom
  • deleted
TestScript.requirements
  • deleted
TestScript.metadata.capability.conformance
  • deleted
TestScript.multiserver
  • deleted
TestScript.setup.metadata
  • deleted
TestScript.test.metadata
  • deleted

See the Full Difference for further information

This analysis is available as XML or JSON .

See R2 <--> R3 Conversion Maps (status = 6 tests that all execute ok. 6 fail round-trip testing and 6 r3 resources are invalid (11 errors). ).

Structure

Absolute URL used Logical id for this Informal name External identifier If for testing purposes, not real usage 0..1 Name of a individual Contact details Date for this version of the TestScript 0..1 string Natural language description Σ Content intends to support these contexts Scope and Usage this Test Script is for Use and/or publishing restrictions Links Required Conformance Whether or not the tests apply to more than one FHIR server A series of required setup operations before tests are executed see metadata Capabilities that are assumed to function correctly on Which server metadata I 0..1 see metadata Capabilities that are expected to function correctly on the FHIR server being tested Test metadata capability SHALL contain required or validated or both. I 0..1
Name Flags Card. Type Description & Constraints doco
. . TestScript DomainResource Describes a set of tests
Elements defined in Ancestors: id , meta , implicitRules , language , text , contained , extension , modifierExtension
. . . url Σ 1..1 uri Logical URI to reference this TestScript test script (globally unique)
. . . identifier Σ 0..1 Identifier Additional identifier for the test script
... version Σ 0..1 string Business version of the TestScript test script
. . . name Σ 1..1 string Name for this TestScript test script (computer friendly)
. . . title Σ 0..1 string Name for this test script (human friendly)
... status ?! Σ 1..1 code draft | active | retired | unknown
ConformanceResourceStatus PublicationStatus ( Required )
. . identifier . experimental ?! Σ 0..1 Identifier boolean For testing purposes, not real usage
. . experimental . date Σ 0..1 boolean dateTime Date this was last changed
. . . publisher Σ 0..1 string Name of the publisher (Organization (organization or individual)
. . . contact Σ 0..* BackboneElement ContactDetail Contact details of for the publisher
. . . description name 0..1 markdown Natural language description of the test script
. . . useContext Σ 0..* string UsageContext Context the content is intended to contact support
. . telecom . jurisdiction Σ 0..* ContactPoint CodeableConcept Intended jurisdiction for individual or publisher test script (if applicable)
Jurisdiction ValueSet ( Extensible )
. . date . purpose Σ 0..1 markdown Why this test script is defined
... copyright 0..1 dateTime markdown Use and/or publishing restrictions
. . description . origin Σ 0..* BackboneElement An abstract server representing a client or sender in a message exchange
. . . . index 1..1 integer The index of the TestScript abstract origin server starting at 1
. . useContext . . profile 0..* 1..1 CodeableConcept Coding FHIR-Client | FHIR-SDC-FormFiller
Context of Use ValueSet TestScriptProfileOriginType ( Extensible )
. . requirements . destination 0..1 0..* string BackboneElement An abstract server representing a destination or receiver in a message exchange
. . copyright . . index 0..1 1..1 string integer The index of the abstract destination server starting at 1
. . . . profile 1..1 Coding FHIR-Server | FHIR-SDC-FormManager | FHIR-SDC-FormReceiver | FHIR-SDC-FormProcessor
TestScriptProfileDestinationType ( Extensible )
... metadata I 0..1 BackboneElement Required capability that is assumed to function correctly on the FHIR server being tested
+ TestScript metadata capability SHALL contain required or validated or both.
. . . . link 0..* BackboneElement Links to the FHIR specification
. . . . . url 1..1 uri URL to the specification
. . . . . description 0..1 string Short description
. . . . capability 1..* BackboneElement Capabilities that are assumed to function correctly on the FHIR server being tested
. . . . . required 0..1 boolean Are the capabilities required?
. . . . . validated 0..1 boolean Are the capabilities validated?
. . . . . description 0..1 string The expected capabilities of the server
. . . . destination . origin 0..1 0..* integer Which origin server these requirements apply to
. . . . link . destination 0..* 0..1 uri integer Which server these requirements apply to the FHIR specification
. . . . conformance . link 1..1 0..* Reference ( Conformance uri ) Links to the FHIR specification
. . multiserver . . . capabilities 0..1 1..1 boolean Reference ( CapabilityStatement ) Required Capability Statement
. . . fixture 0..* BackboneElement Fixture in the test script - by reference (uri)
. . . . autocreate 0..1 boolean Whether or not to implicitly create the fixture during setup
. . . . autodelete 0..1 boolean Whether or not to implicitly delete the fixture during teardown
. . . . resource 0..1 Reference ( Any ) Reference of the resource
. . . profile 0..* Reference ( Any ) Reference of the validation profile
. . . variable I 0..* BackboneElement Placeholder for evaluated elements
+ Variable cannot can only contain both one of expression, headerField and or path.
. . . . name 1..1 string Descriptive name for this variable
. . . . defaultValue 0..1 string Default, hard-coded, or user-defined value for this variable
.... description 0..1 string Natural language description of the variable
.... expression 0..1 string The fluentpath expression against the fixture body
.... headerField 0..1 string HTTP header field name for source
. . . . hint 0..1 string Hint help text for default value to enter
.... path 0..1 string XPath or JSONPath against the fixture body
. . . . sourceId 0..1 id Fixture Id of source expression or headerField within this variable
. . setup . rule 0..1 0..* BackboneElement Assert rule used within the test script
. . . metadata . resource I 1..1 Reference ( Any ) Assert rule resource reference
.... param 0..* BackboneElement Rule parameter template
..... name 1..1 string Parameter name matching external assert rule parameter
..... value 0..1 string Parameter value defined either explicitly or dynamically
... ruleset 0..* BackboneElement Assert ruleset used within the FHIR server being tested test script
Setup metadata capability SHALL contain required or validated
. . . . resource 1..1 Reference ( Any ) Assert ruleset resource reference
.... rule 1..* BackboneElement The referenced rule within the ruleset
..... ruleId 1..1 id Id of referenced rule within the ruleset
..... param 0..* BackboneElement Ruleset rule parameter template
...... name 1..1 string Parameter name matching external assert ruleset rule parameter
...... value 0..1 string Parameter value defined either explicitly or both. dynamically
... setup 0..1 BackboneElement A series of required setup operations before tests are executed
. . . . action I 1..* BackboneElement A setup operation or assert to perform
+ Setup action SHALL contain either an operation or assert but not both.
. . . . . operation I 0..1 BackboneElement The setup operation to perform
+ Setup operation SHALL contain either sourceId or targetId or params or url.
. . . . . . type 0..1 Coding The setup operation code type that will be executed
TestScriptOperationCodes TestScriptOperationCode ( Extensible )
. . . . . . resource 0..1 code Resource type
FHIRDefinedType ( Required )
. . . . . . label 0..1 string Tracking/logging operation label
. . . . . . description 0..1 string Tracking/reporting operation description
. . . . . . accept 0..1 code xml | json | ttl | none
ContentType ( Required )
. . . . . . contentType 0..1 code xml | json | ttl | none
ContentType ( Required )
. . . . . . destination 0..1 integer Server responding to perform the operation on request
. . . . . . encodeRequestUrl 0..1 boolean Whether or not to send the request url in encoded format
. . . . . . origin 0..1 integer Server initiating the request
...... params 0..1 string Explicitly defined path parameters
. . . . . . requestHeader 0..* BackboneElement Each operation can have one ore or more header elements
. . . . . . . field 1..1 string HTTP header field name
. . . . . . . value 1..1 string HTTP headerfield value
. . . . . . requestId 0..1 id Fixture Id of mapped request
...... responseId 0..1 id Fixture Id of mapped response
. . . . . . sourceId 0..1 id Fixture Id of body for PUT and POST requests
. . . . . . targetId 0..1 id Id of fixture used for extracting the [id], [type], and [vid] for GET requests
. . . . . . url 0..1 string Request URL
. . . . . assert I 0..1 BackboneElement The assertion to perform
+ Only a single assertion SHALL be present within setup action assert element.
+ Setup action assert shall SHALL contain both either compareToSourceId and compareToSourceExpression, compareToSourceId and compareToSourcePath or neither.
Only a single assertion SHALL be present within setup + Setup action assert element. response and responseCode SHALL be empty when direction equals request
. . . . . . label 0..1 string Tracking/logging assertion label
. . . . . . description 0..1 string Tracking/reporting assertion description
. . . . . . direction 0..1 code response | request
AssertionDirectionType ( Required )
. . . . . . compareToSourceId 0..1 string Id of the source fixture used to compare the "sourceId/path" evaluations be evaluated
...... compareToSourceExpression 0..1 string The fluentpath expression to evaluate against the source fixture
. . . . . . compareToSourcePath 0..1 string XPath or JSONPath expression against fixture used to compare evaluate against the "sourceId/path" evaluations to source fixture
. . . . . . contentType 0..1 code xml | json | ttl | none
ContentType ( Required )
. . . . . . expression 0..1 string The fluentpath expression to be evaluated
...... headerField 0..1 string HTTP header field name
. . . . . . minimumId 0..1 string Fixture Id of minimum content resource
. . . . . . navigationLinks 0..1 boolean Perform validation on navigation links?
. . . . . . operator 0..1 code equals | notEquals | in | notIn | greaterThan | lessThan | empty | notEmpty | contains | notContains | eval
AssertionOperatorType ( Required )
. . . . . . path 0..1 string XPath or JSONPath expression
. . . . . . requestMethod 0..1 code delete | get | options | patch | post | put
TestScriptRequestMethodCode ( Required )
...... requestURL 0..1 string Request URL comparison value
...... resource 0..1 code Resource type
FHIRDefinedType ( Required )
. . . . . . response 0..1 code okay | created | noContent | notModified | bad | forbidden | notFound | methodNotAllowed | conflict | gone | preconditionFailed | unprocessable
AssertionResponseTypes ( Required )
. . . . . . responseCode 0..1 string HTTP response code to test
. . . . . . rule 0..1 BackboneElement The reference to a TestScript.rule
....... ruleId 1..1 id Id of the TestScript.rule
....... param 0..* BackboneElement Rule parameter template
........ name 1..1 string Parameter name matching external assert rule parameter
........ value 1..1 string Parameter value defined either explicitly or dynamically
...... ruleset 0..1 BackboneElement The reference to a TestScript.ruleset
....... rulesetId 1..1 id Id of the TestScript.ruleset
....... rule 0..* BackboneElement The referenced rule within the ruleset
........ ruleId 1..1 id Id of referenced rule within the ruleset
........ param 0..* BackboneElement Rule parameter template
......... name 1..1 string Parameter name matching external assert ruleset rule parameter
......... value 1..1 string Parameter value defined either explicitly or dynamically
...... sourceId 0..1 id Fixture Id of source expression or headerField
. . . . . . validateProfileId 0..1 id Profile Id of validation profile reference
. . . . . . value 0..1 string The value to compare to
. . . . . . warningOnly 0..1 boolean Will this assert produce a warning only on error?
. . . test 0..* BackboneElement A test in this script
. . . . name 0..1 string Tracking/logging name of this test
. . . . description 0..1 string Tracking/reporting short description of the test
. . . . action I 1..* BackboneElement A test operation or assert to perform
+ Test action SHALL contain either an operation or assert but not both.
. . . . . operation I 0..1 see operation The setup operation to perform
+ Test operation SHALL contain either sourceId or targetId or params or url.
. . . . . assert I 0..1 see assert The setup assertion to perform
+ Only a single assertion SHALL be present within test action assert element.
+ Test action assert shall SHALL contain both either compareToSourceId and compareToSourceExpression, compareToSourceId and compareToSourcePath or neither.
Only a single assertion SHALL be present within test + Test action assert element. response and response and responseCode SHALL be empty when direction equals request
. . . teardown 0..1 BackboneElement A series of required clean up steps
. . . . action 1..* BackboneElement One or more teardown operations to perform
Teardown action SHALL contain an operation.
. . . . . operation I 1..1 see operation The teardown operation to perform
+ Teardown operation SHALL contain either sourceId or targetId or params or url.

doco Documentation for this format

UML Diagram ( Legend )

TestScript ( DomainResource ) An absolute URL URI that is used to identify this Test Script. test script when it is referenced in a specification, model, design or an instance. This SHALL be a URL, SHOULD be globally unique, and SHOULD be an address at which this Test Script test script is (or will be) published published. The URL SHOULD include the major version of the test script. For more information see [Technical and Business Versions](resource.html#versions) url : uri [1..1] A formal identifier that is used to identify this test script when it is represented in other formats, or referenced in a specification, model, design or an instance identifier : Identifier [0..1] The identifier that is used to identify this version of the TestScript. test script when it is referenced in a specification, model, design or instance. This is an arbitrary value managed by the TestScript test script author manually and is not expected to be globally unique. For example, it might be a timestamp (e.g. yyyymmdd) if a managed version is not available. There is also no expectation that versions can be placed in a lexicographical sequence version : string [0..1] A free text natural language name identifying the TestScript test script. This name should be usable as an identifier for the module by machine processing applications such as code generation name : string [1..1] A short, descriptive, user-friendly title for the test script title : string [0..1] The status of this test script. Enables tracking the TestScript life-cycle of the content (this element modifies the meaning of other elements) status : code [1..1] « The lifecycle status of a Value Set or Concept Map. (Strength=Required) ConformanceResourceStatus PublicationStatus ! » Identifier for the TestScript assigned for external purposes outside the context of FHIR identifier : Identifier [0..1] This TestScript was A boolean value to indicate that this test script is authored for testing purposes (or education/evaluation/marketing), and is not intended to be used for genuine usage (this element modifies the meaning of other elements) experimental : boolean [0..1] The name of the individual or organization that published the Test Script publisher : string [0..1] The date this version of (and optionally time) when the test tcript script was published. The date must change if and when the business version changes, if it does, changes and it must change if the status code changes. In addition, it should change when the substantive content of the test cases change script changes date : dateTime [0..1] The name of the individual or organization that published the test script publisher : string [0..1] Contact details to assist a user in finding and communicating with the publisher contact : ContactDetail [0..*] A free text natural language description of the TestScript and its use test script from a consumer's perspective description : string markdown [0..1] The content was developed with a focus and intent of supporting the contexts that are listed. These terms may be used to assist with indexing and searching of Test Scripts for appropriate test script instances useContext : UsageContext [0..*] A legal or geographic region in which the test script is intended to be used jurisdiction : CodeableConcept [0..*] « Indicates the countries, regions, disciplines Countries and other aspects of use regions within which this artifact is targeted for use. use (Strength=Extensible) Context of Use Jurisdiction ValueSet + » Explains Explaination of why this Test Script test script is needed and why it's it has been constrained designed as it has requirements purpose : string markdown [0..1] A copyright statement relating to the Test Script test script and/or its contents. Copyright statements are generally legal restrictions on the use and publishing of the details of the constraints and mappings test script copyright : string [0..1] If the tests apply to more than one FHIR server (e.g. cross-server interoperability tests) then multiserver=true. Defaults to false if value is unspecified multiserver : boolean markdown [0..1] Reference to the profile to be used for validation profile : Reference [0..*] « Any » Contact Origin Abstract name given to an origin server in this test script. The name is provided as a number starting at 1 index : integer [1..1] The type of an individual to contact regarding origin profile the Test Script test system supports name profile : string Coding [0..1] [1..1] The type of origin profile the test system supports. (Strength=Extensible) TestScriptProfileOriginType + Destination Contact details for individual (if Abstract name given to a destination server in this test script. The name was provided) or is provided as a number starting at 1 index : integer [1..1] The type of destination profile the publisher test system supports telecom profile : ContactPoint Coding [0..*] [1..1] The type of destination profile the test system supports. (Strength=Extensible) TestScriptProfileDestinationT... + Metadata Link URL to a particular requirement or feature within the FHIR specification url : uri [1..1] Short description of the link description : string [0..1] Capability Whether or not the test execution will require the given capabilities of the server in order for this test script to execute required : boolean [0..1] Whether or not the test execution will validate the given capabilities of the server in order for this test script to execute validated : boolean [0..1] Description of the capabilities that this test script is requiring the server to support description : string [0..1] Which origin server these requirements apply to origin : integer [0..*] Which server these requirements apply to destination : integer [0..1] Links to the FHIR specification that describes this interaction and the resources involved in more detail link : uri [0..*] Minimum conformance capabilities required of server for test script to execute successfully. If server does not meet at a minimum the reference conformance definition, referenced capability statement, then all tests in this script are skipped conformance capabilities : Reference [1..1] « Conformance CapabilityStatement » Fixture Whether or not to implicitly create the fixture during setup. If true, the fixture is automatically created on each server being tested during setup, therefore no create operation is required for this fixture in the TestScript.setup section autocreate : boolean [0..1] Whether or not to implicitly delete the fixture during teardown teardown. If true, the fixture is automatically deleted on each server being tested during teardown, therefore no delete operation is required for this fixture in the TestScript.teardown section autodelete : boolean [0..1] Reference to the resource (containing the contents of the resource needed for operations) resource : Reference [0..1] « Any » Variable Descriptive name for this variable name : string [1..1] A default, hard-coded, or user-defined value for this variable defaultValue : string [0..1] A free text natural language description of the variable and its purpose description : string [0..1] The fluentpath expression to evaluate against the fixture body. When variables are defined, only one of either expression, headerField or path must be specified expression : string [0..1] Will be used to grab the HTTP header field value from the headers that sourceId is pointing to headerField : string [0..1] Displayable text string with hint help information to the user when entering a default value hint : string [0..1] XPath or JSONPath to evaluate against the fixture body. When variables are defined, only one of either expression, headerField or path must be specified or path, but not both path : string [0..1] Fixture to evaluate the XPath/JSONPath expression or the headerField against within this variable sourceId : id [0..1] Rule Reference to the resource (containing the contents of the rule needed for assertions) resource : Reference [1..1] Any RuleParam Descriptive name for this parameter that matches the external assert rule parameter name name : string [1..1] The explicit or dynamic value for the parameter that will be passed on to the external rule template value : string [0..1] Ruleset Reference to the resource (containing the contents of the ruleset needed for assertions) resource : Reference [1..1] Any RulesetRule Id of the referenced rule within the external ruleset template ruleId : id [1..1] RulesetRuleParam Descriptive name for this parameter that matches the external assert ruleset rule parameter name name : string [1..1] The value for the parameter that will be passed on to the external ruleset rule template value : string [0..1] Setup Action SetupAction Operation Server interaction or operation type type : Coding [0..1] « The allowable operation code types. (Strength=Extensible) TestScriptOperationCodes TestScriptOperationCode + » The type of the resource. See http://hl7-fhir.github.io/resourcelist.html http://hl7.org/fhir/STU3/resourcelist.html resource : code [0..1] « Either a resource or a data type. (Strength=Required) FHIRDefinedType ! » The label would be used for tracking/logging purposes by test engines label : string [0..1] The description would be used by test engines for tracking and reporting purposes description : string [0..1] The content-type or mime-type to use for RESTful operation in the 'Accept' header accept : code [0..1] « The content or mime type. (Strength=Required) ContentType ! » The content-type or mime-type to use for RESTful operation in the 'Content-Type' header contentType : code [0..1] « The content or mime type. (Strength=Required) ContentType ! » Which The server to perform where the operation on request message is destined for. Must be one of the server numbers listed in TestScript.destination section destination : integer [0..1] Whether or not to implicitly send the request url in encoded format. The default is true to match the standard RESTful client behavior. Set to false when communicating with a server that does not support encoded url paths encodeRequestUrl : boolean [0..1] The server where the request message originates from. Must be one of the server numbers listed in TestScript.origin section origin : integer [0..1] Path plus parameters after [type]. Used to set parts of the request URL explicitly params : string [0..1] The fixture id (maybe new) to map to the request requestId : id [0..1] The fixture id (maybe new) to map to the response responseId : id [0..1] The id of the fixture used as the body of a PUT or POST request sourceId : id [0..1] Id of fixture used for extracting the [id], [type], and [vid] for GET requests targetId : id [0..1] Complete request URL url : string [0..1] RequestHeader The HTTP header field e.g. "Accept" field : string [1..1] The value of the header e.g. "application/xml" "application/fhir+xml" value : string [1..1] Assert The label would be used for tracking/logging purposes by test engines label : string [0..1] The description would be used by test engines for tracking and reporting purposes description : string [0..1] The direction to use for the assertion direction : code [0..1] « The type of direction to use for assertion. (Strength=Required) AssertionDirectionType ! » Id of the source fixture used as the contents to compare be evaluated by either the "source/expression" or "sourceId/path" evaluations to definition compareToSourceId : string [0..1] The fluentpath expression to evaluate against the source fixture. When compareToSourceId is defined, either compareToSourceExpression or compareToSourcePath must be defined, but not both compareToSourceExpression : string [0..1] XPath or JSONPath expression against fixture used to compare evaluate against the "sourceId/path" evaluations to source fixture. When compareToSourceId is defined, either compareToSourceExpression or compareToSourcePath must be defined, but not both compareToSourcePath : string [0..1] The content-type or mime-type to use for RESTful operation in the 'Content-Type' header contentType : code [0..1] « The content or mime type. (Strength=Required) ContentType ! » The fluentpath expression to be evaluated against the request or response message contents - HTTP headers and payload expression : string [0..1] The HTTP header field name e.g. 'Location' headerField : string [0..1] The ID of a fixture. Asserts that the response contains at a minimumId minimum the fixture specified by minimumId minimumId : string [0..1] Whether or not the test execution performs validation on the bundle navigation links navigationLinks : boolean [0..1] The operator type defines the conditional behavior of the assert. If not defined, the default is equals operator : code [0..1] « The type of operator to use for assertion. (Strength=Required) AssertionOperatorType ! » The XPath or JSONPath expression to be evaluated against the fixture representing the response received from server path : string [0..1] The request method or HTTP operation code to compare against that used by the client system under test requestMethod : code [0..1] The allowable request method or HTTP operation codes. (Strength=Required) TestScriptRequestMethodCode ! The value to use in a comparison against the request URL path string requestURL : string [0..1] The type of the resource. See http://hl7-fhir.github.io/resourcelist.html http://hl7.org/fhir/STU3/resourcelist.html resource : code [0..1] « Either a resource or a data type. (Strength=Required) FHIRDefinedType ! » okay | created | noContent | notModified | bad | forbidden | notFound | methodNotAllowed | conflict | gone | preconditionFailed | unprocessable response : code [0..1] « The type of response code to use for assertion. (Strength=Required) AssertionResponseTypes ! » The value of the HTTP response code to be tested responseCode : string [0..1] Fixture to evaluate the XPath/JSONPath expression or the headerField against sourceId : id [0..1] The ID of the Profile to validate against validateProfileId : id [0..1] The value to compare to value : string [0..1] Whether or not the test execution will produce a warning only on error for this assert warningOnly : boolean [0..1] ActionAssertRule The TestScript.rule id value this assert will evaluate ruleId : id [1..1] ActionAssertRuleParam Descriptive name for this parameter that matches the external assert rule parameter name name : string [1..1] The value for the parameter that will be passed on to the external rule template value : string [1..1] ActionAssertRuleset The TestScript.ruleset id value this assert will evaluate rulesetId : id [1..1] ActionAssertRulesetRule Id of the referenced rule within the external ruleset template ruleId : id [1..1] Param Descriptive name for this parameter that matches the external assert ruleset rule parameter name name : string [1..1] The value for the parameter that will be passed on to the external ruleset rule template value : string [1..1] Test The name of this test used for tracking/logging purposes by test engines name : string [0..1] A short description of the test used by test engines for tracking and reporting purposes description : string [0..1] Action TestAction Teardown Action TeardownAction Contacts to assist a user An abstract server used in operations within this test script in finding and communicating with the publisher origin element contact origin [0..*] An abstract server used in operations within this test script in the destination element destination [0..*] A link to the FHIR specification that this test is covering link [0..*] Capabilities that must exist and are assumed to function correctly on the FHIR server being tested capability [1..*] The required capability must exist and are assumed to function correctly on the FHIR server being tested metadata [0..1] Fixture in the test script - by reference (uri). All fixtures are required for the test script to execute fixture [0..*] Variable is set based either on element value in response body or on header field value in the response headers variable [0..*] Capabilities that must exist and are assumed Each rule template can take one or more parameters for rule evaluation param [0..*] Assert rule to function correctly on be used in one or more asserts within the FHIR server being tested test script metadata rule [0..1] [0..*] Each rule template can take one or more parameters for rule evaluation param [0..*] The referenced rule within the external ruleset template rule [1..*] Contains one or more rules. Offers a way to group rules so assertions could reference the group of rules and have them all applied ruleset [0..*] Header elements would be used to set HTTP headers requestHeader [0..*] The operation to perform operation [0..1] Each rule template can take one or more parameters for rule evaluation param [0..*] The TestScript.rule this assert will evaluate rule [0..1] Each rule template can take one or more parameters for rule evaluation param [0..*] The referenced rule within the external ruleset template rule [0..*] The TestScript.ruleset this assert will evaluate ruleset [0..1] Evaluates the results of previous operations to determine if the server under test behaves appropriately assert [0..1] Action would contain either an operation or an assertion action [1..*] A series of required setup operations before tests are executed setup [0..1] Capabilities that must exist and are assumed to function correctly on the FHIR server being tested metadata [0..1] An operation would involve a REST request to a server operation [0..1] Evaluates the results of previous operations to determine if the server under test behaves appropriately assert [0..1] Action would contain either an operation or an assertion action [1..*] A test in this script test [0..*] An operation would involve a REST request to a server operation [0..1] [1..1] The teardown action will only contain an operation action [1..*] A series of operations required to clean up after the all the tests are executed (successfully or otherwise) teardown [0..1]

XML Template

<

<TestScript xmlns="http://hl7.org/fhir"> doco

 <!-- from Resource: id, meta, implicitRules, and language -->
 <!-- from DomainResource: text, contained, extension, and modifierExtension -->
 <
 <
 <
 <
 <</identifier>
 <
 <
 <
  <
  <</telecom>
 </contact>
 <
 <
 <</useContext>
 <
 <
 <
  <
   <
   <

 <url value="[uri]"/><!-- 1..1 Logical URI to reference this test script (globally unique) -->
 <identifier><!-- 0..1 Identifier Additional identifier for the test script --></identifier>
 <version value="[string]"/><!-- 0..1 Business version of the test script -->
 <name value="[string]"/><!-- 1..1 Name for this test script (computer friendly) -->
 <title value="[string]"/><!-- 0..1 Name for this test script (human friendly) -->
 <status value="[code]"/><!-- 1..1 draft | active | retired | unknown -->
 <experimental value="[boolean]"/><!-- 0..1 For testing purposes, not real usage -->
 <date value="[dateTime]"/><!-- 0..1 Date this was last changed -->
 <publisher value="[string]"/><!-- 0..1 Name of the publisher (organization or individual) -->
 <contact><!-- 0..* ContactDetail Contact details for the publisher --></contact>
 <description value="[markdown]"/><!-- 0..1 Natural language description of the test script -->
 <useContext><!-- 0..* UsageContext Context the content is intended to support --></useContext>
 <jurisdiction><!-- 0..* CodeableConcept Intended jurisdiction for test script (if applicable) --></jurisdiction>
 <purpose value="[markdown]"/><!-- 0..1 Why this test script is defined -->
 <copyright value="[markdown]"/><!-- 0..1 Use and/or publishing restrictions -->
 <origin>  <!-- 0..* An abstract server representing a client or sender in a message exchange -->
  <index value="[integer]"/><!-- 1..1 The index of the abstract origin server starting at 1 -->
  <profile><!-- 1..1 Coding FHIR-Client | FHIR-SDC-FormFiller --></profile>
 </origin>
 <destination>  <!-- 0..* An abstract server representing a destination or receiver in a message exchange -->
  <index value="[integer]"/><!-- 1..1 The index of the abstract destination server starting at 1 -->
  <profile><!-- 1..1 Coding FHIR-Server | FHIR-SDC-FormManager | FHIR-SDC-FormReceiver | FHIR-SDC-FormProcessor --></profile>
 </destination>
 <metadata>  <!-- 0..1 Required capability that is assumed to function correctly on the FHIR server being tested -->
  <link>  <!-- 0..* Links to the FHIR specification -->
   <url value="[uri]"/><!-- 1..1 URL to the specification -->
   <description value="[string]"/><!-- 0..1 Short description -->

  </link>
  <
   <
   <
   <
   <
   <
   <</conformance>

  <capability>  <!-- 1..* Capabilities  that are assumed to function correctly on the FHIR server being tested -->
   <required value="[boolean]"/><!-- 0..1 Are the capabilities required? -->
   <validated value="[boolean]"/><!-- 0..1 Are the capabilities validated? -->
   <description value="[string]"/><!-- 0..1 The expected capabilities of the server -->
   <origin value="[integer]"/><!-- 0..* Which origin server these requirements apply to -->
   <destination value="[integer]"/><!-- 0..1 Which server these requirements apply to -->
   <link value="[uri]"/><!-- 0..* Links to the FHIR specification -->
   <capabilities><!-- 1..1 Reference(CapabilityStatement) Required Capability Statement --></capabilities>

  </capability>
 </metadata>
 <
 <
  <
  <
  <</resource>

 <fixture>  <!-- 0..* Fixture in the test script - by reference (uri) -->
  <autocreate value="[boolean]"/><!-- 0..1 Whether or not to implicitly create the fixture during setup -->
  <autodelete value="[boolean]"/><!-- 0..1 Whether or not to implicitly delete the fixture during teardown -->
  <resource><!-- 0..1 Reference(Any) Reference of the resource --></resource>

 </fixture>
 <</profile>
 <
  <
  <
  <
  <

 <profile><!-- 0..* Reference(Any) Reference of the validation profile --></profile>
 <variable>  <!-- 0..* Placeholder for evaluated elements -->
  <name value="[string]"/><!-- 1..1 Descriptive name for this variable -->
  <defaultValue value="[string]"/><!-- 0..1 Default, hard-coded, or user-defined value for this variable -->
  <description value="[string]"/><!-- 0..1 Natural language description of the variable -->
  <expression value="[string]"/><!-- 0..1 The fluentpath expression against the fixture body -->
  <headerField value="[string]"/><!-- 0..1 HTTP header field name for source -->
  <hint value="[string]"/><!-- 0..1 Hint help text for default value to enter -->
  <path value="[string]"/><!-- 0..1 XPath or JSONPath against the fixture body -->
  <sourceId value="[id]"/><!-- 0..1 Fixture Id of source expression or headerField within this variable -->

 </variable>
 <
  <</metadata>
  <
   <
    <</type>
    <
    <
    <
    <
    <
    <
    <
    <
    <
     <
     <

 <rule>  <!-- 0..* Assert rule used within the test script -->
  <resource><!-- 1..1 Reference(Any) Assert rule resource reference --></resource>
  <param>  <!-- 0..* Rule parameter template -->
   <name value="[string]"/><!-- 1..1 Parameter name matching external assert rule parameter -->
   <value value="[string]"/><!-- 0..1 Parameter value defined either explicitly or dynamically -->
  </param>
 </rule>
 <ruleset>  <!-- 0..* Assert ruleset used within the test script -->
  <resource><!-- 1..1 Reference(Any) Assert ruleset resource reference --></resource>
  <rule>  <!-- 1..* The referenced rule within the ruleset -->
   <ruleId value="[id]"/><!-- 1..1 Id of referenced rule within the ruleset -->
   <param>  <!-- 0..* Ruleset rule parameter template -->
    <name value="[string]"/><!-- 1..1 Parameter name matching external assert ruleset rule parameter -->
    <value value="[string]"/><!-- 0..1 Parameter value defined either explicitly or dynamically -->
   </param>
  </rule>
 </ruleset>
 <setup>  <!-- 0..1 A series of required setup operations before tests are executed -->
  <action>  <!-- 1..* A setup operation or assert to perform -->
   <operation>  <!-- 0..1 The setup operation to perform -->
    <type><!-- 0..1 Coding The operation code type that will be executed --></type>
    <resource value="[code]"/><!-- 0..1 Resource type -->
    <label value="[string]"/><!-- 0..1 Tracking/logging operation label -->
    <description value="[string]"/><!-- 0..1 Tracking/reporting operation description -->
    <accept value="[code]"/><!-- 0..1 xml | json | ttl | none -->
    <contentType value="[code]"/><!-- 0..1 xml | json | ttl | none -->
    <destination value="[integer]"/><!-- 0..1 Server responding to the request -->
    <encodeRequestUrl value="[boolean]"/><!-- 0..1 Whether or not to send the request url in encoded format -->
    <origin value="[integer]"/><!-- 0..1 Server initiating the request -->
    <params value="[string]"/><!-- 0..1 Explicitly defined path parameters -->
    <requestHeader>  <!-- 0..* Each operation can have one or more header elements -->
     <field value="[string]"/><!-- 1..1 HTTP header field name -->
     <value value="[string]"/><!-- 1..1 HTTP headerfield value -->

    </requestHeader>
    <
    <
    <
    <

    <requestId value="[id]"/><!-- 0..1 Fixture Id of mapped request -->
    <responseId value="[id]"/><!-- 0..1 Fixture Id of mapped response -->
    <sourceId value="[id]"/><!-- 0..1 Fixture Id of body for PUT and POST requests -->
    <targetId value="[id]"/><!-- 0..1 Id of fixture used for extracting the [id],  [type], and [vid] for GET requests -->
    <url value="[string]"/><!-- 0..1 Request URL -->

   </operation>
   <
    <
    <
    <
    <
    <
    <
    <
    <
    <
    <
    <
    <
    <
    <
    <
    <
    <
    <

   <assert>  <!-- 0..1 The assertion to perform -->
    <label value="[string]"/><!-- 0..1 Tracking/logging assertion label -->
    <description value="[string]"/><!-- 0..1 Tracking/reporting assertion description -->
    <direction value="[code]"/><!-- 0..1 response | request -->
    <compareToSourceId value="[string]"/><!-- 0..1 Id of the source fixture to be evaluated -->
    <compareToSourceExpression value="[string]"/><!-- 0..1 The fluentpath expression to evaluate against the source fixture -->
    <compareToSourcePath value="[string]"/><!-- 0..1 XPath or JSONPath expression to evaluate against the source fixture -->
    <contentType value="[code]"/><!-- 0..1 xml | json | ttl | none -->
    <expression value="[string]"/><!-- 0..1 The fluentpath expression to be evaluated -->
    <headerField value="[string]"/><!-- 0..1 HTTP header field name -->
    <minimumId value="[string]"/><!-- 0..1 Fixture Id of minimum content resource -->
    <navigationLinks value="[boolean]"/><!-- 0..1 Perform validation on navigation links? -->
    <operator value="[code]"/><!-- 0..1 equals | notEquals | in | notIn | greaterThan | lessThan | empty | notEmpty | contains | notContains | eval -->
    <path value="[string]"/><!-- 0..1 XPath or JSONPath expression -->
    <requestMethod value="[code]"/><!-- 0..1 delete | get | options | patch | post | put -->
    <requestURL value="[string]"/><!-- 0..1 Request URL comparison value -->
    <resource value="[code]"/><!-- 0..1 Resource type -->
    <response value="[code]"/><!-- 0..1 okay | created | noContent | notModified | bad | forbidden | notFound | methodNotAllowed | conflict | gone | preconditionFailed | unprocessable -->
    <responseCode value="[string]"/><!-- 0..1 HTTP response code to test -->
    <rule>  <!-- 0..1 The reference to a TestScript.rule -->
     <ruleId value="[id]"/><!-- 1..1 Id of the TestScript.rule -->
     <param>  <!-- 0..* Rule parameter template -->
      <name value="[string]"/><!-- 1..1 Parameter name matching external assert rule parameter -->
      <value value="[string]"/><!-- 1..1 Parameter value defined either explicitly or dynamically -->
     </param>
    </rule>
    <ruleset>  <!-- 0..1 The reference to a TestScript.ruleset -->
     <rulesetId value="[id]"/><!-- 1..1 Id of the TestScript.ruleset -->
     <rule>  <!-- 0..* The referenced rule within the ruleset -->
      <ruleId value="[id]"/><!-- 1..1 Id of referenced rule within the ruleset -->
      <param>  <!-- 0..* Rule parameter template -->
       <name value="[string]"/><!-- 1..1 Parameter name matching external assert ruleset rule parameter -->
       <value value="[string]"/><!-- 1..1 Parameter value defined either explicitly or dynamically -->
      </param>
     </rule>
    </ruleset>
    <sourceId value="[id]"/><!-- 0..1 Fixture Id of source expression or headerField -->
    <validateProfileId value="[id]"/><!-- 0..1 Profile Id of validation profile reference -->
    <value value="[string]"/><!-- 0..1 The value to compare to -->
    <warningOnly value="[boolean]"/><!-- 0..1 Will this assert produce a warning only on error? -->

   </assert>
  </action>
 </setup>
 <
  <
  <
  <</metadata>
  <
   <</operation>
   <</assert>

 <test>  <!-- 0..* A test in this script -->
  <name value="[string]"/><!-- 0..1 Tracking/logging name of this test -->
  <description value="[string]"/><!-- 0..1 Tracking/reporting short description of the test -->
  <action>  <!-- 1..* A test operation or assert to perform -->
   <operation><!-- 0..1 Content as for TestScript.setup.action.operation The setup operation to perform --></operation>
   <assert><!-- 0..1 Content as for TestScript.setup.action.assert The setup assertion to perform --></assert>

  </action>
 </test>
 <
  <
   <</operation>

 <teardown>  <!-- 0..1 A series of required clean up steps -->
  <action>  <!-- 1..* One or more teardown operations to perform -->
   <operation><!-- 1..1 Content as for TestScript.setup.action.operation The teardown operation to perform --></operation>

  </action>
 </teardown>
</TestScript>

JSON Template

{
  "resourceType" : "",

{doco
  "resourceType" : "TestScript",

  // from Resource: id, meta, implicitRules, and language
  // from DomainResource: text, contained, extension, and modifierExtension
  "
  "
  "
  "
  "
  "
  "
  "
    "
    "

  "url" : "<uri>", // R!  Logical URI to reference this test script (globally unique)
  "identifier" : { Identifier }, // Additional identifier for the test script
  "version" : "<string>", // Business version of the test script
  "name" : "<string>", // R!  Name for this test script (computer friendly)
  "title" : "<string>", // Name for this test script (human friendly)
  "status" : "<code>", // R!  draft | active | retired | unknown
  "experimental" : <boolean>, // For testing purposes, not real usage
  "date" : "<dateTime>", // Date this was last changed
  "publisher" : "<string>", // Name of the publisher (organization or individual)
  "contact" : [{ ContactDetail }], // Contact details for the publisher
  "description" : "<markdown>", // Natural language description of the test script
  "useContext" : [{ UsageContext }], // Context the content is intended to support
  "jurisdiction" : [{ CodeableConcept }], // Intended jurisdiction for test script (if applicable)
  "purpose" : "<markdown>", // Why this test script is defined
  "copyright" : "<markdown>", // Use and/or publishing restrictions
  "origin" : [{ // An abstract server representing a client or sender in a message exchange
    "index" : <integer>, // R!  The index of the abstract origin server starting at 1
    "profile" : { Coding } // R!  FHIR-Client | FHIR-SDC-FormFiller

  }],
  "
  "
  "
  "
  "
  "
    "
      "
      "

  "destination" : [{ // An abstract server representing a destination or receiver in a message exchange
    "index" : <integer>, // R!  The index of the abstract destination server starting at 1
    "profile" : { Coding } // R!  FHIR-Server | FHIR-SDC-FormManager | FHIR-SDC-FormReceiver | FHIR-SDC-FormProcessor
  }],
  "metadata" : { // Required capability that is assumed to function correctly on the FHIR server being tested
    "link" : [{ // Links to the FHIR specification
      "url" : "<uri>", // R!  URL to the specification
      "description" : "<string>" // Short description

    }],
    "
      "
      "
      "
      "
      "
      "

    "capability" : [{ // R!  Capabilities  that are assumed to function correctly on the FHIR server being tested
      "required" : <boolean>, // Are the capabilities required?
      "validated" : <boolean>, // Are the capabilities validated?
      "description" : "<string>", // The expected capabilities of the server
      "origin" : [<integer>], // Which origin server these requirements apply to
      "destination" : <integer>, // Which server these requirements apply to
      "link" : ["<uri>"], // Links to the FHIR specification
      "capabilities" : { Reference(CapabilityStatement) } // R!  Required Capability Statement

    }]
  },
  "
  "
    "
    "
    "

  "fixture" : [{ // Fixture in the test script - by reference (uri)
    "autocreate" : <boolean>, // Whether or not to implicitly create the fixture during setup
    "autodelete" : <boolean>, // Whether or not to implicitly delete the fixture during teardown
    "resource" : { Reference(Any) } // Reference of the resource

  }],
  "
  "
    "
    "
    "
    "

  "profile" : [{ Reference(Any) }], // Reference of the validation profile
  "variable" : [{ // Placeholder for evaluated elements
    "name" : "<string>", // R!  Descriptive name for this variable
    "defaultValue" : "<string>", // Default, hard-coded, or user-defined value for this variable
    "description" : "<string>", // Natural language description of the variable
    "expression" : "<string>", // The fluentpath expression against the fixture body
    "headerField" : "<string>", // HTTP header field name for source
    "hint" : "<string>", // Hint help text for default value to enter
    "path" : "<string>", // XPath or JSONPath against the fixture body
    "sourceId" : "<id>" // Fixture Id of source expression or headerField within this variable

  }],
  "
    "
    "
      "
        "
        "
        "
        "
        "
        "
        "
        "
        "
        "
          "
          "

  "rule" : [{ // Assert rule used within the test script
    "resource" : { Reference(Any) }, // R!  Assert rule resource reference
    "param" : [{ // Rule parameter template
      "name" : "<string>", // R!  Parameter name matching external assert rule parameter
      "value" : "<string>" // Parameter value defined either explicitly or dynamically
    }]
  }],
  "ruleset" : [{ // Assert ruleset used within the test script
    "resource" : { Reference(Any) }, // R!  Assert ruleset resource reference
    "rule" : [{ // R!  The referenced rule within the ruleset
      "ruleId" : "<id>", // R!  Id of referenced rule within the ruleset
      "param" : [{ // Ruleset rule parameter template
        "name" : "<string>", // R!  Parameter name matching external assert ruleset rule parameter
        "value" : "<string>" // Parameter value defined either explicitly or dynamically
      }]
    }]
  }],
  "setup" : { // A series of required setup operations before tests are executed
    "action" : [{ // R!  A setup operation or assert to perform
      "operation" : { // The setup operation to perform
        "type" : { Coding }, // The operation code type that will be executed
        "resource" : "<code>", // Resource type
        "label" : "<string>", // Tracking/logging operation label
        "description" : "<string>", // Tracking/reporting operation description
        "accept" : "<code>", // xml | json | ttl | none
        "contentType" : "<code>", // xml | json | ttl | none
        "destination" : <integer>, // Server responding to the request
        "encodeRequestUrl" : <boolean>, // Whether or not to send the request url in encoded format
        "origin" : <integer>, // Server initiating the request
        "params" : "<string>", // Explicitly defined path parameters
        "requestHeader" : [{ // Each operation can have one or more header elements
          "field" : "<string>", // R!  HTTP header field name
          "value" : "<string>" // R!  HTTP headerfield value

        }],
        "
        "
        "
        "

        "requestId" : "<id>", // Fixture Id of mapped request
        "responseId" : "<id>", // Fixture Id of mapped response
        "sourceId" : "<id>", // Fixture Id of body for PUT and POST requests
        "targetId" : "<id>", // Id of fixture used for extracting the [id],  [type], and [vid] for GET requests
        "url" : "<string>" // Request URL

      },
      "
        "
        "
        "
        "
        "
        "
        "
        "
        "
        "
        "
        "
        "
        "
        "
        "
        "
        "

      "assert" : { // The assertion to perform
        "label" : "<string>", // Tracking/logging assertion label
        "description" : "<string>", // Tracking/reporting assertion description
        "direction" : "<code>", // response | request
        "compareToSourceId" : "<string>", // Id of the source fixture to be evaluated
        "compareToSourceExpression" : "<string>", // The fluentpath expression to evaluate against the source fixture
        "compareToSourcePath" : "<string>", // XPath or JSONPath expression to evaluate against the source fixture
        "contentType" : "<code>", // xml | json | ttl | none
        "expression" : "<string>", // The fluentpath expression to be evaluated
        "headerField" : "<string>", // HTTP header field name
        "minimumId" : "<string>", // Fixture Id of minimum content resource
        "navigationLinks" : <boolean>, // Perform validation on navigation links?
        "operator" : "<code>", // equals | notEquals | in | notIn | greaterThan | lessThan | empty | notEmpty | contains | notContains | eval
        "path" : "<string>", // XPath or JSONPath expression
        "requestMethod" : "<code>", // delete | get | options | patch | post | put
        "requestURL" : "<string>", // Request URL comparison value
        "resource" : "<code>", // Resource type
        "response" : "<code>", // okay | created | noContent | notModified | bad | forbidden | notFound | methodNotAllowed | conflict | gone | preconditionFailed | unprocessable
        "responseCode" : "<string>", // HTTP response code to test
        "rule" : { // The reference to a TestScript.rule
          "ruleId" : "<id>", // R!  Id of the TestScript.rule
          "param" : [{ // Rule parameter template
            "name" : "<string>", // R!  Parameter name matching external assert rule parameter
            "value" : "<string>" // R!  Parameter value defined either explicitly or dynamically
          }]
        },
        "ruleset" : { // The reference to a TestScript.ruleset
          "rulesetId" : "<id>", // R!  Id of the TestScript.ruleset
          "rule" : [{ // The referenced rule within the ruleset
            "ruleId" : "<id>", // R!  Id of referenced rule within the ruleset
            "param" : [{ // Rule parameter template
              "name" : "<string>", // R!  Parameter name matching external assert ruleset rule parameter
              "value" : "<string>" // R!  Parameter value defined either explicitly or dynamically
            }]
          }]
        },
        "sourceId" : "<id>", // Fixture Id of source expression or headerField
        "validateProfileId" : "<id>", // Profile Id of validation profile reference
        "value" : "<string>", // The value to compare to
        "warningOnly" : <boolean> // Will this assert produce a warning only on error?

      }
    }]
  },
  "
    "
    "
    "
    "
      "
      "

  "test" : [{ // A test in this script
    "name" : "<string>", // Tracking/logging name of this test
    "description" : "<string>", // Tracking/reporting short description of the test
    "action" : [{ // R!  A test operation or assert to perform
      "operation" : { Content as for TestScript.setup.action.operation }, // The setup operation to perform
      "assert" : { Content as for TestScript.setup.action.assert } // The setup assertion to perform

    }]
  }],
  "
    "
      "

  "teardown" : { // A series of required clean up steps
    "action" : [{ // R!  One or more teardown operations to perform
      "operation" : { Content as for TestScript.setup.action.operation } // R!  The teardown operation to perform

    }]
  }
}

Turtle Template


@prefix fhir: <http://hl7.org/fhir/> .doco


[ a fhir:TestScript;
  fhir:nodeRole fhir:treeRoot; # if this is the parser root

  # from Resource: .id, .meta, .implicitRules, and .language
  # from DomainResource: .text, .contained, .extension, and .modifierExtension
  fhir:TestScript.url [ uri ]; # 1..1 Logical URI to reference this test script (globally unique)
  fhir:TestScript.identifier [ Identifier ]; # 0..1 Additional identifier for the test script
  fhir:TestScript.version [ string ]; # 0..1 Business version of the test script
  fhir:TestScript.name [ string ]; # 1..1 Name for this test script (computer friendly)
  fhir:TestScript.title [ string ]; # 0..1 Name for this test script (human friendly)
  fhir:TestScript.status [ code ]; # 1..1 draft | active | retired | unknown
  fhir:TestScript.experimental [ boolean ]; # 0..1 For testing purposes, not real usage
  fhir:TestScript.date [ dateTime ]; # 0..1 Date this was last changed
  fhir:TestScript.publisher [ string ]; # 0..1 Name of the publisher (organization or individual)
  fhir:TestScript.contact [ ContactDetail ], ... ; # 0..* Contact details for the publisher
  fhir:TestScript.description [ markdown ]; # 0..1 Natural language description of the test script
  fhir:TestScript.useContext [ UsageContext ], ... ; # 0..* Context the content is intended to support
  fhir:TestScript.jurisdiction [ CodeableConcept ], ... ; # 0..* Intended jurisdiction for test script (if applicable)
  fhir:TestScript.purpose [ markdown ]; # 0..1 Why this test script is defined
  fhir:TestScript.copyright [ markdown ]; # 0..1 Use and/or publishing restrictions
  fhir:TestScript.origin [ # 0..* An abstract server representing a client or sender in a message exchange
    fhir:TestScript.origin.index [ integer ]; # 1..1 The index of the abstract origin server starting at 1
    fhir:TestScript.origin.profile [ Coding ]; # 1..1 FHIR-Client | FHIR-SDC-FormFiller
  ], ...;
  fhir:TestScript.destination [ # 0..* An abstract server representing a destination or receiver in a message exchange
    fhir:TestScript.destination.index [ integer ]; # 1..1 The index of the abstract destination server starting at 1
    fhir:TestScript.destination.profile [ Coding ]; # 1..1 FHIR-Server | FHIR-SDC-FormManager | FHIR-SDC-FormReceiver | FHIR-SDC-FormProcessor
  ], ...;
  fhir:TestScript.metadata [ # 0..1 Required capability that is assumed to function correctly on the FHIR server being tested
    fhir:TestScript.metadata.link [ # 0..* Links to the FHIR specification
      fhir:TestScript.metadata.link.url [ uri ]; # 1..1 URL to the specification
      fhir:TestScript.metadata.link.description [ string ]; # 0..1 Short description
    ], ...;
    fhir:TestScript.metadata.capability [ # 1..* Capabilities  that are assumed to function correctly on the FHIR server being tested
      fhir:TestScript.metadata.capability.required [ boolean ]; # 0..1 Are the capabilities required?
      fhir:TestScript.metadata.capability.validated [ boolean ]; # 0..1 Are the capabilities validated?
      fhir:TestScript.metadata.capability.description [ string ]; # 0..1 The expected capabilities of the server
      fhir:TestScript.metadata.capability.origin [ integer ], ... ; # 0..* Which origin server these requirements apply to
      fhir:TestScript.metadata.capability.destination [ integer ]; # 0..1 Which server these requirements apply to
      fhir:TestScript.metadata.capability.link [ uri ], ... ; # 0..* Links to the FHIR specification
      fhir:TestScript.metadata.capability.capabilities [ Reference(CapabilityStatement) ]; # 1..1 Required Capability Statement
    ], ...;
  ];
  fhir:TestScript.fixture [ # 0..* Fixture in the test script - by reference (uri)
    fhir:TestScript.fixture.autocreate [ boolean ]; # 0..1 Whether or not to implicitly create the fixture during setup
    fhir:TestScript.fixture.autodelete [ boolean ]; # 0..1 Whether or not to implicitly delete the fixture during teardown
    fhir:TestScript.fixture.resource [ Reference(Any) ]; # 0..1 Reference of the resource
  ], ...;
  fhir:TestScript.profile [ Reference(Any) ], ... ; # 0..* Reference of the validation profile
  fhir:TestScript.variable [ # 0..* Placeholder for evaluated elements
    fhir:TestScript.variable.name [ string ]; # 1..1 Descriptive name for this variable
    fhir:TestScript.variable.defaultValue [ string ]; # 0..1 Default, hard-coded, or user-defined value for this variable
    fhir:TestScript.variable.description [ string ]; # 0..1 Natural language description of the variable
    fhir:TestScript.variable.expression [ string ]; # 0..1 The fluentpath expression against the fixture body
    fhir:TestScript.variable.headerField [ string ]; # 0..1 HTTP header field name for source
    fhir:TestScript.variable.hint [ string ]; # 0..1 Hint help text for default value to enter
    fhir:TestScript.variable.path [ string ]; # 0..1 XPath or JSONPath against the fixture body
    fhir:TestScript.variable.sourceId [ id ]; # 0..1 Fixture Id of source expression or headerField within this variable
  ], ...;
  fhir:TestScript.rule [ # 0..* Assert rule used within the test script
    fhir:TestScript.rule.resource [ Reference(Any) ]; # 1..1 Assert rule resource reference
    fhir:TestScript.rule.param [ # 0..* Rule parameter template
      fhir:TestScript.rule.param.name [ string ]; # 1..1 Parameter name matching external assert rule parameter
      fhir:TestScript.rule.param.value [ string ]; # 0..1 Parameter value defined either explicitly or dynamically
    ], ...;
  ], ...;
  fhir:TestScript.ruleset [ # 0..* Assert ruleset used within the test script
    fhir:TestScript.ruleset.resource [ Reference(Any) ]; # 1..1 Assert ruleset resource reference
    fhir:TestScript.ruleset.rule [ # 1..* The referenced rule within the ruleset
      fhir:TestScript.ruleset.rule.ruleId [ id ]; # 1..1 Id of referenced rule within the ruleset
      fhir:TestScript.ruleset.rule.param [ # 0..* Ruleset rule parameter template
        fhir:TestScript.ruleset.rule.param.name [ string ]; # 1..1 Parameter name matching external assert ruleset rule parameter
        fhir:TestScript.ruleset.rule.param.value [ string ]; # 0..1 Parameter value defined either explicitly or dynamically
      ], ...;
    ], ...;
  ], ...;
  fhir:TestScript.setup [ # 0..1 A series of required setup operations before tests are executed
    fhir:TestScript.setup.action [ # 1..* A setup operation or assert to perform
      fhir:TestScript.setup.action.operation [ # 0..1 The setup operation to perform
        fhir:TestScript.setup.action.operation.type [ Coding ]; # 0..1 The operation code type that will be executed
        fhir:TestScript.setup.action.operation.resource [ code ]; # 0..1 Resource type
        fhir:TestScript.setup.action.operation.label [ string ]; # 0..1 Tracking/logging operation label
        fhir:TestScript.setup.action.operation.description [ string ]; # 0..1 Tracking/reporting operation description
        fhir:TestScript.setup.action.operation.accept [ code ]; # 0..1 xml | json | ttl | none
        fhir:TestScript.setup.action.operation.contentType [ code ]; # 0..1 xml | json | ttl | none
        fhir:TestScript.setup.action.operation.destination [ integer ]; # 0..1 Server responding to the request
        fhir:TestScript.setup.action.operation.encodeRequestUrl [ boolean ]; # 0..1 Whether or not to send the request url in encoded format
        fhir:TestScript.setup.action.operation.origin [ integer ]; # 0..1 Server initiating the request
        fhir:TestScript.setup.action.operation.params [ string ]; # 0..1 Explicitly defined path parameters
        fhir:TestScript.setup.action.operation.requestHeader [ # 0..* Each operation can have one or more header elements
          fhir:TestScript.setup.action.operation.requestHeader.field [ string ]; # 1..1 HTTP header field name
          fhir:TestScript.setup.action.operation.requestHeader.value [ string ]; # 1..1 HTTP headerfield value
        ], ...;
        fhir:TestScript.setup.action.operation.requestId [ id ]; # 0..1 Fixture Id of mapped request
        fhir:TestScript.setup.action.operation.responseId [ id ]; # 0..1 Fixture Id of mapped response
        fhir:TestScript.setup.action.operation.sourceId [ id ]; # 0..1 Fixture Id of body for PUT and POST requests
        fhir:TestScript.setup.action.operation.targetId [ id ]; # 0..1 Id of fixture used for extracting the [id],  [type], and [vid] for GET requests
        fhir:TestScript.setup.action.operation.url [ string ]; # 0..1 Request URL
      ];
      fhir:TestScript.setup.action.assert [ # 0..1 The assertion to perform
        fhir:TestScript.setup.action.assert.label [ string ]; # 0..1 Tracking/logging assertion label
        fhir:TestScript.setup.action.assert.description [ string ]; # 0..1 Tracking/reporting assertion description
        fhir:TestScript.setup.action.assert.direction [ code ]; # 0..1 response | request
        fhir:TestScript.setup.action.assert.compareToSourceId [ string ]; # 0..1 Id of the source fixture to be evaluated
        fhir:TestScript.setup.action.assert.compareToSourceExpression [ string ]; # 0..1 The fluentpath expression to evaluate against the source fixture
        fhir:TestScript.setup.action.assert.compareToSourcePath [ string ]; # 0..1 XPath or JSONPath expression to evaluate against the source fixture
        fhir:TestScript.setup.action.assert.contentType [ code ]; # 0..1 xml | json | ttl | none
        fhir:TestScript.setup.action.assert.expression [ string ]; # 0..1 The fluentpath expression to be evaluated
        fhir:TestScript.setup.action.assert.headerField [ string ]; # 0..1 HTTP header field name
        fhir:TestScript.setup.action.assert.minimumId [ string ]; # 0..1 Fixture Id of minimum content resource
        fhir:TestScript.setup.action.assert.navigationLinks [ boolean ]; # 0..1 Perform validation on navigation links?
        fhir:TestScript.setup.action.assert.operator [ code ]; # 0..1 equals | notEquals | in | notIn | greaterThan | lessThan | empty | notEmpty | contains | notContains | eval
        fhir:TestScript.setup.action.assert.path [ string ]; # 0..1 XPath or JSONPath expression
        fhir:TestScript.setup.action.assert.requestMethod [ code ]; # 0..1 delete | get | options | patch | post | put
        fhir:TestScript.setup.action.assert.requestURL [ string ]; # 0..1 Request URL comparison value
        fhir:TestScript.setup.action.assert.resource [ code ]; # 0..1 Resource type
        fhir:TestScript.setup.action.assert.response [ code ]; # 0..1 okay | created | noContent | notModified | bad | forbidden | notFound | methodNotAllowed | conflict | gone | preconditionFailed | unprocessable
        fhir:TestScript.setup.action.assert.responseCode [ string ]; # 0..1 HTTP response code to test
        fhir:TestScript.setup.action.assert.rule [ # 0..1 The reference to a TestScript.rule
          fhir:TestScript.setup.action.assert.rule.ruleId [ id ]; # 1..1 Id of the TestScript.rule
          fhir:TestScript.setup.action.assert.rule.param [ # 0..* Rule parameter template
            fhir:TestScript.setup.action.assert.rule.param.name [ string ]; # 1..1 Parameter name matching external assert rule parameter
            fhir:TestScript.setup.action.assert.rule.param.value [ string ]; # 1..1 Parameter value defined either explicitly or dynamically
          ], ...;
        ];
        fhir:TestScript.setup.action.assert.ruleset [ # 0..1 The reference to a TestScript.ruleset
          fhir:TestScript.setup.action.assert.ruleset.rulesetId [ id ]; # 1..1 Id of the TestScript.ruleset
          fhir:TestScript.setup.action.assert.ruleset.rule [ # 0..* The referenced rule within the ruleset
            fhir:TestScript.setup.action.assert.ruleset.rule.ruleId [ id ]; # 1..1 Id of referenced rule within the ruleset
            fhir:TestScript.setup.action.assert.ruleset.rule.param [ # 0..* Rule parameter template
              fhir:TestScript.setup.action.assert.ruleset.rule.param.name [ string ]; # 1..1 Parameter name matching external assert ruleset rule parameter
              fhir:TestScript.setup.action.assert.ruleset.rule.param.value [ string ]; # 1..1 Parameter value defined either explicitly or dynamically
            ], ...;
          ], ...;
        ];
        fhir:TestScript.setup.action.assert.sourceId [ id ]; # 0..1 Fixture Id of source expression or headerField
        fhir:TestScript.setup.action.assert.validateProfileId [ id ]; # 0..1 Profile Id of validation profile reference
        fhir:TestScript.setup.action.assert.value [ string ]; # 0..1 The value to compare to
        fhir:TestScript.setup.action.assert.warningOnly [ boolean ]; # 0..1 Will this assert produce a warning only on error?
      ];
    ], ...;
  ];
  fhir:TestScript.test [ # 0..* A test in this script
    fhir:TestScript.test.name [ string ]; # 0..1 Tracking/logging name of this test
    fhir:TestScript.test.description [ string ]; # 0..1 Tracking/reporting short description of the test
    fhir:TestScript.test.action [ # 1..* A test operation or assert to perform
      fhir:TestScript.test.action.operation [ See TestScript.setup.action.operation ]; # 0..1 The setup operation to perform
      fhir:TestScript.test.action.assert [ See TestScript.setup.action.assert ]; # 0..1 The setup assertion to perform
    ], ...;
  ], ...;
  fhir:TestScript.teardown [ # 0..1 A series of required clean up steps
    fhir:TestScript.teardown.action [ # 1..* One or more teardown operations to perform
      fhir:TestScript.teardown.action.operation [ See TestScript.setup.action.operation ]; # 1..1 The teardown operation to perform
    ], ...;
  ];
]

  Changes since DSTU2

TestScript
TestScript.title
  • Added Element
TestScript.status
  • Change value set from http://hl7.org/fhir/ValueSet/conformance-resource-status to http://hl7.org/fhir/ValueSet/publication-status
TestScript.experimental
  • Now marked as Modifier
TestScript.contact
  • Type changed from BackboneElement to ContactDetail
TestScript.description
  • Type changed from string to markdown
TestScript.useContext
  • Type changed from CodeableConcept to UsageContext
  • Remove Binding http://hl7.org/fhir/ValueSet/use-context (extensible)
TestScript.jurisdiction
  • Added Element
TestScript.purpose
  • Added Element
TestScript.copyright
  • Type changed from string to markdown
TestScript.origin
  • Added Element
TestScript.origin.index
  • Added Element
TestScript.origin.profile
  • Added Element
TestScript.destination
  • Added Element
TestScript.destination.index
  • Added Element
TestScript.destination.profile
  • Added Element
TestScript.metadata.capability.origin
  • Added Element
TestScript.metadata.capability.capabilities
  • Added Element
TestScript.fixture.autocreate
  • Default Value "false" added
TestScript.fixture.autodelete
  • Default Value "false" added
TestScript.variable.defaultValue
  • Added Element
TestScript.variable.description
  • Added Element
TestScript.variable.expression
  • Added Element
TestScript.variable.hint
  • Added Element
TestScript.rule
  • Added Element
TestScript.rule.resource
  • Added Element
TestScript.rule.param
  • Added Element
TestScript.rule.param.name
  • Added Element
TestScript.rule.param.value
  • Added Element
TestScript.ruleset
  • Added Element
TestScript.ruleset.resource
  • Added Element
TestScript.ruleset.rule
  • Added Element
TestScript.ruleset.rule.ruleId
  • Added Element
TestScript.ruleset.rule.param
  • Added Element
TestScript.ruleset.rule.param.name
  • Added Element
TestScript.ruleset.rule.param.value
  • Added Element
TestScript.setup.action.operation.destination
  • Default Value "0" removed
TestScript.setup.action.operation.origin
  • Added Element
TestScript.setup.action.operation.requestId
  • Added Element
TestScript.setup.action.assert.compareToSourceExpression
  • Added Element
TestScript.setup.action.assert.expression
  • Added Element
TestScript.setup.action.assert.requestMethod
  • Added Element
TestScript.setup.action.assert.requestURL
  • Added Element
TestScript.setup.action.assert.rule
  • Added Element
TestScript.setup.action.assert.rule.ruleId
  • Added Element
TestScript.setup.action.assert.rule.param
  • Added Element
TestScript.setup.action.assert.rule.param.name
  • Added Element
TestScript.setup.action.assert.rule.param.value
  • Added Element
TestScript.setup.action.assert.ruleset
  • Added Element
TestScript.setup.action.assert.ruleset.rulesetId
  • Added Element
TestScript.setup.action.assert.ruleset.rule
  • Added Element
TestScript.setup.action.assert.ruleset.rule.ruleId
  • Added Element
TestScript.setup.action.assert.ruleset.rule.param
  • Added Element
TestScript.setup.action.assert.ruleset.rule.param.name
  • Added Element
TestScript.setup.action.assert.ruleset.rule.param.value
  • Added Element
TestScript.teardown.action.operation
  • Min Cardinality changed from 0 to 1
TestScript.contact.name
  • deleted
TestScript.contact.telecom
  • deleted
TestScript.requirements
  • deleted
TestScript.metadata.capability.conformance
  • deleted
TestScript.multiserver
  • deleted
TestScript.setup.metadata
  • deleted
TestScript.test.metadata
  • deleted

See the Full Difference for further information

This analysis is available as XML or JSON .

See R2 <--> R3 Conversion Maps (status = 6 tests that all execute ok. 6 fail round-trip testing and 6 r3 resources are invalid (11 errors). ).

 

Alternate definitions: Schema / Schematron , Resource Profile Master Definition ( XML , JSON ), Questionnaire XML Schema / Schematron (for ) + JSON Schema , ShEx (for Turtle )

TestScript.useContext
Path Definition Type Reference
TestScript.status The lifecycle status of a Value Set or Concept Map. Required ConformanceResourceStatus PublicationStatus
TestScript.jurisdiction Indicates the countries, regions, disciplines Countries and other aspects of use regions within which this artifact is targeted for use. use Extensible Context of Use Jurisdiction ValueSet
TestScript.origin.profile The type of origin profile the test system supports. Extensible TestScriptProfileOriginType
TestScript.destination.profile The type of destination profile the test system supports. Extensible TestScriptProfileDestinationType
TestScript.setup.action.operation.type The allowable operation code types. Extensible TestScriptOperationCodes TestScriptOperationCode
TestScript.setup.action.operation.resource
TestScript.setup.action.assert.resource
Either a resource or a data type. Required http://hl7.org/fhir/valueset/defined-types Defined Types FHIRDefinedType
TestScript.setup.action.operation.accept
TestScript.setup.action.operation.contentType
TestScript.setup.action.assert.contentType
The content or mime type. Required ContentType
TestScript.setup.action.assert.direction The type of direction to use for assertion. Required AssertionDirectionType
TestScript.setup.action.assert.operator The type of operator to use for assertion. Required AssertionOperatorType
TestScript.setup.action.assert.requestMethod The allowable request method or HTTP operation codes. Required TestScriptRequestMethodCode
TestScript.setup.action.assert.response The type of response code to use for assertion. Required AssertionResponseTypes

  • inv-1 : On TestScript.setup.action: Setup action SHALL contain either an operation or assert but not both. (xpath ( expression on f:TestScript/f:setup/f:action: TestScript.setup.action: (f:operation or f:assert) and not(f:operation and f:assert) operation.exists() xor assert.exists() )
  • inv-10 : On TestScript.setup.action.operation: TestScript.setup.action.assert: Setup operation action assert SHALL contain either sourceId or targetId or params compareToSourceId and compareToSourceExpression, compareToSourceId and compareToSourcePath or url. (xpath neither. ( expression on f:TestScript/f:setup/f:action/f:operation: TestScript.setup.action.assert: f:sourceId or ((f:targetId or f:url or f:params) and (count(f:targetId) + count(f:url) + count(f:params) =1)) or (f:type/f:code/@value='conformance' or f:type/f:code/@value='search' or f:type/f:code/@value='transaction' compareToSourceId.empty() xor (compareToSourceExpression.exists() or f:type/f:code/@value='history') compareToSourcePath.exists()) )
  • inv-11 : On TestScript.test.action.operation: TestScript.test.action.assert: Test operation action assert SHALL contain either sourceId or targetId or params or url. (xpath on f:TestScript/f:test/f:action/f:operation: f:sourceId or (f:targetId or f:url or f:params) compareToSourceId and (count(f:targetId) + count(f:url) + count(f:params) =1) or (f:type/f:code/@value='conformance' or f:type/f:code/@value='search' or f:type/f:code/@value='transaction' compareToSourceExpression, compareToSourceId and compareToSourcePath or f:type/f:code/@value='history') ) neither. ( expression inv-12 : On TestScript.teardown.action.operation: Teardown operation SHALL contain either sourceId or targetId or params or url. (xpath on f:TestScript/f:teardown/f:action/f:operation: TestScript.test.action.assert: f:sourceId or (f:targetId or f:url or (f:params and f:resource)) and (count(f:targetId) + count(f:url) + count(f:params) =1) or (f:type/f:code/@value='conformance' or f:type/f:code/@value='search' or f:type/f:code/@value='transaction' compareToSourceId.empty() xor (compareToSourceExpression.exists() or f:type/f:code/@value='history') compareToSourcePath.exists()) )
  • inv-13 inv-12 : On TestScript.setup.action.assert: Setup action assert shall contain both compareToSourceId response and compareToSourcePath or neither. (xpath responseCode SHALL be empty when direction equals request ( expression on f:TestScript/f:setup/f:action/f:assert: TestScript.setup.action.assert: (f:compareToSourceId (response.empty() and f:compareToSourcePath) responseCode.empty() and direction = 'request') or not(f:compareToSourceId direction.empty() or f:compareToSourcePath) direction = 'response' )
  • inv-14 inv-13 : On TestScript.test.action.assert: Test action assert shall contain both compareToSourceId response and compareToSourcePath or neither. (xpath response and responseCode SHALL be empty when direction equals request ( expression on f:TestScript/f:test/f:action/f:assert: TestScript.test.action.assert: (f:compareToSourceId (response.empty() and f:compareToSourcePath) responseCode.empty() and direction = 'request') or not(f:compareToSourceId direction.empty() or f:compareToSourcePath) direction = 'response' )
  • inv-2 : On TestScript.test.action: Test action SHALL contain either an operation or assert but not both. (xpath on f:TestScript/f:test/f:action: (f:operation or f:assert) and not(f:operation and f:assert) ) ( expression inv-3 : On TestScript.teardown.action: Teardown action SHALL contain an operation. (xpath on f:TestScript/f:teardown/f:action: TestScript.test.action: f:operation operation.exists() xor assert.exists() )
  • inv-4 inv-3 : On TestScript.variable: Variable cannot can only contain both one of expression, headerField and or path. (xpath on f:TestScript/f:variable: not(f:headerField and f:path) ) ( expression inv-5 : On TestScript.metadata: TestScript metadata capability SHALL contain required or validated or both. (xpath on f:TestScript/f:metadata: TestScript.variable: f:capability/f:required expression.empty() or f:capability/f:validated headerField.empty() or (f:capability/f:required and f:capability/f:validated) path.empty() )
  • inv-6 inv-4 : On TestScript.setup.metadata: Setup TestScript.metadata: TestScript metadata capability SHALL contain required or validated or both. (xpath on f:TestScript/f:setup/f:metadata: f:capability/f:required or f:capability/f:validated or (f:capability/f:required and f:capability/f:validated) ) ( expression inv-7 : On TestScript.test.metadata: Test metadata capability SHALL contain required or validated or both. (xpath on f:TestScript/f:test/f:metadata: TestScript.metadata: f:capability/f:required or f:capability/f:validated capability.required.exists() or (f:capability/f:required and f:capability/f:validated) capability.validated.exists() )
  • inv-8 inv-5 : On TestScript.setup.action.assert: Only a single assertion SHALL be present within setup action assert element. (xpath ( expression on f:TestScript/f:setup/f:action/f:assert: TestScript.setup.action.assert: count(f:contentType) contentType.count() + count(f:headerField) expression.count() + count(f:minimumId) headerField.count() + count(f:navigationLinks) minimumId.count() + count(f:path) navigationLinks.count() + count(f:resource) path.count() + count(f:responseCode) requestMethod.count() + count(f:response) resource.count() + count(f:validateProfileId) responseCode.count() + response.count() + rule.count() + ruleset.count() + validateProfileId.count() <=1 )
  • inv-9 inv-6 : On TestScript.test.action.assert: Only a single assertion SHALL be present within test action assert element. (xpath ( expression on f:TestScript/f:test/f:action/f:assert: TestScript.test.action.assert: count(f:contentType) contentType.count() + count(f:headerField) expression.count() + count(f:minimumId) headerField.count() + count(f:navigationLinks) minimumId.count() + count(f:path) navigationLinks.count() + count(f:resource) path.count() + count(f:responseCode) requestMethod.count() + count(f:response) resource.count() + count(f:validateProfileId) responseCode.count() + response.count() + rule.count() + ruleset.count() + validateProfileId.count() <=1 )
  • .xmlCode { border: 1px solid #CCCCCC; background: #F0FFFF; padding: 0px 2px 10px 50px; margin: 0; margin-bottom: 20px; font-size: 0.9em; } xmp { margin: 0; padding: 0; } 6.24.5 Notes 6.24.5.1 How Tos 6.24.5.1.1 Test create operation To test if create operation is properly supported on a server, run the operation as part of TestScript.test . First, define the fixture as a reference at the top of the test script. The fixture will hold the body of the POST request: Note that it is illegal for the fixture to contain a resource id in a create operation. Point the sourceId element of the create operation to the fixture id just defined: There are two ways to verify that the create operation returned the right status code: Use assert.response : See response codes for complete list. Use assert.responseCode explicitly: 6.24.5.1.2 Test search operation To test if search operation is properly supported on a server, run the operation as part of TestScript.test . Use the resource element to specify the resource type and the params element to specify the search parameters: The contentType element is optional and will default to "xml" which will translate to HTTP request header "Content-Type" being set to "application/xml+fhir" by test engines. In this case, though, it was used to set it to "application/json+fhir". The responseId element was used to store the response in a reference called "R1". This reference will hold both the response headers and the response body. Verify that the search operation returned the right status code: See response codes for complete list. Verify that the search operation returned the right resource type: There are many ways to verify that the search operation returned the right Patient:
  • Explicitly compare the elements to known value: The sourceId element is pointed to the responseId value of the search operation. If no sourceId is specified, then test engines will use the response of the last inv-7 : On TestScript.setup.action.operation: Setup operation in the test script even if responseId was not specified in the operation. The path element holds an XPath or JSONPath expression against the response body contents. Compare the elements in response to elements in another fixture that is SHALL contain either dynamically set by responseId or defined statically by the fixture element at the top of the script: This time the birthDate value in the response is compared to the birthDate value in a fixture called 'F1'. Verify that the response contains all the element/content in another fixture pointed to by minimumId . Test engines will parse the 'body' of the F1 fixture and verify that each element and its value matches the corresponding element in the R1 response body. In other words, R1 is verified to be a 'superset' of F1. The resource id element in the body will be ignored during comparison. The headers will also be ignored. F1 can be statically defined or it can be the responseId for another operation. If sourceId is not specified, then test engines will use the response of the last operation. So the previous assertion could have been defined as: 6.24.5.1.3 Perform delete operation in teardown Test scripts should clean up resources created as part of execution. The TestScript.teardown operations will get executed once before the test script execution completes. Here are a couple of ways to run delete operation in TestScript.teardown : Use conditional delete operation in TestScript.teardown : Use delete operation with targetId fixture. To do that, the resource must have been created during TestScript.setup or TestScript.test : As part of TestScript.teardown , run the delete operation with targetId value pointed to sourceId value of the create operation: Test engines will keep track of response headers and body of all operations. The delete operation's targetId value is expected to correspond to the responseId of a GET operation (such as search or read) or the sourceId of a POST/PUT operation (such as create). For targetId value corresponding to responseId of GET operations (such as search or read), test engines will use the resource type and id returned in the GET response body's resource to set the [type] and [id] in delete operation's URL, respectively. For targetId value corresponding to responseId of POST/PUT operations (such as create), test engines will use the resource type and id returned in the POST/PUT response "Location" header to set the [type] and [id] in delete operation's URL, respectively. This is the case in the example above. The targetId value cannot point to a statically defined fixture as the id in the fixture cannot be relied upon. 6.24.5.1.4 Perform delete operation in setup Deletion of resources created during test script execution should be done using delete operation in TestScript.teardown . See Perform delete operation in teardown for details. There might be left-over resource instances though on the server from prior executions of the script that terminated prematurely through an error. Resources can be deleted in TestScript.setup as well to ensure reliable test execution. To delete a resource in setup, the server is required to support Conditional Delete operation. Use the params element to specify the search criteria for the delete operation: Test engines will append the contents of the params element to url after [type]: "[base]/[type] ?[search parameters]" . The resource element value ("Patient") will be used to replace [type] in the url. 6.24.5.1.5 Test conditional delete operation To test if a server supports conditional delete operation, run a create operation prior to the delete using a sourceId that points to a fixture defined at the top of the script: Then use the params element to specify the search criteria for the delete operation: Test engines will append the contents of the params element to url after [type]: "[base]/[type] ?[search parameters]" . The resource element value ("Patient") will be used to replace [type] in the or url. To verify that the delete operation returned the right status code: To verify that the resource was indeed deleted on the server, run a search using the same parameters and verify that the status code is 404 (not found): 6.24.5.1.6 Test conditional create operation To test if a server supports conditional create operation, use the 'If-None-Exist' request header: The response code of 200 verifies that the resource already exists and did not get created: 6.24.5.1.7 Test update operation ( expression Update operations require a resource id. The id must be present in the fixture (PUT body contents) as well as the URL. The values must match. Because resource ids cannot be predicted on the server, it is best to retrieve the id on a resource freshly created as part of the script There are many ways to do that. Below is a couple: Use update operation with targetId fixture pointing to create operation's responseId : Test engines will keep track of response headers and body of all operations. The update operation's targetId value is expected to correspond to the responseId of a GET operation (such as search or read) TestScript.setup.action.operation: sourceId.exists() or the sourceId of a POST/PUT operation (such as create). For targetId value corresponding to responseId of GET operations (such as search (targetId.count() + url.count() + params.count() = 1) or read), test engines will use the resource type and id returned in the GET response body's resource to set the [type] and [id] in update operation's URL, respectively. This is the case in the next example below. For targetId value corresponding to responseId of POST/PUT operations (such as create and update), test engines will use the resource type and id returned in the POST/PUT response "Location" header to set the [type] and [id] in update operation's URL, respectively. This is the case in the example above. The targetId value cannot point to a statically defined fixture as the id (type.code in the fixture cannot be relied upon. Use update operation with targetId fixture pointing to search operation's responseId : ('capabilities' |'search' | 'transaction' | 'history')) )
  • After the update operation, test scripts would perform at least one more read/search operation to retrieve the contents of the updated resource and then perform assertions to verify that the data did indeed get updated on the server: Verify that the birthdate got updated and is being returned properly: 6.24.5.1.8
  • inv-8 : On TestScript.test.action.operation: Test conditional update operation Unlike a regular update operation, a conditional update operation does not require a resource id in the URL (or the body of the PUT). To test conditional update, use params element in the operation instead of SHALL contain either sourceId or targetId . The resource element will be required in this case. Test engines will append the contents of the or params element to url after [type]: "PUT [base]/[type] ?[search parameters]" . The resource element value ("Patient") will be used to replace [type] in the URL. Verify that the birthdate got updated and is being returned properly: 6.24.5.1.9 Test read operation or url. ( expression The read operation operation requires the resource id in the URL. Since resource ids are unpredictable on servers, it's best to create the resource within the test script prior to executing the read operation: One way to execute the read operation is to run the read operation with targetId value pointed to responseId value of the create operation: Test engines will keep track of response headers and body of all operations. The read operation's targetId value is expected to correspond to the responseId of a GET operation (such as search or read) TestScript.test.action.operation: sourceId.exists() or the sourceId of a POST/PUT operation (such as create). For targetId value corresponding to responseId of GET operations (such as search (targetId.count() + url.count() + params.count() = 1) or read), test engines will use the resource type and id returned in the GET response body's resource to set the [type] and [id] in read operation's URL, respectively. For targetId value corresponding to responseId of POST/PUT operations (such as create), test engines will use the resource type and id returned in the POST/PUT response "Location" header to set the [type] and [id] in read operation's URL, respectively. This is the case in the example above. The targetId value cannot point to a statically defined fixture as the id (type.code in the fixture cannot be relied upon. 6.24.5.1.10 ('capabilities' | 'search' | 'transaction' | 'history')) Test vread operation The vread operation operation requires the resource id as well as the resource version id in the URL. Since resource ids and version ids are unpredictable on servers, it's best to create the resource within the test script prior to executing the vread operation: One way to execute the vread operation is to run the vread operation with targetId value pointed to responseId value of the create operation: )
  • Test engines will keep track of response headers and body of all operations. The vread operation's targetId value is expected to correspond to the responseId of a GET inv-9 : On TestScript.teardown.action.operation: Teardown operation (such as search or read) or the SHALL contain either sourceId of a POST/PUT operation (such as create). For targetId value corresponding to responseId of GET operations (such as search or read), test engines will use the resource type, id and version id returned in the GET response body's resource to set the [type], [id] and [vid] in vread operation's URL, respectively. For targetId value corresponding to responseId of POST/PUT operations (such as create), test engines will use the resource type, id and version id returned in the POST/PUT response "Location" header to set the [type], [id] and [vid] in vread operation's URL, respectively. This is the case in the example above. The targetId value cannot point to a statically defined fixture as the id in the fixture cannot be relied upon. 6.24.5.1.11 Test history operation The history operation can be executed in the following ways: GET [base]/[type]/[id]/_history{?[parameters]&_format=[mime-type]} Here the resource id is required in the URL. This is similar to read operation if targetId elemet is used. See Test read operation for details. GET [base]/[type]/_history{?[parameters]&_format=[mime-type]} Here the resource id is not required in the URL. Instead of targetId element, the or params element can be used to specify the search criteria for the history operation. In the following example, all history entries for John Doe patient would be returned by server: GET [base]/_history{?[parameters]&_format=[mime-type]} Here neither the resource type nor the resource id is required in the or url. In the following example, no more than 50 history entries would be returned by server: 6.24.5.1.12 Specify Accept header in request ( expression The default "Accept" header that will be set on all GET operations (such as read, vread, search, history, etc.) will be "application/xml+fhir". There are two ways to change the default "Accept" header: Use the accept element: Test engines will set the Accept header to "application/json+fhir" if "json" is specified and will use "application/xml+fhir" if "xml" is specified. Use the requestHeader element to set "Accept" explicitly : Test engines will take values specified for requestHeader "as-is" and not transform them. This might be useful for negative testing e.g. the value can be set explicitly to "applcation/xml" TestScript.teardown.action.operation: sourceId.exists() or an invalid value and verify server response. 6.24.5.1.13 Specify Content-Type header (targetId.count() + url.count() + params.count() = 1) or (type.code in request The default "Content-Type" header that will be set on all POST/PUT operations (such as create, update, etc.) will be "application/xml+fhir". There are two ways to change the default "Content-Type" header: Use the contentType element: Test engines will set the Content-Type header to "application/json+fhir" if "json" is specified and will use "application/xml+fhir" if "xml" is specified. ('capabilities' | 'search' | 'transaction' | 'history')) )
  • Use the requestHeader element to set Content-Type explicitly : Test engines will take values specified for requestHeader
"as-is" and not transform them. This might be useful for negative testing e.g. the value can be set explicitly to "applcation/xml" or an invalid value and verify server response.

There are two ways Please refer to verify the "Content-Type" header in response: Use the contentType element: Test engines will verify that "application/json+fhir" is present in Content-Type header if "json" is specified and will verify that "application/xml+fhir" is present if "xml" is specified. Use the requestHeader element to verify Content-Type explicitly : Test engines will take values specified for headerField "as-is" and not interpret them. Note that test engines will not verify contentType in response if assertions for contentType are missing. 6.24.5.1.15 Use variables Variables Testing FHIR - How Tos can be defined against static fixtures and dynamic operation responses. They can be used in "operation.params", "operation.requestHeader.value", "operation.url", and "assert.value" element values. As such they allow for the data used in operations and assertions to be externally defined. The data could be unique to each client involved in interactions examples on working with a server or could be unique to a given server database instance. This allows for multiple clients to execute the same test scripts concurrently against the same server. Variables would be defined at the top of the script. Below is a variable that is defined as the Location header to the response referenced by "R1": Test engines will not evaluate this at this point. They will store the expresssion in "V1" and will look for "${}" in "operation.params", "operation.requestHeader.value", and "operation.url" element values during operation calls. Here is a read operation that will use the V1 variable. The variable expression was "Location against R1 response" (defined above). If a prior operation has not set R1 to be the responseId of the operation, then test engine will error out. Otherwise, V1 will be set to the Location header value of R1 response and that value will be substituted for ${V1} below. In other words, the read will be performed against the Location header value of R1 response. Below are three variables defined as path expressions against the static fixture referenced by "F1". The expressions are against the given name, family name, and birthDate of a patient resource. The resource data will be managed external to the test script. Again, test engines will not evaluate the path expression at this point. They will look for anything wrapped in '${}' in "operation.params", "operation.requestHeader.value", "operation.url", and "assert.value" element values and substitute the placeholders with the evaluated expressions.

Here is a conditional create operation that will set the requestHeader using the PatientGivenName, PatientFamilyName, and PatientDOB variables defined above. The variable expressions were path expressions against the statically defined F1 fixture. They will be evaluated against the fixture body (containing resource) and the corresponding values will be extracted from the fixtures and used to substitute the variables in the requestHeader value below. Here is a search operation that will perform a search using the PatientGivenName, PatientFamilyName, and PatientDOB variables defined above. The variable expressions were path expressions against the statically defined F1 fixture. They will be evaluated against the fixture body (containing resource) and the corresponding values will be extracted from the fixtures and used to substitute the variables in the params value below. Here are the assertions that verify that the search was successful: 6.24.5.1.16 Test server support for '_format' Servers are required to support "_format" in the request url to determine the response mime-type. See Content Type and Encodings Use the params element to specify the _format: Use the requestHeader element to verify Content-Type explicitly :

Search parameters for this resource. The contents of PatientCreateDelete.xml would be a minimal conformance statement to indicate what sections need to be present in server conformance statement: When the metadata capabilities section is defined at TestScript.metadata common parameters or at TestScript.setup.metadata , and the server's conformance statement does not contain the elements defined in the minimal conformance statement, then all the tests in the TestScript are skipped. When the metadata capabilities section is defined at TestScript.test.metadata also apply. See Searching and the server's conformance statement does not contain the elements defined for more information about searching in the minimal conformance statement, then only that test is skipped. The "metadata.capabilities.required" and "metadata.capabilities.validated" elements only indicate whether the capabilities are the primary focus of the test script or not. The do not impact the skipping logic. Capabilities whose "metadata.capabilities.validated" flag is true are the primary focus of the test script. 6.24.6 Operations This table presents a summary of the constraints applicable to TestScript.setup.action.operation, TestScript.test.action.operation, REST, messaging, and TestScript.teardown.action.operation elements. The operation elements should be configured consistently with the FHIR RESTful API summary . services.

read vread search history create update transaction conformance delete params The params element can be used to specify the [id] using variable substitutions and the rest of the highlighted portion in the request URL: [base]/[type] /[id] {?_format=[mime-type]} If used, then resource is required and targetId and url must not be specified. The params element can be used to specify the highlighted portion in the request URL: [base]/[type] {?[parameters]{&_format=[mime-type]}} If used, then resource is optional and targetId and url must not be specified. N/A The params element can be used in conditional update operation to specify the highlighted portion of the request URL: [base]/[type] ?[search parameters] N/A The params element can be used to specify the highlighted portion in the request URL: [base] /metadata {?_format=[mime-type]} The params element can be used to specify the [id] using variable substitutions in the request URL: [base]/[type] /[id] resource The resource element is required to specify the resource ([type]) in the request URL when params element is used. Will be ignored if targetId or url are specified. In the case of targetId , the resource type will be extracted from the fixture. If targetId is specified, then [type] for request URL will be determined from targetId's fixture and resource element will be ignored. Otherwise, resource type will be extracted from sourceId 's fixture if specified. For conditional updates , resource is required. N/A N/A targetId The targetId element can be used to specify the [type], [id], and [vid] in the request URL. If used, then params and url must not be specified. The targetId element can be used to specify the [type] and [id] in the request URL. If used, then params and url must not be specified. responseId The responseId element can be used to reference the operation response containing response body and headers. If specified, the value can later be used in assertion sourceId to evaluate path (XPath/JSONPath) and headerFields against the response received for an operation. N/A accept The accept element can be used to specify the "Accept" header in the outgoing HTTP request. If "json" is specified, then "Accept" value of "application/json+fhir" will be set in the request header. If "xml" is specified, then "application/xml+fhir" will be used. N/A contentType The contentType element can be used to specify the "Content-Type" header in the outgoing HTTP request. If "json" is specified, then "Content-Type" value of "application/json+fhir" will be set in the request header. If "xml" is specified, then "application/xml+fhir" will be used. 6.24.7 Assertions 6.24.8 Search Parameters
The params element can be used to specify the [id] and [vid] using variable substitutions and the rest of the highlighted portion in the request URL: [base]/[type] /[id]/_history/[vid] {?_format=[mime-type]} Name If used, then resource is required and targetId and url must not be specified. The params element can be used to specify the [id] using variable substitutions and the rest of the highlighted portion in the following request URLs: [base]/[type] /[id]/_history{?[parameters]&_format=[mime-type]} [base]/[type] /_history{?[parameters]&_format=[mime-type]} [base] /_history{?[parameters]&_format=[mime-type]} Type If used, then resource is optional and targetId and url must not be specified. Description If used, then resource is required and targetId and url must not be specified. Expression If used, then resource is ignored and targetId and url must not be specified. In Common If used, then resource is required and targetId and url must not be specified.
If targetId is specified, then [type] for request URL will be determined from targetId and resource element will be ignored. For conditional deletes , resource is required. sourceId N/A N/A N/A N/A date The sourceId date element points to a fixture to be used for the created resource. The fixture cannot contain the id element. The sourceId element points to a fixture to be used for the updated resource. Has to correspond to the responseId of an operation executed upstream in the test script. The response body must contain a resource with a resource id. The sourceId fixture cannot be statically defined because the id cannot be relied upon. Fixture to be used for the transaction. Has to be a Bundle . N/A script publication date N/A TestScript.date
The targetId element can be used to specify the [type] and [id] in the request URL. If used, then params and url must not be specified. The targetId value has to correspond to the responseId of an operation executed upstream in the test script. The response body must contain a reosurce with a resource id. The targetId fixture cannot be statically defined because the id cannot be relied upon. description The targetId element can be used to specify the [type], [id], and [vid] in the request URL. If used, then params and url string must not be specified. The targetId value has to correspond to the responseId of an operation executed upstream in the test script. The response body must contain a reosurce with a resource id. The targetId fixture cannot be statically defined because the id and vid cannot be relied upon. The targetId element cannot be used as it's not allowed with params element The targetId value has to correspond to the responseId description of an operation executed upstream in the test script. The response body must contain a reosurce with a resource id. The targetId fixture cannot be statically defined because the id and vid cannot be relied upon. N/A. The [type] for the request URL will be extracted from sourceId . N/A. The [type] for the request URL will be extracted from sourceId . N/A. script N/A. TestScript.description The targetId value has to correspond to the responseId of an operation executed upstream in the test script. The response body must contain a reosurce with a resource id. The targetId fixture cannot be statically defined because the id cannot be relied upon.
N/A requestHeader The requestHeader element allows for request headers to be specified explicitly . Test engines will take values specified for requestHeader "as-is" and not transform them. This allows for testing using: "If-Modified-Since" and "If-None-Match" headers. See Conditional read . "If-Match" header. See Managing resource contention . Conditional Create using "If-None-Exist". See Conditional Create . Invalid "Content-Type" header for negative testing. etc. destination If the TestScript is testing more than one FHIR server simultaneously, the destination identifies which server the operation applies to using zero-based indexing. url The url element will contain the full HTTP URL for the operation. This should rarely be used in test scripts. One possible application would be to test if the Location header returned in a response is pointing to an expected resource. See testscript-search example . identifier token Assertion Valid operator values Description contentType equals | notEquals | contains | notContains Asserts that the "Content-Type" in response header is or is not the specified value for contentType element depending on the operator used. headerField equals | notEquals | in | notIn | greaterThan | lessThan | empty | notEmpty | contains | notContains Asserts that the header specified for headerField element in the response contains, not contains, is equal, not equal, in, not in, greater than, or less than the value specified for value element if present. If the operator is "empty" or "notEmpty" then value will be ignored. If sourceId is not specified, then headerField will be evaluated against the last operation's response headers. minimumId N/A Asserts that the response contains all the element/content in another fixture pointed to by minimumId element. This can be a statically defined fixture or one that is dynamically set via responseId . navigationLinks N/A Asserts that the response Bundle contains or does NOT contain first, last, and next links depending on whether or not navigationLinks element is set to true or false. path equals | notEquals | in | notIn | greaterThan | lessThan | empty | notEmpty | contains | notContains Asserts that path against the response body evaluates to a value that contains, not contains, is equal, not equal, in, not in, greater than, or less than the value specified for value element if present. If the operator is "empty" or "notEmpty" then value will be ignored. If sourceId is not specified, then path will be evaluated against the last operation's response body. compareToSourcePath equals | notEquals Asserts that compareToSourcePath against the response body of compareToSourceId fixture evaluates to a value that is equal or notEqual to the evaluated value of path which must be present also. resource equals | notEquals Asserts that the resource returned in the response body is or is not of the specified value External identifier for resource element. response equals | notEquals Asserts that status code in the response is or is not one of the enumerated values in response abbreviations . responseCode equals | notEquals | in | notIn | greaterThan | lessThan Asserts that status code in the response is equal, notEqual, in, not in, greater than, or less than the specified value(s) for responseCode element validateProfileId N/A test script Asserts that the response is valid according to the profile specified by validateProfileId element. TestScript.identifier Search parameters for this resource. The common parameters also apply. See Searching for more information about searching in REST, messaging, and services.
Name jurisdiction Type token Description Intended jurisdiction for the test script Paths TestScript.jurisdiction
description name string Natural language description Computationally friendly name of the TestScript test script TestScript.description TestScript.name
identifier publisher token string External identifier Name of the publisher of the test script TestScript.identifier TestScript.publisher
name status string token Informal name for this TestScript The current status of the test script TestScript.name TestScript.status
testscript-capability string TestScript required and validated capability TestScript.metadata.capability.description
testscript-setup-capability title string TestScript setup required and validated capability The human-friendly name of the test script TestScript.setup.metadata.capability.description TestScript.title
testscript-test-capability url string uri TestScript The uri that identifies the test required and validated capability script TestScript.test.metadata.capability.description TestScript.url
url version uri token Absolute URL used to reference this TestScript The business version of the test script TestScript.url TestScript.version