Generated Narrative: ConceptMap R4B-TestScript-element-map-to-R4 Mapping from http://hl7.org/fhir/4.3 to http://hl7.org/fhir/4.0 Group 1 Mapping from http://hl7.org/fhir/StructureDefinition/TestScript|4.3.0 to TestScriptversion: 4.0.1) Source Code Relationship Target Code Comment TestScript.meta (meta) is equivalent to TestScript.meta Element `TestScript.meta` is mapped to FHIR R4 element `TestScript.meta` as `Equivalent`. TestScript.implicitRules (implicitRules) is equivalent to TestScript.implicitRules Element `TestScript.implicitRules` is mapped to FHIR R4 element `TestScript.implicitRules` as `Equivalent`. Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of it's narrative along with other profiles, value sets, etc. TestScript.language (language) is equivalent to TestScript.language Element `TestScript.language` is mapped to FHIR R4 element `TestScript.language` as `Equivalent`. Language is provided to support indexing and accessibility (typically, services such as text to speech use the language tag). The html language tag in the narrative applies to the narrative. The language tag on the resource may be used to specify the language of other presentations generated from the data in the resource. Not all the content has to be in the base language. The Resource.language should not be assumed to apply to the narrative automatically. If a language is specified, it should it also be specified on the div element in the html (see rules in HTML5 for information about the relationship between xml:lang and the html lang attribute). TestScript.text (text) is equivalent to TestScript.text Element `TestScript.text` is mapped to FHIR R4 element `TestScript.text` as `Equivalent`. Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a "text blob" or where text is additionally entered raw or narrated and encoded information is added later. TestScript.contained (contained) is equivalent to TestScript.contained Element `TestScript.contained` is mapped to FHIR R4 element `TestScript.contained` as `Equivalent`. This should never be done when the content can be identified properly, as once identification is lost, it is extremely difficult (and context dependent) to restore it again. Contained resources may have profiles and tags In their meta elements, but SHALL NOT have security labels. TestScript.url (url) is equivalent to TestScript.url Element `TestScript.url` is mapped to FHIR R4 element `TestScript.url` as `Equivalent`. Can be a urn:uuid: or a urn:oid: but real http: addresses are preferred. Multiple instances may share the same URL if they have a distinct version. The determination of when to create a new version of a resource (same url, new version) vs. defining a new artifact is up to the author. Considerations for making this decision are found in [Technical and Business Versions](https://hl7.org/fhir/resource..html#versions). In some cases, the resource can no longer be found at the stated url, but the url itself cannot change. Implementations can use the [meta.source](https://hl7.org/fhir/resou.html#meta) element to indicate where the current master source of the resource can be found. TestScript.identifier (identifier) is equivalent to TestScript.identifier Element `TestScript.identifier` is mapped to FHIR R4 element `TestScript.identifier` as `Equivalent`. Typically, this is used for identifiers that can go in an HL7 V3 II (instance identifier) data type, and can then identify this test script outside of FHIR, where it is not possible to use the logical URI. TestScript.version (version) is equivalent to TestScript.version Element `TestScript.version` is mapped to FHIR R4 element `TestScript.version` as `Equivalent`. There may be different test script instances that have the same identifier but different versions. The version can be appended to the url in a reference to allow a reference to a particular business version of the test script with the format [url]|[version]. TestScript.name (name) is equivalent to TestScript.name Element `TestScript.name` is mapped to FHIR R4 element `TestScript.name` as `Equivalent`. The name is not expected to be globally unique. The name should be a simple alphanumeric type name to ensure that it is machine-processing friendly. TestScript.title (title) is equivalent to TestScript.title Element `TestScript.title` is mapped to FHIR R4 element `TestScript.title` as `Equivalent`. This name does not need to be machine-processing friendly and may contain punctuation, white-space, etc. TestScript.status (status) is equivalent to TestScript.status Element `TestScript.status` is mapped to FHIR R4 element `TestScript.status` as `Equivalent`. Allows filtering of test scripts that are appropriate for use versus not. TestScript.experimental (experimental) is equivalent to TestScript.experimental Element `TestScript.experimental` is mapped to FHIR R4 element `TestScript.experimental` as `Equivalent`. Allows filtering of test scripts that are appropriate for use versus not. TestScript.date (date) is equivalent to TestScript.date Element `TestScript.date` is mapped to FHIR R4 element `TestScript.date` as `Equivalent`. Note that this is not the same as the resource last-modified-date, since the resource may be a secondary representation of the test script. Additional specific dates may be added as extensions or be found by consulting Provenances associated with past versions of the resource. TestScript.publisher (publisher) is equivalent to TestScript.publisher Element `TestScript.publisher` is mapped to FHIR R4 element `TestScript.publisher` as `Equivalent`. Usually an organization but may be an individual. The publisher (or steward) of the test script is the organization or individual primarily responsible for the maintenance and upkeep of the test script. This is not necessarily the same individual or organization that developed and initially authored the content. The publisher is the primary point of contact for questions or issues with the test script. This item SHOULD be populated unless the information is available from context. TestScript.contact (contact) is equivalent to TestScript.contact Element `TestScript.contact` is mapped to FHIR R4 element `TestScript.contact` as `Equivalent`. May be a web site, an email address, a telephone number, etc. TestScript.description (description) is equivalent to TestScript.description Element `TestScript.description` is mapped to FHIR R4 element `TestScript.description` as `Equivalent`. This description can be used to capture details such as why the test script was built, comments about misuse, instructions for clinical use and interpretation, literature references, examples from the paper world, etc. It is not a rendering of the test script as conveyed in the 'text' field of the resource itself. This item SHOULD be populated unless the information is available from context (e.g. the language of the test script is presumed to be the predominant language in the place the test script was created). TestScript.useContext (useContext) is equivalent to TestScript.useContext Element `TestScript.useContext` is mapped to FHIR R4 element `TestScript.useContext` as `Equivalent`. When multiple useContexts are specified, there is no expectation that all or any of the contexts apply. TestScript.jurisdiction (jurisdiction) is equivalent to TestScript.jurisdiction Element `TestScript.jurisdiction` is mapped to FHIR R4 element `TestScript.jurisdiction` as `Equivalent`. It may be possible for the test script to be used in jurisdictions other than those for which it was originally designed or intended. TestScript.purpose (purpose) is equivalent to TestScript.purpose Element `TestScript.purpose` is mapped to FHIR R4 element `TestScript.purpose` as `Equivalent`. This element does not describe the usage of the test script. Instead, it provides traceability of ''why'' the resource is either needed or ''why'' it is defined as it is. This may be used to point to source materials or specifications that drove the structure of this test script. TestScript.copyright (copyright) is equivalent to TestScript.copyright Element `TestScript.copyright` is mapped to FHIR R4 element `TestScript.copyright` as `Equivalent`. TestScript.origin (origin) maps to wider concept TestScript.origin Element `TestScript.origin` is mapped to FHIR R4 element `TestScript.origin` as `Equivalent`. The purpose of this element is to define the profile of an origin element used elsewhere in the script. Test engines could then use the origin-profile mapping to offer a filtered list of test systems that can serve as the sender for the interaction. TestScript.origin.index (index) is equivalent to TestScript.origin.index Element `TestScript.origin.index` is mapped to FHIR R4 element `TestScript.origin.index` as `Equivalent`. A given origin index (e.g. 1) can appear only once in the list (e.g. Origin 1 cannot be specified twice ... once as FormFiller and again as FormProcessor within the same script as that could get confusing during test configuration). Different origin indices could play the same actor in the same test script (e.g. You could have two different test systems acting as Form-Filler). The origin indices provided elsewhere in the test script must be one of these origin indices. TestScript.origin.profile (profile) is equivalent to TestScript.origin.profile Element `TestScript.origin.profile` is mapped to FHIR R4 element `TestScript.origin.profile` as `Equivalent`. Must be a "sender"/"client" profile. TestScript.destination (destination) maps to wider concept TestScript.destination Element `TestScript.destination` is mapped to FHIR R4 element `TestScript.destination` as `Equivalent`. The purpose of this element is to define the profile of a destination element used elsewhere in the script. Test engines could then use the destination-profile mapping to offer a filtered list of test systems that can serve as the receiver for the interaction. TestScript.destination.index (index) is equivalent to TestScript.destination.index Element `TestScript.destination.index` is mapped to FHIR R4 element `TestScript.destination.index` as `Equivalent`. A given destination index (e.g. 1) can appear only once in the list (e.g. Destination 1 cannot be specified twice ... once as Form-Manager and again as Form-Processor within the same script as that could get confusing during test configuration). Different destination indices could play the same actor in the same test script (e.g. You could have two different test systems acting as Form-Manager). The destination indices provided elsewhere in the test script must be one of these destination indices. TestScript.destination.profile (profile) is equivalent to TestScript.destination.profile Element `TestScript.destination.profile` is mapped to FHIR R4 element `TestScript.destination.profile` as `Equivalent`. Must be a "receiver"/"server" profile. TestScript.metadata (metadata) maps to wider concept TestScript.metadata Element `TestScript.metadata` is mapped to FHIR R4 element `TestScript.metadata` as `Equivalent`. TestScript.metadata.link (link) maps to wider concept TestScript.metadata.link Element `TestScript.metadata.link` is mapped to FHIR R4 element `TestScript.metadata.link` as `Equivalent`. TestScript.metadata.link.url (url) is equivalent to TestScript.metadata.link.url Element `TestScript.metadata.link.url` is mapped to FHIR R4 element `TestScript.metadata.link.url` as `Equivalent`. TestScript.metadata.link.description (description) is equivalent to TestScript.metadata.link.description Element `TestScript.metadata.link.description` is mapped to FHIR R4 element `TestScript.metadata.link.description` as `Equivalent`. TestScript.metadata.capability (capability) maps to wider concept TestScript.metadata.capability Element `TestScript.metadata.capability` is mapped to FHIR R4 element `TestScript.metadata.capability` as `Equivalent`. When the metadata capabilities section is defined at TestScript.metadata 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 and the server's conformance statement does not contain the elements defined 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. They do not impact the skipping logic. Capabilities whose "metadata.capabilities.validated" flag is true are the primary focus of the test script. TestScript.metadata.capability.required (required) is equivalent to TestScript.metadata.capability.required Element `TestScript.metadata.capability.required` is mapped to FHIR R4 element `TestScript.metadata.capability.required` as `Equivalent`. TestScript.metadata.capability.validated (validated) is equivalent to TestScript.metadata.capability.validated Element `TestScript.metadata.capability.validated` is mapped to FHIR R4 element `TestScript.metadata.capability.validated` as `Equivalent`. TestScript.metadata.capability.description (description) is equivalent to TestScript.metadata.capability.description Element `TestScript.metadata.capability.description` is mapped to FHIR R4 element `TestScript.metadata.capability.description` as `Equivalent`. TestScript.metadata.capability.origin (origin) is equivalent to TestScript.metadata.capability.origin Element `TestScript.metadata.capability.origin` is mapped to FHIR R4 element `TestScript.metadata.capability.origin` as `Equivalent`. TestScript.metadata.capability.destination (destination) is equivalent to TestScript.metadata.capability.destination Element `TestScript.metadata.capability.destination` is mapped to FHIR R4 element `TestScript.metadata.capability.destination` as `Equivalent`. TestScript.metadata.capability.link (link) is equivalent to TestScript.metadata.capability.link Element `TestScript.metadata.capability.link` is mapped to FHIR R4 element `TestScript.metadata.capability.link` as `Equivalent`. TestScript.metadata.capability.capabilities (capabilities) is equivalent to TestScript.metadata.capability.capabilities Element `TestScript.metadata.capability.capabilities` is mapped to FHIR R4 element `TestScript.metadata.capability.capabilities` as `Equivalent`. The conformance statement of the server has to contain at a minimum the contents of the reference pointed to by this element. TestScript.fixture (fixture) maps to wider concept TestScript.fixture Element `TestScript.fixture` is mapped to FHIR R4 element `TestScript.fixture` as `Equivalent`. TestScript.fixture.autocreate (autocreate) is equivalent to TestScript.fixture.autocreate Element `TestScript.fixture.autocreate` is mapped to FHIR R4 element `TestScript.fixture.autocreate` as `Equivalent`. TestScript.fixture.autodelete (autodelete) is equivalent to TestScript.fixture.autodelete Element `TestScript.fixture.autodelete` is mapped to FHIR R4 element `TestScript.fixture.autodelete` as `Equivalent`. TestScript.fixture.resource (resource) is equivalent to TestScript.fixture.resource Element `TestScript.fixture.resource` is mapped to FHIR R4 element `TestScript.fixture.resource` as `Equivalent`. See http://build.fhir.org/resourcelist.html for complete list of resource types. TestScript.profile (profile) is equivalent to TestScript.profile Element `TestScript.profile` is mapped to FHIR R4 element `TestScript.profile` as `Equivalent`. See http://build.fhir.org/resourcelist.html for complete list of resource types. TestScript.variable (variable) maps to wider concept TestScript.variable Element `TestScript.variable` is mapped to FHIR R4 element `TestScript.variable` as `Equivalent`. Variables would be set based either on XPath/JSONPath expressions against fixtures (static and response), or headerField evaluations against response headers. If variable evaluates to nodelist or anything other than a primitive value, then test engine would report an error. Variables would be used to perform clean replacements in "operation.params", "operation.requestHeader.value", and "operation.url" element values during operation calls and in "assert.value" during assertion evaluations. This limits the places that test engines would need to look for placeholders "${}". Variables are scoped to the whole script. They are NOT evaluated at declaration. They are evaluated by test engine when used for substitutions in "operation.params", "operation.requestHeader.value", and "operation.url" element values during operation calls and in "assert.value" during assertion evaluations. See example testscript-search.xml. TestScript.variable.name (name) is equivalent to TestScript.variable.name Element `TestScript.variable.name` is mapped to FHIR R4 element `TestScript.variable.name` as `Equivalent`. Placeholders would contain the variable name wrapped in ${} in "operation.params", "operation.requestHeader.value", and "operation.url" elements. These placeholders would need to be replaced by the variable value before the operation is executed. TestScript.variable.defaultValue (defaultValue) is equivalent to TestScript.variable.defaultValue Element `TestScript.variable.defaultValue` is mapped to FHIR R4 element `TestScript.variable.defaultValue` as `Equivalent`. The purpose of this element is to allow for a pre-defined value that can be used as a default or as an override value. Test engines can optionally use this as a placeholder for user-defined execution time values. TestScript.variable.description (description) is equivalent to TestScript.variable.description Element `TestScript.variable.description` is mapped to FHIR R4 element `TestScript.variable.description` as `Equivalent`. TestScript.variable.expression (expression) is equivalent to TestScript.variable.expression Element `TestScript.variable.expression` is mapped to FHIR R4 element `TestScript.variable.expression` as `Equivalent`. If headerField is defined, then the variable will be evaluated against the headers that sourceId is pointing to. If expression or path is defined, then the variable will be evaluated against the fixture body that sourceId is pointing to. It is an error to define any combination of expression, headerField and path. TestScript.variable.headerField (headerField) is equivalent to TestScript.variable.headerField Element `TestScript.variable.headerField` is mapped to FHIR R4 element `TestScript.variable.headerField` as `Equivalent`. If headerField is defined, then the variable will be evaluated against the headers that sourceId is pointing to. If path is defined, then the variable will be evaluated against the fixture body that sourceId is pointing to. It is an error to define both headerField and path. TestScript.variable.hint (hint) is equivalent to TestScript.variable.hint Element `TestScript.variable.hint` is mapped to FHIR R4 element `TestScript.variable.hint` as `Equivalent`. TestScript.variable.path (path) is equivalent to TestScript.variable.path Element `TestScript.variable.path` is mapped to FHIR R4 element `TestScript.variable.path` as `Equivalent`. If headerField is defined, then the variable will be evaluated against the headers that sourceId is pointing to. If expression or path is defined, then the variable will be evaluated against the fixture body that sourceId is pointing to. It is an error to define any combination of expression, headerField and path. TestScript.variable.sourceId (sourceId) is equivalent to TestScript.variable.sourceId Element `TestScript.variable.sourceId` is mapped to FHIR R4 element `TestScript.variable.sourceId` as `Equivalent`. This can be a statically defined fixture (at the top of the TestScript) or a dynamically set fixture created by responseId of the `action.operation` element. TestScript.setup (setup) maps to wider concept TestScript.setup Element `TestScript.setup` is mapped to FHIR R4 element `TestScript.setup` as `Equivalent`. TestScript.setup.action (action) maps to wider concept TestScript.setup.action Element `TestScript.setup.action` is mapped to FHIR R4 element `TestScript.setup.action` as `Equivalent`. An action should contain either an operation or an assertion but not both. It can contain any number of variables. TestScript.setup.action.operation (operation) maps to wider concept TestScript.setup.action.operation Element `TestScript.setup.action.operation` is mapped to FHIR R4 element `TestScript.setup.action.operation` as `Equivalent`. TestScript.setup.action.operation.type (type) is equivalent to TestScript.setup.action.operation.type Element `TestScript.setup.action.operation.type` is mapped to FHIR R4 element `TestScript.setup.action.operation.type` as `Equivalent`. See http://build.fhir.org/http.html for list of server interactions. TestScript.setup.action.operation.resource (resource) maps to wider concept TestScript.setup.action.operation.resource Element `TestScript.setup.action.operation.resource` is mapped to FHIR R4 element `TestScript.setup.action.operation.resource` as `RelatedTo`. The mappings for `TestScript.setup.action.operation.resource` do not allow expression of the necessary codes, per the bindings on the source and target. If "url" element is specified, then "targetId", "params", and "resource" elements will be ignored as "url" element will have everything needed for constructing the request url. If "params" element is specified, then "targetId" element is ignored. For FHIR operations that require a resource (e.g. "read" and "vread" operations), the "resource" element must be specified when "params" element is specified. If "url" and "params" elements are absent, then the request url will be constructed from "targetId" fixture if present. For "read" operation, the resource and id values will be extracted from "targetId" fixture and used to construct the url. For "vread" and "history" operations, the versionId value will also be used. TestScript.setup.action.operation.label (label) is equivalent to TestScript.setup.action.operation.label Element `TestScript.setup.action.operation.label` is mapped to FHIR R4 element `TestScript.setup.action.operation.label` as `Equivalent`. This has no impact on the verification itself. TestScript.setup.action.operation.description (description) is equivalent to TestScript.setup.action.operation.description Element `TestScript.setup.action.operation.description` is mapped to FHIR R4 element `TestScript.setup.action.operation.description` as `Equivalent`. This has no impact on the verification itself. TestScript.setup.action.operation.accept (accept) is equivalent to TestScript.setup.action.operation.accept Element `TestScript.setup.action.operation.accept` is mapped to FHIR R4 element `TestScript.setup.action.operation.accept` as `Equivalent`. If this is specified, then test engine shall set the 'Accept' header to the corresponding value. If you'd like to explicitly set the 'Accept' to some other value then use the 'requestHeader' element. TestScript.setup.action.operation.contentType (contentType) is equivalent to TestScript.setup.action.operation.contentType Element `TestScript.setup.action.operation.contentType` is mapped to FHIR R4 element `TestScript.setup.action.operation.contentType` as `Equivalent`. If this is specified, then test engine shall set the 'Content-Type' header to the corresponding value. If you'd like to explicitly set the 'Content-Type' to some other value then use the 'requestHeader' element. TestScript.setup.action.operation.destination (destination) is equivalent to TestScript.setup.action.operation.destination Element `TestScript.setup.action.operation.destination` is mapped to FHIR R4 element `TestScript.setup.action.operation.destination` as `Equivalent`. If multiple TestScript.destination elements are defined and operation.destination is undefined, test engine will report an error as it cannot determine what destination to use for the exchange. TestScript.setup.action.operation.encodeRequestUrl (encodeRequestUrl) is equivalent to TestScript.setup.action.operation.encodeRequestUrl Element `TestScript.setup.action.operation.encodeRequestUrl` is mapped to FHIR R4 element `TestScript.setup.action.operation.encodeRequestUrl` as `Equivalent`. TestScript.setup.action.operation.method (method) is equivalent to TestScript.setup.action.operation.method Element `TestScript.setup.action.operation.method` is mapped to FHIR R4 element `TestScript.setup.action.operation.method` as `Equivalent`. The primary purpose of the explicit HTTP method is support of HTTP POST method invocation of the FHIR search. Other uses will include support of negative testing. TestScript.setup.action.operation.origin (origin) is equivalent to TestScript.setup.action.operation.origin Element `TestScript.setup.action.operation.origin` is mapped to FHIR R4 element `TestScript.setup.action.operation.origin` as `Equivalent`. If absent, test engine will send the message. When present, test engine will not send the request message but will wait for the request message to be sent from this origin server. TestScript.setup.action.operation.params (params) is equivalent to TestScript.setup.action.operation.params Element `TestScript.setup.action.operation.params` is mapped to FHIR R4 element `TestScript.setup.action.operation.params` as `Equivalent`. If "url" element is specified, then "targetId", "params", and "resource" elements will be ignored as "url" element will have everything needed for constructing the request url. If "params" element is specified, then "targetId" element is ignored. For FHIR operations that require a resource (e.g. "read" and "vread" operations), the "resource" element must be specified when "params" element is specified. If "url" and "params" elements are absent, then the request url will be constructed from "targetId" fixture if present. For "read" operation, the resource and id values will be extracted from "targetId" fixture and used to construct the url. For "vread" and "history" operations, the versionId value will also be used. Test engines would append whatever is specified for "params" to the URL after the resource type without tampering with the string (beyond encoding the URL for HTTP). The "params" element does not correspond exactly to "search parameters". Nor is it the "path". It corresponds to the part of the URL that comes after the [type] (when "resource" element is specified); e.g. It corresponds to "/[id]/_history/[vid] {?_format=[mime-type]}" in the following operation: GET [base]/[type]/[id]/_history/[vid] {?_format=[mime-type]} Test engines do have to look for placeholders (${}) and replace the variable placeholders with the variable values at runtime before sending the request. TestScript.setup.action.operation.requestHeader (requestHeader) maps to wider concept TestScript.setup.action.operation.requestHeader Element `TestScript.setup.action.operation.requestHeader` is mapped to FHIR R4 element `TestScript.setup.action.operation.requestHeader` as `Equivalent`. This gives control to test-script writers to set headers explicitly based on test requirements. It will allow for testing using: - "If-Modified-Since" and "If-None-Match" headers. See http://build.fhir.org/http.html#2.1.0.5.1 - "If-Match" header. See http://build.fhir.org/http.html#2.1.0.11 - Conditional Create using "If-None-Exist". See http://build.fhir.org/http.html#2.1.0.13.1 - Invalid "Content-Type" header for negative testing. - etc. TestScript.setup.action.operation.requestHeader.field (field) is equivalent to TestScript.setup.action.operation.requestHeader.field Element `TestScript.setup.action.operation.requestHeader.field` is mapped to FHIR R4 element `TestScript.setup.action.operation.requestHeader.field` as `Equivalent`. If header element is specified, then field is required. TestScript.setup.action.operation.requestHeader.value (value) is equivalent to TestScript.setup.action.operation.requestHeader.value Element `TestScript.setup.action.operation.requestHeader.value` is mapped to FHIR R4 element `TestScript.setup.action.operation.requestHeader.value` as `Equivalent`. If header element is specified, then value is required. No conversions will be done by the test engine e.g. "xml" to "application/fhir+xml". The values will be set in HTTP headers "as-is". Test engines do have to look for placeholders (${}) and replace the variable placeholders with the variable values at runtime before sending the request. TestScript.setup.action.operation.requestId (requestId) is equivalent to TestScript.setup.action.operation.requestId Element `TestScript.setup.action.operation.requestId` is mapped to FHIR R4 element `TestScript.setup.action.operation.requestId` as `Equivalent`. If a requestId is supplied, then the resulting request (both headers and body) is mapped to the fixture ID (which may be entirely new and previously undeclared) designated by "requestId". If requestId is not specified, it is the test engine's responsibility to store the request and use it as the requestId in subsequent assertions when assertion path and/or headerField is specified, direction is equal to request, and the requestId in not specified. TestScript.setup.action.operation.responseId (responseId) is equivalent to TestScript.setup.action.operation.responseId Element `TestScript.setup.action.operation.responseId` is mapped to FHIR R4 element `TestScript.setup.action.operation.responseId` as `Equivalent`. If a responseId is supplied, and the server responds, then the resulting response (both headers and body) is mapped to the fixture ID (which may be entirely new and previously undeclared) designated by "responseId". If responseId is not specified, it is the test engine's responsibility to store the response and use it as the responseId in subsequent assertions when assertion path and/or headerField is specified and the responseId is not specified. TestScript.setup.action.operation.sourceId (sourceId) is equivalent to TestScript.setup.action.operation.sourceId Element `TestScript.setup.action.operation.sourceId` is mapped to FHIR R4 element `TestScript.setup.action.operation.sourceId` as `Equivalent`. TestScript.setup.action.operation.targetId (targetId) is equivalent to TestScript.setup.action.operation.targetId Element `TestScript.setup.action.operation.targetId` is mapped to FHIR R4 element `TestScript.setup.action.operation.targetId` as `Equivalent`. If "url" element is specified, then "targetId", "params", and "resource" elements will be ignored as "url" element will have everything needed for constructing the request url. If "params" element is specified, then "targetId" element is ignored. For FHIR operations that require a resource (e.g. "read" and "vread" operations), the "resource" element must be specified when "params" element is specified. If "url" and "params" elements are absent, then the request url will be constructed from "targetId" fixture if present. For "read" operation, the resource and id values will be extracted from "targetId" fixture and used to construct the url. For "vread" and "history" operations, the versionId value will also be used. TestScript.setup.action.operation.url (url) is equivalent to TestScript.setup.action.operation.url Element `TestScript.setup.action.operation.url` is mapped to FHIR R4 element `TestScript.setup.action.operation.url` as `Equivalent`. Used to set the request URL explicitly. If "url" element is defined, then "targetId", "resource", and "params" elements will be ignored. Test engines would use whatever is specified in "url" without tampering with the string (beyond encoding the URL for HTTP). Test engines do have to look for placeholders (${}) and replace the variable placeholders with the variable values at runtime before sending the request. TestScript.setup.action.assert (assert) maps to wider concept TestScript.setup.action.assert Element `TestScript.setup.action.assert` is mapped to FHIR R4 element `TestScript.setup.action.assert` as `Equivalent`. In order to evaluate an assertion, the request, response, and results of the most recently executed operation must always be maintained by the test engine. TestScript.setup.action.assert.label (label) is equivalent to TestScript.setup.action.assert.label Element `TestScript.setup.action.assert.label` is mapped to FHIR R4 element `TestScript.setup.action.assert.label` as `Equivalent`. This has no impact on the verification itself. TestScript.setup.action.assert.description (description) is equivalent to TestScript.setup.action.assert.description Element `TestScript.setup.action.assert.description` is mapped to FHIR R4 element `TestScript.setup.action.assert.description` as `Equivalent`. This has no impact on the verification itself. TestScript.setup.action.assert.direction (direction) is equivalent to TestScript.setup.action.assert.direction Element `TestScript.setup.action.assert.direction` is mapped to FHIR R4 element `TestScript.setup.action.assert.direction` as `Equivalent`. If the direction is specified as "response" (the default), then the processing of this assert is against the received response message. If the direction is specified as "request", then the processing of this assert is against the sent request message. TestScript.setup.action.assert.compareToSourceId (compareToSourceId) is equivalent to TestScript.setup.action.assert.compareToSourceId Element `TestScript.setup.action.assert.compareToSourceId` is mapped to FHIR R4 element `TestScript.setup.action.assert.compareToSourceId` as `Equivalent`. TestScript.setup.action.assert.compareToSourceExpression (compareToSourceExpression) is equivalent to TestScript.setup.action.assert.compareToSourceExpression Element `TestScript.setup.action.assert.compareToSourceExpression` is mapped to FHIR R4 element `TestScript.setup.action.assert.compareToSourceExpression` as `Equivalent`. Thefhirpath expression to be evaluated against the expected fixture to compare to. Ignored if "assert.value" is used. The evaluation will be done before the assertion is evaluated. TestScript.setup.action.assert.compareToSourcePath (compareToSourcePath) is equivalent to TestScript.setup.action.assert.compareToSourcePath Element `TestScript.setup.action.assert.compareToSourcePath` is mapped to FHIR R4 element `TestScript.setup.action.assert.compareToSourcePath` as `Equivalent`. The XPath or JSONPath expression to be evaluated against the expected fixture to compare to. Ignored if "assert.value" is used. The evaluation will be done before the assertion is evaluated. TestScript.setup.action.assert.contentType (contentType) is equivalent to TestScript.setup.action.assert.contentType Element `TestScript.setup.action.assert.contentType` is mapped to FHIR R4 element `TestScript.setup.action.assert.contentType` as `Equivalent`. If this is specified, then test engine shall confirm that the content-type of the last operation's headers is set to this value. If "assert.sourceId" element is specified, then the evaluation will be done against the headers mapped to that sourceId (and not the last operation's headers). If you'd like to have more control over the string, then use 'assert.headerField' instead. TestScript.setup.action.assert.expression (expression) is equivalent to TestScript.setup.action.assert.expression Element `TestScript.setup.action.assert.expression` is mapped to FHIR R4 element `TestScript.setup.action.assert.expression` as `Equivalent`. If both "expression" and a "fixtureId" are specified, then the expression will be evaluated against the request or response body mapped to the fixtureId. If "expression" is specified and a "fixtureId" is not, then the expression will be evaluated against the response body of the last operation. Test engines are to store the request and response body and headers of the last operation at all times for subsequent assertions. TestScript.setup.action.assert.headerField (headerField) is equivalent to TestScript.setup.action.assert.headerField Element `TestScript.setup.action.assert.headerField` is mapped to FHIR R4 element `TestScript.setup.action.assert.headerField` as `Equivalent`. If "headerField" is specified then "value" must be specified. If "sourceId" is not specified, then "headerField" will be evaluated against the last operation's response headers. Test engines are to keep track of the last operation's response body and response headers. TestScript.setup.action.assert.minimumId (minimumId) is equivalent to TestScript.setup.action.assert.minimumId Element `TestScript.setup.action.assert.minimumId` is mapped to FHIR R4 element `TestScript.setup.action.assert.minimumId` as `Equivalent`. Asserts that the response contains all the element/content in another fixture pointed to by minimumId. This can be a statically defined fixture or one that is dynamically set via responseId. TestScript.setup.action.assert.navigationLinks (navigationLinks) is equivalent to TestScript.setup.action.assert.navigationLinks Element `TestScript.setup.action.assert.navigationLinks` is mapped to FHIR R4 element `TestScript.setup.action.assert.navigationLinks` as `Equivalent`. Asserts that the Bundle contains first, last, and next links. TestScript.setup.action.assert.operator (operator) is equivalent to TestScript.setup.action.assert.operator Element `TestScript.setup.action.assert.operator` is mapped to FHIR R4 element `TestScript.setup.action.assert.operator` as `Equivalent`. Operators are useful especially for negative testing. If operator is not specified, then the "equals" operator is assumed; e.g. ``` <assert> <operator value="in" /> <responseCode value="200,201,204" /> </assert> <assert> <operator value="notEquals" /> <response value="okay"/> </assert> <assert> <operator value="greaterThan" /> <responseHeader> <field value="Content-Length" /> <value value="0" /> </responseHeader/> </assert> ```. TestScript.setup.action.assert.path (path) is equivalent to TestScript.setup.action.assert.path Element `TestScript.setup.action.assert.path` is mapped to FHIR R4 element `TestScript.setup.action.assert.path` as `Equivalent`. If both "path" and a "fixtureId" are specified, then the path will be evaluated against the request or response body mapped to the fixtureId. If "path" is specified and a "fixtureId" is not, then the path will be evaluated against the response body of the last operation. Test engines are to store the request and response body and headers of the last operation at all times for subsequent assertions. TestScript.setup.action.assert.requestMethod (requestMethod) is equivalent to TestScript.setup.action.assert.requestMethod Element `TestScript.setup.action.assert.requestMethod` is mapped to FHIR R4 element `TestScript.setup.action.assert.requestMethod` as `Equivalent`. If "requestMethod" is specified then it will be used in place of "value". The "requestMethod" will evaluate against the last operation's request HTTP operation. TestScript.setup.action.assert.requestURL (requestURL) is equivalent to TestScript.setup.action.assert.requestURL Element `TestScript.setup.action.assert.requestURL` is mapped to FHIR R4 element `TestScript.setup.action.assert.requestURL` as `Equivalent`. If "requestURL" is specified then it will be used in place of "value". The "requestURL" will evaluate against the last operation's full request URL path string. TestScript.setup.action.assert.resource (resource) maps to wider concept TestScript.setup.action.assert.resource Element `TestScript.setup.action.assert.resource` is mapped to FHIR R4 element `TestScript.setup.action.assert.resource` as `RelatedTo`. The mappings for `TestScript.setup.action.assert.resource` do not allow expression of the necessary codes, per the bindings on the source and target. This will be expected resource type in response body e.g. in read, vread, search, etc. See http://build.fhir.org/resourcelist.html for complete list of resource types; e.g. <assert > <resourceType value="Patient" </assert>. TestScript.setup.action.assert.response (response) is equivalent to TestScript.setup.action.assert.response Element `TestScript.setup.action.assert.response` is mapped to FHIR R4 element `TestScript.setup.action.assert.response` as `Equivalent`. This is a shorter way of achieving similar verifications via "assert.responseCode". If you need more control, then use "assert.responseCode" e.g. <assert> <contentType value="json" /> <response value="okay"/> </assert>. TestScript.setup.action.assert.responseCode (responseCode) is equivalent to TestScript.setup.action.assert.responseCode Element `TestScript.setup.action.assert.responseCode` is mapped to FHIR R4 element `TestScript.setup.action.assert.responseCode` as `Equivalent`. To be used with "operator" attribute value. Asserts that the response code equals this value if "operator" is not specified. If the operator is "in" or "notIn" then the responseCode would be a comma-separated list of values e.g. "200,201". Otherwise, it's expected to be a numeric value. If "fixture" is not specified, then the "responseBodyId" value of the last operation is assumed. TestScript.setup.action.assert.sourceId (sourceId) is equivalent to TestScript.setup.action.assert.sourceId Element `TestScript.setup.action.assert.sourceId` is mapped to FHIR R4 element `TestScript.setup.action.assert.sourceId` as `Equivalent`. This can be a statically defined fixture (at the top of the testscript) or a dynamically set fixture created by responseId of the action.operation element. TestScript.setup.action.assert.validateProfileId (validateProfileId) is equivalent to TestScript.setup.action.assert.validateProfileId Element `TestScript.setup.action.assert.validateProfileId` is mapped to FHIR R4 element `TestScript.setup.action.assert.validateProfileId` as `Equivalent`. The ID of a Profile fixture. Asserts that the response is valid according to the Profile specified by validateProfileId. TestScript.setup.action.assert.value (value) is equivalent to TestScript.setup.action.assert.value Element `TestScript.setup.action.assert.value` is mapped to FHIR R4 element `TestScript.setup.action.assert.value` as `Equivalent`. The string-representation of a number, string, or boolean that is expected. Test engines do have to look for placeholders (${}) and replace the variable placeholders with the variable values at runtime before comparing this value to the actual value. TestScript.setup.action.assert.warningOnly (warningOnly) is equivalent to TestScript.setup.action.assert.warningOnly Element `TestScript.setup.action.assert.warningOnly` is mapped to FHIR R4 element `TestScript.setup.action.assert.warningOnly` as `Equivalent`. If this element is specified and it is true, then assertion failures can be logged by test engine but should not stop the test script execution from proceeding. There are likely cases where the spec is not clear on what should happen. If the spec says something is optional (maybe a response header for example), but a server doesn’t do it, we could choose to issue a warning. TestScript.test (test) maps to wider concept TestScript.test Element `TestScript.test` is mapped to FHIR R4 element `TestScript.test` as `Equivalent`. TestScript.test.name (name) is equivalent to TestScript.test.name Element `TestScript.test.name` is mapped to FHIR R4 element `TestScript.test.name` as `Equivalent`. TestScript.test.description (description) is equivalent to TestScript.test.description Element `TestScript.test.description` is mapped to FHIR R4 element `TestScript.test.description` as `Equivalent`. TestScript.test.action (action) maps to wider concept TestScript.test.action Element `TestScript.test.action` is mapped to FHIR R4 element `TestScript.test.action` as `Equivalent`. An action should contain either an operation or an assertion but not both. It can contain any number of variables. TestScript.test.action.operation (operation) is equivalent to TestScript.test.action.operation Element `TestScript.test.action.operation` is mapped to FHIR R4 element `TestScript.test.action.operation` as `Equivalent`. TestScript.test.action.assert (assert) is equivalent to TestScript.test.action.assert Element `TestScript.test.action.assert` is mapped to FHIR R4 element `TestScript.test.action.assert` as `Equivalent`. In order to evaluate an assertion, the request, response, and results of the most recently executed operation must always be maintained by the test engine. TestScript.teardown (teardown) maps to wider concept TestScript.teardown Element `TestScript.teardown` is mapped to FHIR R4 element `TestScript.teardown` as `Equivalent`. TestScript.teardown.action (action) maps to wider concept TestScript.teardown.action Element `TestScript.teardown.action` is mapped to FHIR R4 element `TestScript.teardown.action` as `Equivalent`. An action should contain either an operation or an assertion but not both. It can contain any number of variables. TestScript.teardown.action.operation (operation) is equivalent to TestScript.teardown.action.operation Element `TestScript.teardown.action.operation` is mapped to FHIR R4 element `TestScript.teardown.action.operation` as `Equivalent`. Group 2 Mapping from http://hl7.org/fhir/StructureDefinition/TestScript|4.3.0 to R4B: resource additional codesversion: 0.1.0) Source Code Relationship Target Code Comment TestScript.setup.action.operation.resource (resource) is equivalent to Extension (R4B: resource additional codes) Element `TestScript.setup.action.operation.resource` is mapped to FHIR R4 element `TestScript.setup.action.operation.resource` as `RelatedTo`. The mappings for `TestScript.setup.action.operation.resource` do not allow expression of the necessary codes, per the bindings on the source and target. If "url" element is specified, then "targetId", "params", and "resource" elements will be ignored as "url" element will have everything needed for constructing the request url. If "params" element is specified, then "targetId" element is ignored. For FHIR operations that require a resource (e.g. "read" and "vread" operations), the "resource" element must be specified when "params" element is specified. If "url" and "params" elements are absent, then the request url will be constructed from "targetId" fixture if present. For "read" operation, the resource and id values will be extracted from "targetId" fixture and used to construct the url. For "vread" and "history" operations, the versionId value will also be used. Group 3 Mapping from http://hl7.org/fhir/StructureDefinition/TestScript|4.3.0 to R4B: resource additional codesversion: 0.1.0) Source Code Relationship Target Code Comment TestScript.setup.action.assert.resource (resource) is equivalent to Extension (R4B: resource additional codes) Element `TestScript.setup.action.assert.resource` is mapped to FHIR R4 element `TestScript.setup.action.assert.resource` as `RelatedTo`. The mappings for `TestScript.setup.action.assert.resource` do not allow expression of the necessary codes, per the bindings on the source and target. This will be expected resource type in response body e.g. in read, vread, search, etc. See http://build.fhir.org/resourcelist.html for complete list of resource types; e.g. <assert > <resourceType value="Patient" </assert>.
Cross-version mapping for FHIR R4B TestScript to FHIR R4 TestScript
This ConceptMap represents cross-version mappings for elements from a FHIR R4B TestScript to FHIR R4.
Element `TestScript.meta` is mapped to FHIR R4 element `TestScript.meta` as `Equivalent`.
Element `TestScript.implicitRules` is mapped to FHIR R4 element `TestScript.implicitRules` as `Equivalent`. Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of it's narrative along with other profiles, value sets, etc.
Element `TestScript.language` is mapped to FHIR R4 element `TestScript.language` as `Equivalent`. Language is provided to support indexing and accessibility (typically, services such as text to speech use the language tag). The html language tag in the narrative applies to the narrative. The language tag on the resource may be used to specify the language of other presentations generated from the data in the resource. Not all the content has to be in the base language. The Resource.language should not be assumed to apply to the narrative automatically. If a language is specified, it should it also be specified on the div element in the html (see rules in HTML5 for information about the relationship between xml:lang and the html lang attribute).
Element `TestScript.text` is mapped to FHIR R4 element `TestScript.text` as `Equivalent`. Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a "text blob" or where text is additionally entered raw or narrated and encoded information is added later.
Element `TestScript.contained` is mapped to FHIR R4 element `TestScript.contained` as `Equivalent`. This should never be done when the content can be identified properly, as once identification is lost, it is extremely difficult (and context dependent) to restore it again. Contained resources may have profiles and tags In their meta elements, but SHALL NOT have security labels.
Element `TestScript.url` is mapped to FHIR R4 element `TestScript.url` as `Equivalent`. Can be a urn:uuid: or a urn:oid: but real http: addresses are preferred. Multiple instances may share the same URL if they have a distinct version. The determination of when to create a new version of a resource (same url, new version) vs. defining a new artifact is up to the author. Considerations for making this decision are found in [Technical and Business Versions](https://hl7.org/fhir/resource..html#versions). In some cases, the resource can no longer be found at the stated url, but the url itself cannot change. Implementations can use the [meta.source](https://hl7.org/fhir/resou.html#meta) element to indicate where the current master source of the resource can be found.
Element `TestScript.identifier` is mapped to FHIR R4 element `TestScript.identifier` as `Equivalent`. Typically, this is used for identifiers that can go in an HL7 V3 II (instance identifier) data type, and can then identify this test script outside of FHIR, where it is not possible to use the logical URI.
Element `TestScript.version` is mapped to FHIR R4 element `TestScript.version` as `Equivalent`. There may be different test script instances that have the same identifier but different versions. The version can be appended to the url in a reference to allow a reference to a particular business version of the test script with the format [url]|[version].
Element `TestScript.name` is mapped to FHIR R4 element `TestScript.name` as `Equivalent`. The name is not expected to be globally unique. The name should be a simple alphanumeric type name to ensure that it is machine-processing friendly.
Element `TestScript.title` is mapped to FHIR R4 element `TestScript.title` as `Equivalent`. This name does not need to be machine-processing friendly and may contain punctuation, white-space, etc.
Element `TestScript.status` is mapped to FHIR R4 element `TestScript.status` as `Equivalent`. Allows filtering of test scripts that are appropriate for use versus not.
Element `TestScript.experimental` is mapped to FHIR R4 element `TestScript.experimental` as `Equivalent`. Allows filtering of test scripts that are appropriate for use versus not.
Element `TestScript.date` is mapped to FHIR R4 element `TestScript.date` as `Equivalent`. Note that this is not the same as the resource last-modified-date, since the resource may be a secondary representation of the test script. Additional specific dates may be added as extensions or be found by consulting Provenances associated with past versions of the resource.
Element `TestScript.publisher` is mapped to FHIR R4 element `TestScript.publisher` as `Equivalent`. Usually an organization but may be an individual. The publisher (or steward) of the test script is the organization or individual primarily responsible for the maintenance and upkeep of the test script. This is not necessarily the same individual or organization that developed and initially authored the content. The publisher is the primary point of contact for questions or issues with the test script. This item SHOULD be populated unless the information is available from context.
Element `TestScript.contact` is mapped to FHIR R4 element `TestScript.contact` as `Equivalent`. May be a web site, an email address, a telephone number, etc.
Element `TestScript.description` is mapped to FHIR R4 element `TestScript.description` as `Equivalent`. This description can be used to capture details such as why the test script was built, comments about misuse, instructions for clinical use and interpretation, literature references, examples from the paper world, etc. It is not a rendering of the test script as conveyed in the 'text' field of the resource itself. This item SHOULD be populated unless the information is available from context (e.g. the language of the test script is presumed to be the predominant language in the place the test script was created).
Element `TestScript.useContext` is mapped to FHIR R4 element `TestScript.useContext` as `Equivalent`. When multiple useContexts are specified, there is no expectation that all or any of the contexts apply.
Element `TestScript.jurisdiction` is mapped to FHIR R4 element `TestScript.jurisdiction` as `Equivalent`. It may be possible for the test script to be used in jurisdictions other than those for which it was originally designed or intended.
Element `TestScript.purpose` is mapped to FHIR R4 element `TestScript.purpose` as `Equivalent`. This element does not describe the usage of the test script. Instead, it provides traceability of ''why'' the resource is either needed or ''why'' it is defined as it is. This may be used to point to source materials or specifications that drove the structure of this test script.
Element `TestScript.copyright` is mapped to FHIR R4 element `TestScript.copyright` as `Equivalent`.
Element `TestScript.origin` is mapped to FHIR R4 element `TestScript.origin` as `Equivalent`. The purpose of this element is to define the profile of an origin element used elsewhere in the script. Test engines could then use the origin-profile mapping to offer a filtered list of test systems that can serve as the sender for the interaction.
Element `TestScript.origin.index` is mapped to FHIR R4 element `TestScript.origin.index` as `Equivalent`. A given origin index (e.g. 1) can appear only once in the list (e.g. Origin 1 cannot be specified twice ... once as FormFiller and again as FormProcessor within the same script as that could get confusing during test configuration). Different origin indices could play the same actor in the same test script (e.g. You could have two different test systems acting as Form-Filler). The origin indices provided elsewhere in the test script must be one of these origin indices.
Element `TestScript.origin.profile` is mapped to FHIR R4 element `TestScript.origin.profile` as `Equivalent`. Must be a "sender"/"client" profile.
Element `TestScript.destination` is mapped to FHIR R4 element `TestScript.destination` as `Equivalent`. The purpose of this element is to define the profile of a destination element used elsewhere in the script. Test engines could then use the destination-profile mapping to offer a filtered list of test systems that can serve as the receiver for the interaction.
Element `TestScript.destination.index` is mapped to FHIR R4 element `TestScript.destination.index` as `Equivalent`. A given destination index (e.g. 1) can appear only once in the list (e.g. Destination 1 cannot be specified twice ... once as Form-Manager and again as Form-Processor within the same script as that could get confusing during test configuration). Different destination indices could play the same actor in the same test script (e.g. You could have two different test systems acting as Form-Manager). The destination indices provided elsewhere in the test script must be one of these destination indices.
Element `TestScript.destination.profile` is mapped to FHIR R4 element `TestScript.destination.profile` as `Equivalent`. Must be a "receiver"/"server" profile.
Element `TestScript.metadata` is mapped to FHIR R4 element `TestScript.metadata` as `Equivalent`.
Element `TestScript.metadata.link` is mapped to FHIR R4 element `TestScript.metadata.link` as `Equivalent`.
Element `TestScript.metadata.link.url` is mapped to FHIR R4 element `TestScript.metadata.link.url` as `Equivalent`.
Element `TestScript.metadata.link.description` is mapped to FHIR R4 element `TestScript.metadata.link.description` as `Equivalent`.
Element `TestScript.metadata.capability` is mapped to FHIR R4 element `TestScript.metadata.capability` as `Equivalent`. When the metadata capabilities section is defined at TestScript.metadata 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 and the server's conformance statement does not contain the elements defined 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. They do not impact the skipping logic. Capabilities whose "metadata.capabilities.validated" flag is true are the primary focus of the test script.
Element `TestScript.metadata.capability.required` is mapped to FHIR R4 element `TestScript.metadata.capability.required` as `Equivalent`.
Element `TestScript.metadata.capability.validated` is mapped to FHIR R4 element `TestScript.metadata.capability.validated` as `Equivalent`.
Element `TestScript.metadata.capability.description` is mapped to FHIR R4 element `TestScript.metadata.capability.description` as `Equivalent`.
Element `TestScript.metadata.capability.origin` is mapped to FHIR R4 element `TestScript.metadata.capability.origin` as `Equivalent`.
Element `TestScript.metadata.capability.destination` is mapped to FHIR R4 element `TestScript.metadata.capability.destination` as `Equivalent`.
Element `TestScript.metadata.capability.link` is mapped to FHIR R4 element `TestScript.metadata.capability.link` as `Equivalent`.
Element `TestScript.metadata.capability.capabilities` is mapped to FHIR R4 element `TestScript.metadata.capability.capabilities` as `Equivalent`. The conformance statement of the server has to contain at a minimum the contents of the reference pointed to by this element.
Element `TestScript.fixture` is mapped to FHIR R4 element `TestScript.fixture` as `Equivalent`.
Element `TestScript.fixture.autocreate` is mapped to FHIR R4 element `TestScript.fixture.autocreate` as `Equivalent`.
Element `TestScript.fixture.autodelete` is mapped to FHIR R4 element `TestScript.fixture.autodelete` as `Equivalent`.
Element `TestScript.fixture.resource` is mapped to FHIR R4 element `TestScript.fixture.resource` as `Equivalent`. See http://build.fhir.org/resourcelist.html for complete list of resource types.
Element `TestScript.profile` is mapped to FHIR R4 element `TestScript.profile` as `Equivalent`. See http://build.fhir.org/resourcelist.html for complete list of resource types.
Element `TestScript.variable` is mapped to FHIR R4 element `TestScript.variable` as `Equivalent`. Variables would be set based either on XPath/JSONPath expressions against fixtures (static and response), or headerField evaluations against response headers. If variable evaluates to nodelist or anything other than a primitive value, then test engine would report an error. Variables would be used to perform clean replacements in "operation.params", "operation.requestHeader.value", and "operation.url" element values during operation calls and in "assert.value" during assertion evaluations. This limits the places that test engines would need to look for placeholders "${}". Variables are scoped to the whole script. They are NOT evaluated at declaration. They are evaluated by test engine when used for substitutions in "operation.params", "operation.requestHeader.value", and "operation.url" element values during operation calls and in "assert.value" during assertion evaluations. See example testscript-search.xml.
Element `TestScript.variable.name` is mapped to FHIR R4 element `TestScript.variable.name` as `Equivalent`. Placeholders would contain the variable name wrapped in ${} in "operation.params", "operation.requestHeader.value", and "operation.url" elements. These placeholders would need to be replaced by the variable value before the operation is executed.
Element `TestScript.variable.defaultValue` is mapped to FHIR R4 element `TestScript.variable.defaultValue` as `Equivalent`. The purpose of this element is to allow for a pre-defined value that can be used as a default or as an override value. Test engines can optionally use this as a placeholder for user-defined execution time values.
Element `TestScript.variable.description` is mapped to FHIR R4 element `TestScript.variable.description` as `Equivalent`.
Element `TestScript.variable.expression` is mapped to FHIR R4 element `TestScript.variable.expression` as `Equivalent`. If headerField is defined, then the variable will be evaluated against the headers that sourceId is pointing to. If expression or path is defined, then the variable will be evaluated against the fixture body that sourceId is pointing to. It is an error to define any combination of expression, headerField and path.
Element `TestScript.variable.headerField` is mapped to FHIR R4 element `TestScript.variable.headerField` as `Equivalent`. If headerField is defined, then the variable will be evaluated against the headers that sourceId is pointing to. If path is defined, then the variable will be evaluated against the fixture body that sourceId is pointing to. It is an error to define both headerField and path.
Element `TestScript.variable.hint` is mapped to FHIR R4 element `TestScript.variable.hint` as `Equivalent`.
Element `TestScript.variable.path` is mapped to FHIR R4 element `TestScript.variable.path` as `Equivalent`. If headerField is defined, then the variable will be evaluated against the headers that sourceId is pointing to. If expression or path is defined, then the variable will be evaluated against the fixture body that sourceId is pointing to. It is an error to define any combination of expression, headerField and path.
Element `TestScript.variable.sourceId` is mapped to FHIR R4 element `TestScript.variable.sourceId` as `Equivalent`. This can be a statically defined fixture (at the top of the TestScript) or a dynamically set fixture created by responseId of the `action.operation` element.
Element `TestScript.setup` is mapped to FHIR R4 element `TestScript.setup` as `Equivalent`.
Element `TestScript.setup.action` is mapped to FHIR R4 element `TestScript.setup.action` as `Equivalent`. An action should contain either an operation or an assertion but not both. It can contain any number of variables.
Element `TestScript.setup.action.operation` is mapped to FHIR R4 element `TestScript.setup.action.operation` as `Equivalent`.
Element `TestScript.setup.action.operation.type` is mapped to FHIR R4 element `TestScript.setup.action.operation.type` as `Equivalent`. See http://build.fhir.org/http.html for list of server interactions.
Element `TestScript.setup.action.operation.resource` is mapped to FHIR R4 element `TestScript.setup.action.operation.resource` as `RelatedTo`. The mappings for `TestScript.setup.action.operation.resource` do not allow expression of the necessary codes, per the bindings on the source and target. If "url" element is specified, then "targetId", "params", and "resource" elements will be ignored as "url" element will have everything needed for constructing the request url. If "params" element is specified, then "targetId" element is ignored. For FHIR operations that require a resource (e.g. "read" and "vread" operations), the "resource" element must be specified when "params" element is specified. If "url" and "params" elements are absent, then the request url will be constructed from "targetId" fixture if present. For "read" operation, the resource and id values will be extracted from "targetId" fixture and used to construct the url. For "vread" and "history" operations, the versionId value will also be used.
Element `TestScript.setup.action.operation.label` is mapped to FHIR R4 element `TestScript.setup.action.operation.label` as `Equivalent`. This has no impact on the verification itself.
Element `TestScript.setup.action.operation.description` is mapped to FHIR R4 element `TestScript.setup.action.operation.description` as `Equivalent`. This has no impact on the verification itself.
Element `TestScript.setup.action.operation.accept` is mapped to FHIR R4 element `TestScript.setup.action.operation.accept` as `Equivalent`. If this is specified, then test engine shall set the 'Accept' header to the corresponding value. If you'd like to explicitly set the 'Accept' to some other value then use the 'requestHeader' element.
Element `TestScript.setup.action.operation.contentType` is mapped to FHIR R4 element `TestScript.setup.action.operation.contentType` as `Equivalent`. If this is specified, then test engine shall set the 'Content-Type' header to the corresponding value. If you'd like to explicitly set the 'Content-Type' to some other value then use the 'requestHeader' element.
Element `TestScript.setup.action.operation.destination` is mapped to FHIR R4 element `TestScript.setup.action.operation.destination` as `Equivalent`. If multiple TestScript.destination elements are defined and operation.destination is undefined, test engine will report an error as it cannot determine what destination to use for the exchange.
Element `TestScript.setup.action.operation.encodeRequestUrl` is mapped to FHIR R4 element `TestScript.setup.action.operation.encodeRequestUrl` as `Equivalent`.
Element `TestScript.setup.action.operation.method` is mapped to FHIR R4 element `TestScript.setup.action.operation.method` as `Equivalent`. The primary purpose of the explicit HTTP method is support of HTTP POST method invocation of the FHIR search. Other uses will include support of negative testing.
Element `TestScript.setup.action.operation.origin` is mapped to FHIR R4 element `TestScript.setup.action.operation.origin` as `Equivalent`. If absent, test engine will send the message. When present, test engine will not send the request message but will wait for the request message to be sent from this origin server.
Element `TestScript.setup.action.operation.params` is mapped to FHIR R4 element `TestScript.setup.action.operation.params` as `Equivalent`. If "url" element is specified, then "targetId", "params", and "resource" elements will be ignored as "url" element will have everything needed for constructing the request url. If "params" element is specified, then "targetId" element is ignored. For FHIR operations that require a resource (e.g. "read" and "vread" operations), the "resource" element must be specified when "params" element is specified. If "url" and "params" elements are absent, then the request url will be constructed from "targetId" fixture if present. For "read" operation, the resource and id values will be extracted from "targetId" fixture and used to construct the url. For "vread" and "history" operations, the versionId value will also be used. Test engines would append whatever is specified for "params" to the URL after the resource type without tampering with the string (beyond encoding the URL for HTTP). The "params" element does not correspond exactly to "search parameters". Nor is it the "path". It corresponds to the part of the URL that comes after the [type] (when "resource" element is specified); e.g. It corresponds to "/[id]/_history/[vid] {?_format=[mime-type]}" in the following operation: GET [base]/[type]/[id]/_history/[vid] {?_format=[mime-type]} Test engines do have to look for placeholders (${}) and replace the variable placeholders with the variable values at runtime before sending the request.
Element `TestScript.setup.action.operation.requestHeader` is mapped to FHIR R4 element `TestScript.setup.action.operation.requestHeader` as `Equivalent`. This gives control to test-script writers to set headers explicitly based on test requirements. It will allow for testing using: - "If-Modified-Since" and "If-None-Match" headers. See http://build.fhir.org/http.html#2.1.0.5.1 - "If-Match" header. See http://build.fhir.org/http.html#2.1.0.11 - Conditional Create using "If-None-Exist". See http://build.fhir.org/http.html#2.1.0.13.1 - Invalid "Content-Type" header for negative testing. - etc.
Element `TestScript.setup.action.operation.requestHeader.field` is mapped to FHIR R4 element `TestScript.setup.action.operation.requestHeader.field` as `Equivalent`. If header element is specified, then field is required.
Element `TestScript.setup.action.operation.requestHeader.value` is mapped to FHIR R4 element `TestScript.setup.action.operation.requestHeader.value` as `Equivalent`. If header element is specified, then value is required. No conversions will be done by the test engine e.g. "xml" to "application/fhir+xml". The values will be set in HTTP headers "as-is". Test engines do have to look for placeholders (${}) and replace the variable placeholders with the variable values at runtime before sending the request.
Element `TestScript.setup.action.operation.requestId` is mapped to FHIR R4 element `TestScript.setup.action.operation.requestId` as `Equivalent`. If a requestId is supplied, then the resulting request (both headers and body) is mapped to the fixture ID (which may be entirely new and previously undeclared) designated by "requestId". If requestId is not specified, it is the test engine's responsibility to store the request and use it as the requestId in subsequent assertions when assertion path and/or headerField is specified, direction is equal to request, and the requestId in not specified.
Element `TestScript.setup.action.operation.responseId` is mapped to FHIR R4 element `TestScript.setup.action.operation.responseId` as `Equivalent`. If a responseId is supplied, and the server responds, then the resulting response (both headers and body) is mapped to the fixture ID (which may be entirely new and previously undeclared) designated by "responseId". If responseId is not specified, it is the test engine's responsibility to store the response and use it as the responseId in subsequent assertions when assertion path and/or headerField is specified and the responseId is not specified.
Element `TestScript.setup.action.operation.sourceId` is mapped to FHIR R4 element `TestScript.setup.action.operation.sourceId` as `Equivalent`.
Element `TestScript.setup.action.operation.targetId` is mapped to FHIR R4 element `TestScript.setup.action.operation.targetId` as `Equivalent`. If "url" element is specified, then "targetId", "params", and "resource" elements will be ignored as "url" element will have everything needed for constructing the request url. If "params" element is specified, then "targetId" element is ignored. For FHIR operations that require a resource (e.g. "read" and "vread" operations), the "resource" element must be specified when "params" element is specified. If "url" and "params" elements are absent, then the request url will be constructed from "targetId" fixture if present. For "read" operation, the resource and id values will be extracted from "targetId" fixture and used to construct the url. For "vread" and "history" operations, the versionId value will also be used.
Element `TestScript.setup.action.operation.url` is mapped to FHIR R4 element `TestScript.setup.action.operation.url` as `Equivalent`. Used to set the request URL explicitly. If "url" element is defined, then "targetId", "resource", and "params" elements will be ignored. Test engines would use whatever is specified in "url" without tampering with the string (beyond encoding the URL for HTTP). Test engines do have to look for placeholders (${}) and replace the variable placeholders with the variable values at runtime before sending the request.
Element `TestScript.setup.action.assert` is mapped to FHIR R4 element `TestScript.setup.action.assert` as `Equivalent`. In order to evaluate an assertion, the request, response, and results of the most recently executed operation must always be maintained by the test engine.
Element `TestScript.setup.action.assert.label` is mapped to FHIR R4 element `TestScript.setup.action.assert.label` as `Equivalent`. This has no impact on the verification itself.
Element `TestScript.setup.action.assert.description` is mapped to FHIR R4 element `TestScript.setup.action.assert.description` as `Equivalent`. This has no impact on the verification itself.
Element `TestScript.setup.action.assert.direction` is mapped to FHIR R4 element `TestScript.setup.action.assert.direction` as `Equivalent`. If the direction is specified as "response" (the default), then the processing of this assert is against the received response message. If the direction is specified as "request", then the processing of this assert is against the sent request message.
Element `TestScript.setup.action.assert.compareToSourceId` is mapped to FHIR R4 element `TestScript.setup.action.assert.compareToSourceId` as `Equivalent`.
Element `TestScript.setup.action.assert.compareToSourceExpression` is mapped to FHIR R4 element `TestScript.setup.action.assert.compareToSourceExpression` as `Equivalent`. Thefhirpath expression to be evaluated against the expected fixture to compare to. Ignored if "assert.value" is used. The evaluation will be done before the assertion is evaluated.
Element `TestScript.setup.action.assert.compareToSourcePath` is mapped to FHIR R4 element `TestScript.setup.action.assert.compareToSourcePath` as `Equivalent`. The XPath or JSONPath expression to be evaluated against the expected fixture to compare to. Ignored if "assert.value" is used. The evaluation will be done before the assertion is evaluated.
Element `TestScript.setup.action.assert.contentType` is mapped to FHIR R4 element `TestScript.setup.action.assert.contentType` as `Equivalent`. If this is specified, then test engine shall confirm that the content-type of the last operation's headers is set to this value. If "assert.sourceId" element is specified, then the evaluation will be done against the headers mapped to that sourceId (and not the last operation's headers). If you'd like to have more control over the string, then use 'assert.headerField' instead.
Element `TestScript.setup.action.assert.expression` is mapped to FHIR R4 element `TestScript.setup.action.assert.expression` as `Equivalent`. If both "expression" and a "fixtureId" are specified, then the expression will be evaluated against the request or response body mapped to the fixtureId. If "expression" is specified and a "fixtureId" is not, then the expression will be evaluated against the response body of the last operation. Test engines are to store the request and response body and headers of the last operation at all times for subsequent assertions.
Element `TestScript.setup.action.assert.headerField` is mapped to FHIR R4 element `TestScript.setup.action.assert.headerField` as `Equivalent`. If "headerField" is specified then "value" must be specified. If "sourceId" is not specified, then "headerField" will be evaluated against the last operation's response headers. Test engines are to keep track of the last operation's response body and response headers.
Element `TestScript.setup.action.assert.minimumId` is mapped to FHIR R4 element `TestScript.setup.action.assert.minimumId` as `Equivalent`. Asserts that the response contains all the element/content in another fixture pointed to by minimumId. This can be a statically defined fixture or one that is dynamically set via responseId.
Element `TestScript.setup.action.assert.navigationLinks` is mapped to FHIR R4 element `TestScript.setup.action.assert.navigationLinks` as `Equivalent`. Asserts that the Bundle contains first, last, and next links.
Element `TestScript.setup.action.assert.operator` is mapped to FHIR R4 element `TestScript.setup.action.assert.operator` as `Equivalent`. Operators are useful especially for negative testing. If operator is not specified, then the "equals" operator is assumed; e.g. ``` <assert> <operator value="in" /> <responseCode value="200,201,204" /> </assert> <assert> <operator value="notEquals" /> <response value="okay"/> </assert> <assert> <operator value="greaterThan" /> <responseHeader> <field value="Content-Length" /> <value value="0" /> </responseHeader/> </assert> ```.
Element `TestScript.setup.action.assert.path` is mapped to FHIR R4 element `TestScript.setup.action.assert.path` as `Equivalent`. If both "path" and a "fixtureId" are specified, then the path will be evaluated against the request or response body mapped to the fixtureId. If "path" is specified and a "fixtureId" is not, then the path will be evaluated against the response body of the last operation. Test engines are to store the request and response body and headers of the last operation at all times for subsequent assertions.
Element `TestScript.setup.action.assert.requestMethod` is mapped to FHIR R4 element `TestScript.setup.action.assert.requestMethod` as `Equivalent`. If "requestMethod" is specified then it will be used in place of "value". The "requestMethod" will evaluate against the last operation's request HTTP operation.
Element `TestScript.setup.action.assert.requestURL` is mapped to FHIR R4 element `TestScript.setup.action.assert.requestURL` as `Equivalent`. If "requestURL" is specified then it will be used in place of "value". The "requestURL" will evaluate against the last operation's full request URL path string.
Element `TestScript.setup.action.assert.resource` is mapped to FHIR R4 element `TestScript.setup.action.assert.resource` as `RelatedTo`. The mappings for `TestScript.setup.action.assert.resource` do not allow expression of the necessary codes, per the bindings on the source and target. This will be expected resource type in response body e.g. in read, vread, search, etc. See http://build.fhir.org/resourcelist.html for complete list of resource types; e.g. <assert > <resourceType value="Patient" </assert>.
Element `TestScript.setup.action.assert.response` is mapped to FHIR R4 element `TestScript.setup.action.assert.response` as `Equivalent`. This is a shorter way of achieving similar verifications via "assert.responseCode". If you need more control, then use "assert.responseCode" e.g. <assert> <contentType value="json" /> <response value="okay"/> </assert>.
Element `TestScript.setup.action.assert.responseCode` is mapped to FHIR R4 element `TestScript.setup.action.assert.responseCode` as `Equivalent`. To be used with "operator" attribute value. Asserts that the response code equals this value if "operator" is not specified. If the operator is "in" or "notIn" then the responseCode would be a comma-separated list of values e.g. "200,201". Otherwise, it's expected to be a numeric value. If "fixture" is not specified, then the "responseBodyId" value of the last operation is assumed.
Element `TestScript.setup.action.assert.sourceId` is mapped to FHIR R4 element `TestScript.setup.action.assert.sourceId` as `Equivalent`. This can be a statically defined fixture (at the top of the testscript) or a dynamically set fixture created by responseId of the action.operation element.
Element `TestScript.setup.action.assert.validateProfileId` is mapped to FHIR R4 element `TestScript.setup.action.assert.validateProfileId` as `Equivalent`. The ID of a Profile fixture. Asserts that the response is valid according to the Profile specified by validateProfileId.
Element `TestScript.setup.action.assert.value` is mapped to FHIR R4 element `TestScript.setup.action.assert.value` as `Equivalent`. The string-representation of a number, string, or boolean that is expected. Test engines do have to look for placeholders (${}) and replace the variable placeholders with the variable values at runtime before comparing this value to the actual value.
Element `TestScript.setup.action.assert.warningOnly` is mapped to FHIR R4 element `TestScript.setup.action.assert.warningOnly` as `Equivalent`. If this element is specified and it is true, then assertion failures can be logged by test engine but should not stop the test script execution from proceeding. There are likely cases where the spec is not clear on what should happen. If the spec says something is optional (maybe a response header for example), but a server doesn’t do it, we could choose to issue a warning.
Element `TestScript.test` is mapped to FHIR R4 element `TestScript.test` as `Equivalent`.
Element `TestScript.test.name` is mapped to FHIR R4 element `TestScript.test.name` as `Equivalent`.
Element `TestScript.test.description` is mapped to FHIR R4 element `TestScript.test.description` as `Equivalent`.
Element `TestScript.test.action` is mapped to FHIR R4 element `TestScript.test.action` as `Equivalent`. An action should contain either an operation or an assertion but not both. It can contain any number of variables.
Element `TestScript.test.action.operation` is mapped to FHIR R4 element `TestScript.test.action.operation` as `Equivalent`.
Element `TestScript.test.action.assert` is mapped to FHIR R4 element `TestScript.test.action.assert` as `Equivalent`. In order to evaluate an assertion, the request, response, and results of the most recently executed operation must always be maintained by the test engine.
Element `TestScript.teardown` is mapped to FHIR R4 element `TestScript.teardown` as `Equivalent`.
Element `TestScript.teardown.action` is mapped to FHIR R4 element `TestScript.teardown.action` as `Equivalent`. An action should contain either an operation or an assertion but not both. It can contain any number of variables.
Element `TestScript.teardown.action.operation` is mapped to FHIR R4 element `TestScript.teardown.action.operation` as `Equivalent`.