Generated Narrative: ConceptMap R2-TestScript-element-map-to-R5 Mapping from http://hl7.org/fhir/1.0 to http://hl7.org/fhir/5.0 Group 1 Mapping from http://hl7.org/fhir/StructureDefinition/TestScript|1.0.2 to TestScriptversion: 5.0.0) Source Code Relationship Target Code Comment TestScript.meta (meta) is broader than TestScript.meta Element `TestScript.meta` is mapped to FHIR R5 element `TestScript.meta` as `SourceIsBroaderThanTarget`. The mappings for `TestScript.meta` do not cover the following types: Meta. The mappings for `TestScript.meta` do not cover the following types based on type expansion: lastUpdated, profile, security, tag, versionId. TestScript.implicitRules (implicitRules) is equivalent to TestScript.implicitRules Element `TestScript.implicitRules` is mapped to FHIR R5 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 as much as possible. TestScript.language (language) is equivalent to TestScript.language Element `TestScript.language` is mapped to FHIR R5 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 broader than TestScript.text Element `TestScript.text` is mapped to FHIR R5 element `TestScript.text` as `SourceIsBroaderThanTarget`. The mappings for `TestScript.text` do not cover the following types: Narrative. The mappings for `TestScript.text` do not cover the following types based on type expansion: div, status. Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative. TestScript.contained (contained) is equivalent to TestScript.contained Element `TestScript.contained` is mapped to FHIR R5 element `TestScript.contained` as `SourceIsBroaderThanTarget`. 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. TestScript.url (url) is equivalent to TestScript.url Element `TestScript.url` is mapped to FHIR R5 element `TestScript.url` as `Equivalent`. TestScript.version (version) is equivalent to TestScript.version Element `TestScript.version` is mapped to FHIR R5 element `TestScript.version` as `Equivalent`. TestScript.name (name) is equivalent to TestScript.name Element `TestScript.name` is mapped to FHIR R5 element `TestScript.name` as `Equivalent`. Not expected to be globally unique. TestScript.status (status) is equivalent to TestScript.status Element `TestScript.status` is mapped to FHIR R5 element `TestScript.status` as `SourceIsNarrowerThanTarget`. The mappings for `TestScript.status` do not allow expression of the necessary codes, per the bindings on the source and target. TestScript.identifier (identifier) is broader than TestScript.identifier Element `TestScript.identifier` is mapped to FHIR R5 element `TestScript.identifier` as `RelatedTo`. The mappings for `TestScript.identifier` do not cover the following types: Identifier. The mappings for `TestScript.identifier` do not cover the following types based on type expansion: assigner, period, system, type, use, value. TestScript.experimental (experimental) is equivalent to TestScript.experimental Element `TestScript.experimental` is mapped to FHIR R5 element `TestScript.experimental` as `Equivalent`. TestScript.publisher (publisher) is equivalent to TestScript.publisher Element `TestScript.publisher` is mapped to FHIR R5 element `TestScript.publisher` as `Equivalent`. Usually an organization, but may be an individual. This item SHOULD be populated unless the information is available from context. TestScript.contact (contact) is broader than TestScript.contact Element `TestScript.contact` is mapped to FHIR R5 element `TestScript.contact` as `Equivalent`. May be a web site, an email address, a telephone number (tel:), etc. TestScript.date (date) is equivalent to TestScript.date Element `TestScript.date` is mapped to FHIR R5 element `TestScript.date` as `Equivalent`. Additional specific dates may be added as extensions. TestScript.description (description) is equivalent to TestScript.description Element `TestScript.description` is mapped to FHIR R5 element `TestScript.description` as `Equivalent`. This field can be used for things such as why the TestScript was written, comments about misuse, instructions for clinical use and interpretation, literature references, examples from the paper world, etc. It is *not* a rendering of the TestScript as conveyed in TestScript.text. This item SHOULD be populated unless the information is available from context. TestScript.useContext (useContext) is broader than TestScript.useContext Element `TestScript.useContext` is mapped to FHIR R5 element `TestScript.useContext` as `SourceIsBroaderThanTarget`. The mappings for `TestScript.useContext` do not cover the following types: CodeableConcept. The mappings for `TestScript.useContext` do not cover the following types based on type expansion: coding, text. TestScript.requirements (requirements) is equivalent to TestScript.purpose Element `TestScript.requirements` is mapped to FHIR R5 element `TestScript.purpose` as `Equivalent`. This element does not describe the usage of the Test Script (that's done in comments), rather it's for traceability of *why* the element is either needed or why the constraints exist as they do. This may be used to point to source materials or specifications that drove the structure of this data element. TestScript.copyright (copyright) is equivalent to TestScript.copyright Element `TestScript.copyright` is mapped to FHIR R5 element `TestScript.copyright` as `Equivalent`. TestScript.metadata (metadata) is broader than TestScript.metadata Element `TestScript.metadata` is mapped to FHIR R5 element `TestScript.metadata` as `Equivalent`. TestScript.metadata.link (link) is broader than TestScript.metadata.link Element `TestScript.metadata.link` is mapped to FHIR R5 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 R5 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 R5 element `TestScript.metadata.link.description` as `Equivalent`. TestScript.metadata.capability (capability) is broader than TestScript.metadata.capability Element `TestScript.metadata.capability` is mapped to FHIR R5 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. The 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 R5 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 R5 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 R5 element `TestScript.metadata.capability.description` as `Equivalent`. TestScript.metadata.capability.destination (destination) is equivalent to TestScript.metadata.capability.destination Element `TestScript.metadata.capability.destination` is mapped to FHIR R5 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 R5 element `TestScript.metadata.capability.link` as `Equivalent`. TestScript.metadata.capability.conformance (conformance) is broader than TestScript.metadata.capability.capabilities Element `TestScript.metadata.capability.conformance` is mapped to FHIR R5 element `TestScript.metadata.capability.capabilities` as `SourceIsBroaderThanTarget`. The mappings for `TestScript.metadata.capability.conformance` do not cover the following types: Reference. The mappings for `TestScript.metadata.capability.conformance` do not cover the following types based on type expansion: display, reference. 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) is broader than TestScript.fixture Element `TestScript.fixture` is mapped to FHIR R5 element `TestScript.fixture` as `Equivalent`. TestScript.fixture.autocreate (autocreate) is equivalent to TestScript.fixture.autocreate Element `TestScript.fixture.autocreate` is mapped to FHIR R5 element `TestScript.fixture.autocreate` as `Equivalent`. TestScript.fixture.autodelete (autodelete) is equivalent to TestScript.fixture.autodelete Element `TestScript.fixture.autodelete` is mapped to FHIR R5 element `TestScript.fixture.autodelete` as `Equivalent`. TestScript.fixture.resource (resource) is broader than TestScript.fixture.resource Element `TestScript.fixture.resource` is mapped to FHIR R5 element `TestScript.fixture.resource` as `SourceIsBroaderThanTarget`. The mappings for `TestScript.fixture.resource` do not cover the following types based on type expansion: display, reference. The standard extension `alternate-reference` has been mapped as the representation of FHIR DSTU2 element `TestScript.fixture.resource` with unmapped reference targets: Resource. See http://hl7-fhir.github.io/resourcelist.html for complete list of resource types. TestScript.profile (profile) is broader than TestScript.profile Element `TestScript.profile` is mapped to FHIR R5 element `TestScript.profile` as `SourceIsBroaderThanTarget`. The mappings for `TestScript.profile` do not cover the following types: Reference. The mappings for `TestScript.profile` do not cover the following types based on type expansion: display, reference. See http://hl7-fhir.github.io/resourcelist.html for complete list of resource types. TestScript.variable (variable) is broader than TestScript.variable Element `TestScript.variable` is mapped to FHIR R5 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 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 R5 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.headerField (headerField) is equivalent to TestScript.variable.headerField Element `TestScript.variable.headerField` is mapped to FHIR R5 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.path (path) is equivalent to TestScript.variable.path Element `TestScript.variable.path` is mapped to FHIR R5 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 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.sourceId (sourceId) is equivalent to TestScript.variable.sourceId Element `TestScript.variable.sourceId` is mapped to FHIR R5 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) is broader than TestScript.setup Element `TestScript.setup` is mapped to FHIR R5 element `TestScript.setup` as `Equivalent`. TestScript.setup.action (action) is broader than TestScript.setup.action Element `TestScript.setup.action` is mapped to FHIR R5 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) is broader than TestScript.setup.action.operation Element `TestScript.setup.action.operation` is mapped to FHIR R5 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 R5 element `TestScript.setup.action.operation.type` as `Equivalent`. See http://hl7-fhir.github.io/http.html for list of server interactions. TestScript.setup.action.operation.resource (resource) is broader than TestScript.setup.action.operation.resource Element `TestScript.setup.action.operation.resource` is mapped to FHIR R5 element `TestScript.setup.action.operation.resource` as `RelatedTo`. The mappings for `TestScript.setup.action.operation.resource` do not cover the following types: code. The mappings for `TestScript.setup.action.operation.resource` do not cover the following types based on type expansion: value. 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 R5 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 R5 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 R5 element `TestScript.setup.action.operation.accept` as `SourceIsNarrowerThanTarget`. If this is specified, then test engine shall set the 'Accept' header to the corresponding value. If 'xml' is specified, then 'Accept' header of 'application/xml+fhir' will be set. If 'json' is specified, then 'application/json+fhir' will be used. 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 R5 element `TestScript.setup.action.operation.contentType` as `SourceIsNarrowerThanTarget`. If this is specified, then test engine shall set the 'Content-Type' header to the corresponding value. If 'xml' is specified, then 'Content-Type' header of 'application/xml+fhir' will be set. If 'json' is specified, then 'application/json+fhir' will be used. 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 R5 element `TestScript.setup.action.operation.destination` as `Equivalent`. TestScript.setup.action.operation.encodeRequestUrl (encodeRequestUrl) is equivalent to TestScript.setup.action.operation.encodeRequestUrl Element `TestScript.setup.action.operation.encodeRequestUrl` is mapped to FHIR R5 element `TestScript.setup.action.operation.encodeRequestUrl` as `Equivalent`. TestScript.setup.action.operation.params (params) is equivalent to TestScript.setup.action.operation.params Element `TestScript.setup.action.operation.params` is mapped to FHIR R5 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) is broader than TestScript.setup.action.operation.requestHeader Element `TestScript.setup.action.operation.requestHeader` is mapped to FHIR R5 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://hl7-fhir.github.io/http.html#2.1.0.5.1 - "If-Match" header. See http://hl7-fhir.github.io/http.html#2.1.0.11 - Conditional Create using "If-None-Exist". See http://hl7-fhir.github.io/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 R5 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 R5 element `TestScript.setup.action.operation.requestHeader.value` as `Equivalent`. If header element is specified, then value is required. No conversions will be done by Test Engine e.g. "xml" to "application/xml+fhir". 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.responseId (responseId) is equivalent to TestScript.setup.action.operation.responseId Element `TestScript.setup.action.operation.responseId` is mapped to FHIR R5 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 sourceId in subsequent assertions when assertion path and/or headerField is specified and sourceId 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 R5 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 R5 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 R5 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) is broader than TestScript.setup.action.assert Element `TestScript.setup.action.assert` is mapped to FHIR R5 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 R5 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 R5 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 R5 element `TestScript.setup.action.assert.direction` as `Equivalent`. TestScript.setup.action.assert.compareToSourceId (compareToSourceId) is equivalent to TestScript.setup.action.assert.compareToSourceId Element `TestScript.setup.action.assert.compareToSourceId` is mapped to FHIR R5 element `TestScript.setup.action.assert.compareToSourceId` as `Equivalent`. The id of the fixture used to make comparisons to. TestScript.setup.action.assert.compareToSourcePath (compareToSourcePath) is equivalent to TestScript.setup.action.assert.compareToSourcePath Element `TestScript.setup.action.assert.compareToSourcePath` is mapped to FHIR R5 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 R5 element `TestScript.setup.action.assert.contentType` as `SourceIsNarrowerThanTarget`. 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 'xml' is specified, then 'Content-Type' header of 'application/xml+fhir' will be confirmed. If 'json' is specified, then 'application/json+fhir' will be used. If you'd like to have more control over the string, then use 'assert.headerField' instead. TestScript.setup.action.assert.headerField (headerField) is equivalent to TestScript.setup.action.assert.headerField Element `TestScript.setup.action.assert.headerField` is mapped to FHIR R5 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 R5 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 R5 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 R5 element `TestScript.setup.action.assert.operator` as `SourceIsNarrowerThanTarget`. The mappings for `TestScript.setup.action.assert.operator` do not allow expression of the necessary codes, per the bindings on the source and target. Operators come handy 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 R5 element `TestScript.setup.action.assert.path` as `Equivalent`. If both "path" and "fixtureId" are specified, then the path will be evaluated against the responseBody mapped to the fixtureId. If "path" is specified and "fixtureId" is not, then the path will be evaluated against the responseBody of the last operation. Test engines are to store the response body and headers of the last operation at all times for subsequent assertions. TestScript.setup.action.assert.resource (resource) is broader than TestScript.setup.action.assert.resource Element `TestScript.setup.action.assert.resource` is mapped to FHIR R5 element `TestScript.setup.action.assert.resource` as `RelatedTo`. The mappings for `TestScript.setup.action.assert.resource` do not cover the following types: code. The mappings for `TestScript.setup.action.assert.resource` do not cover the following types based on type expansion: value. This will be expected resource type in response body e.g. in read, vread, search, etc. See http://hl7-fhir.github.io/resourcelist.html for complete list of resource types; e.g. <assert > <resourceType value="Patient" </assert>. TestScript.setup.action.assert.response (response) is broader than TestScript.setup.action.assert.response Element `TestScript.setup.action.assert.response` is mapped to FHIR R5 element `TestScript.setup.action.assert.response` as `RelatedTo`. The mappings for `TestScript.setup.action.assert.response` do not allow expression of the necessary codes, per the bindings on the source and target. 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 R5 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 R5 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 R5 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 R5 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 R5 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) is broader than TestScript.test Element `TestScript.test` is mapped to FHIR R5 element `TestScript.test` as `Equivalent`. TestScript.test.name (name) is equivalent to TestScript.test.name Element `TestScript.test.name` is mapped to FHIR R5 element `TestScript.test.name` as `Equivalent`. TestScript.test.description (description) is equivalent to TestScript.test.description Element `TestScript.test.description` is mapped to FHIR R5 element `TestScript.test.description` as `Equivalent`. TestScript.test.action (action) is broader than TestScript.test.action Element `TestScript.test.action` is mapped to FHIR R5 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 R5 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 R5 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) is broader than TestScript.teardown Element `TestScript.teardown` is mapped to FHIR R5 element `TestScript.teardown` as `Equivalent`. TestScript.teardown.action (action) is broader than TestScript.teardown.action Element `TestScript.teardown.action` is mapped to FHIR R5 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 R5 element `TestScript.teardown.action.operation` as `Equivalent`. Group 2 Mapping from http://hl7.org/fhir/StructureDefinition/TestScript|1.0.2 to DSTU2: meta additional typesversion: 0.1.0) Source Code Relationship Target Code Comment TestScript.meta (meta) is equivalent to Extension (DSTU2: meta additional types) Element `TestScript.meta` is mapped to FHIR R5 element `TestScript.meta` as `SourceIsBroaderThanTarget`. The mappings for `TestScript.meta` do not cover the following types: Meta. The mappings for `TestScript.meta` do not cover the following types based on type expansion: lastUpdated, profile, security, tag, versionId. Group 3 Mapping from http://hl7.org/fhir/StructureDefinition/TestScript|1.0.2 to DSTU2: text additional typesversion: 0.1.0) Source Code Relationship Target Code Comment TestScript.text (text) is equivalent to Extension (DSTU2: text additional types) Element `TestScript.text` is mapped to FHIR R5 element `TestScript.text` as `SourceIsBroaderThanTarget`. The mappings for `TestScript.text` do not cover the following types: Narrative. The mappings for `TestScript.text` do not cover the following types based on type expansion: div, status. Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative. Group 4 Mapping from http://hl7.org/fhir/StructureDefinition/TestScript|1.0.2 to DSTU2: External identifier additional typesversion: 0.1.0) Source Code Relationship Target Code Comment TestScript.identifier (identifier) is equivalent to Extension (DSTU2: External identifier additional types) Element `TestScript.identifier` is mapped to FHIR R5 element `TestScript.identifier` as `RelatedTo`. The mappings for `TestScript.identifier` do not cover the following types: Identifier. The mappings for `TestScript.identifier` do not cover the following types based on type expansion: assigner, period, system, type, use, value. Group 5 Mapping from http://hl7.org/fhir/StructureDefinition/TestScript|1.0.2 to DSTU2: Name of a individual to contact (new)version: 0.1.0) Source Code Relationship Target Code Comment TestScript.contact.name (name) is broader than Extension (DSTU2: Name of a individual to contact (new)) Element `TestScript.contact.name` has a context of TestScript.contact based on following the parent source element upwards and mapping to `TestScript`. Element `TestScript.contact.name` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element). If there is no named individual, the telecom is for the organization as a whole. Group 6 Mapping from http://hl7.org/fhir/StructureDefinition/TestScript|1.0.2 to DSTU2: Contact details for individual or publisher (new)version: 0.1.0) Source Code Relationship Target Code Comment TestScript.contact.telecom (telecom) is broader than Extension (DSTU2: Contact details for individual or publisher (new)) Element `TestScript.contact.telecom` has a context of TestScript.contact based on following the parent source element upwards and mapping to `TestScript`. Element `TestScript.contact.telecom` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element). Group 7 Mapping from http://hl7.org/fhir/StructureDefinition/TestScript|1.0.2 to DSTU2: Content intends to support these contexts additional typesversion: 0.1.0) Source Code Relationship Target Code Comment TestScript.useContext (useContext) is equivalent to Extension (DSTU2: Content intends to support these contexts additional types) Element `TestScript.useContext` is mapped to FHIR R5 element `TestScript.useContext` as `SourceIsBroaderThanTarget`. The mappings for `TestScript.useContext` do not cover the following types: CodeableConcept. The mappings for `TestScript.useContext` do not cover the following types based on type expansion: coding, text. Group 8 Mapping from http://hl7.org/fhir/StructureDefinition/TestScript|1.0.2 to DSTU2: metadataversion: 0.1.0) Source Code Relationship Target Code Comment TestScript.metadata (metadata) is equivalent to Extension (DSTU2: metadata) Element `TestScript.metadata` is mapped to FHIR R5 element `TestScript.metadata` as `Equivalent`. TestScript.metadata.link (link) is equivalent to Extension.extension:link (DSTU2: link) Element `TestScript.metadata.link` is mapped to FHIR R5 element `TestScript.metadata.link` as `Equivalent`. TestScript.metadata.link.url (url) is equivalent to Extension.extension:link.extension:url (DSTU2: url) Element `TestScript.metadata.link.url` is mapped to FHIR R5 element `TestScript.metadata.link.url` as `Equivalent`. TestScript.metadata.link.description (description) is equivalent to Extension.extension:link.extension:description (DSTU2: description) Element `TestScript.metadata.link.description` is mapped to FHIR R5 element `TestScript.metadata.link.description` as `Equivalent`. TestScript.metadata.capability (capability) is equivalent to Extension.extension:capability (DSTU2: capability) Element `TestScript.metadata.capability` is mapped to FHIR R5 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. The 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 Extension.extension:capability.extension:required (DSTU2: required) Element `TestScript.metadata.capability.required` is mapped to FHIR R5 element `TestScript.metadata.capability.required` as `Equivalent`. TestScript.metadata.capability.validated (validated) is equivalent to Extension.extension:capability.extension:validated (DSTU2: validated) Element `TestScript.metadata.capability.validated` is mapped to FHIR R5 element `TestScript.metadata.capability.validated` as `Equivalent`. TestScript.metadata.capability.description (description) is equivalent to Extension.extension:capability.extension:description (DSTU2: description) Element `TestScript.metadata.capability.description` is mapped to FHIR R5 element `TestScript.metadata.capability.description` as `Equivalent`. TestScript.metadata.capability.destination (destination) is equivalent to Extension.extension:capability.extension:destination (DSTU2: destination) Element `TestScript.metadata.capability.destination` is mapped to FHIR R5 element `TestScript.metadata.capability.destination` as `Equivalent`. TestScript.metadata.capability.link (link) is equivalent to Extension.extension:capability.extension:link (DSTU2: link) Element `TestScript.metadata.capability.link` is mapped to FHIR R5 element `TestScript.metadata.capability.link` as `Equivalent`. TestScript.metadata.capability.conformance (conformance) is broader than Extension.extension:capability.extension:conformance (DSTU2: Required Conformance additional types) Element `TestScript.metadata.capability.conformance` is mapped to FHIR R5 element `TestScript.metadata.capability.capabilities` as `SourceIsBroaderThanTarget`. The mappings for `TestScript.metadata.capability.conformance` do not cover the following types: Reference. The mappings for `TestScript.metadata.capability.conformance` do not cover the following types based on type expansion: display, reference. The conformance statement of the server has to contain at a minimum the contents of the reference pointed to by this element. Group 9 Mapping from http://hl7.org/fhir/StructureDefinition/TestScript|1.0.2 to DSTU2: Required Conformance additional typesversion: 0.1.0) Source Code Relationship Target Code Comment TestScript.metadata.capability.conformance (conformance) is broader than Extension (DSTU2: Required Conformance additional types) Element `TestScript.metadata.capability.conformance` is mapped to FHIR R5 element `TestScript.metadata.capability.capabilities` as `SourceIsBroaderThanTarget`. The mappings for `TestScript.metadata.capability.conformance` do not cover the following types: Reference. The mappings for `TestScript.metadata.capability.conformance` do not cover the following types based on type expansion: display, reference. The conformance statement of the server has to contain at a minimum the contents of the reference pointed to by this element. Group 10 Mapping from http://hl7.org/fhir/StructureDefinition/TestScript|1.0.2 to DSTU2: Whether or not the tests apply to more than one FHIR server (new)version: 0.1.0) Source Code Relationship Target Code Comment TestScript.multiserver (multiserver) is equivalent to Extension (DSTU2: Whether or not the tests apply to more than one FHIR server (new)) Element `TestScript.multiserver` has a context of TestScript based on following the parent source element upwards and mapping to `TestScript`. Element `TestScript.multiserver` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element). Group 11 Mapping from http://hl7.org/fhir/StructureDefinition/TestScript|1.0.2 to DSTU2: profile additional typesversion: 0.1.0) Source Code Relationship Target Code Comment TestScript.profile (profile) is equivalent to Extension (DSTU2: profile additional types) Element `TestScript.profile` is mapped to FHIR R5 element `TestScript.profile` as `SourceIsBroaderThanTarget`. The mappings for `TestScript.profile` do not cover the following types: Reference. The mappings for `TestScript.profile` do not cover the following types based on type expansion: display, reference. See http://hl7-fhir.github.io/resourcelist.html for complete list of resource types. Group 12 Mapping from http://hl7.org/fhir/StructureDefinition/TestScript|1.0.2 to DSTU2: resource additional typesversion: 0.1.0) Source Code Relationship Target Code Comment TestScript.setup.action.operation.resource (resource) is equivalent to Extension (DSTU2: resource additional types) Element `TestScript.setup.action.operation.resource` is mapped to FHIR R5 element `TestScript.setup.action.operation.resource` as `RelatedTo`. The mappings for `TestScript.setup.action.operation.resource` do not cover the following types: code. The mappings for `TestScript.setup.action.operation.resource` do not cover the following types based on type expansion: value. 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 13 Mapping from http://hl7.org/fhir/StructureDefinition/TestScript|1.0.2 to DSTU2: resource additional typesversion: 0.1.0) Source Code Relationship Target Code Comment TestScript.setup.action.assert.resource (resource) is equivalent to Extension (DSTU2: resource additional types) Element `TestScript.setup.action.assert.resource` is mapped to FHIR R5 element `TestScript.setup.action.assert.resource` as `RelatedTo`. The mappings for `TestScript.setup.action.assert.resource` do not cover the following types: code. The mappings for `TestScript.setup.action.assert.resource` do not cover the following types based on type expansion: value. This will be expected resource type in response body e.g. in read, vread, search, etc. See http://hl7-fhir.github.io/resourcelist.html for complete list of resource types; e.g. <assert > <resourceType value="Patient" </assert>. Group 14 Mapping from http://hl7.org/fhir/StructureDefinition/TestScript|1.0.2 to DSTU2: okay | created | noContent | notModified | bad | forbidden | notFound | methodNotAllowed | conflict | gone | preconditionFailed | unprocessable additional codesversion: 0.1.0) Source Code Relationship Target Code Comment TestScript.setup.action.assert.response (response) is equivalent to Extension (DSTU2: okay | created | noContent | notModified | bad | forbidden | notFound | methodNotAllowed | conflict | gone | preconditionFailed | unprocessable additional codes) Element `TestScript.setup.action.assert.response` is mapped to FHIR R5 element `TestScript.setup.action.assert.response` as `RelatedTo`. The mappings for `TestScript.setup.action.assert.response` do not allow expression of the necessary codes, per the bindings on the source and target. 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>.
Cross-version mapping for FHIR DSTU2 TestScript to FHIR R5 TestScript
This ConceptMap represents cross-version mappings for elements from a FHIR DSTU2 TestScript to FHIR R5.
Element `TestScript.meta` is mapped to FHIR R5 element `TestScript.meta` as `SourceIsBroaderThanTarget`. The mappings for `TestScript.meta` do not cover the following types: Meta. The mappings for `TestScript.meta` do not cover the following types based on type expansion: lastUpdated, profile, security, tag, versionId.
Element `TestScript.implicitRules` is mapped to FHIR R5 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 as much as possible.
Element `TestScript.language` is mapped to FHIR R5 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 R5 element `TestScript.text` as `SourceIsBroaderThanTarget`. The mappings for `TestScript.text` do not cover the following types: Narrative. The mappings for `TestScript.text` do not cover the following types based on type expansion: div, status. Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative.
Element `TestScript.contained` is mapped to FHIR R5 element `TestScript.contained` as `SourceIsBroaderThanTarget`. 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.
Element `TestScript.url` is mapped to FHIR R5 element `TestScript.url` as `Equivalent`.
Element `TestScript.version` is mapped to FHIR R5 element `TestScript.version` as `Equivalent`.
Element `TestScript.name` is mapped to FHIR R5 element `TestScript.name` as `Equivalent`. Not expected to be globally unique.
Element `TestScript.status` is mapped to FHIR R5 element `TestScript.status` as `SourceIsNarrowerThanTarget`. The mappings for `TestScript.status` do not allow expression of the necessary codes, per the bindings on the source and target.
Element `TestScript.identifier` is mapped to FHIR R5 element `TestScript.identifier` as `RelatedTo`. The mappings for `TestScript.identifier` do not cover the following types: Identifier. The mappings for `TestScript.identifier` do not cover the following types based on type expansion: assigner, period, system, type, use, value.
Element `TestScript.experimental` is mapped to FHIR R5 element `TestScript.experimental` as `Equivalent`.
Element `TestScript.publisher` is mapped to FHIR R5 element `TestScript.publisher` as `Equivalent`. Usually an organization, but may be an individual. This item SHOULD be populated unless the information is available from context.
Element `TestScript.contact` is mapped to FHIR R5 element `TestScript.contact` as `Equivalent`. May be a web site, an email address, a telephone number (tel:), etc.
Element `TestScript.date` is mapped to FHIR R5 element `TestScript.date` as `Equivalent`. Additional specific dates may be added as extensions.
Element `TestScript.description` is mapped to FHIR R5 element `TestScript.description` as `Equivalent`. This field can be used for things such as why the TestScript was written, comments about misuse, instructions for clinical use and interpretation, literature references, examples from the paper world, etc. It is *not* a rendering of the TestScript as conveyed in TestScript.text. This item SHOULD be populated unless the information is available from context.
Element `TestScript.useContext` is mapped to FHIR R5 element `TestScript.useContext` as `SourceIsBroaderThanTarget`. The mappings for `TestScript.useContext` do not cover the following types: CodeableConcept. The mappings for `TestScript.useContext` do not cover the following types based on type expansion: coding, text.
Element `TestScript.requirements` is mapped to FHIR R5 element `TestScript.purpose` as `Equivalent`. This element does not describe the usage of the Test Script (that's done in comments), rather it's for traceability of *why* the element is either needed or why the constraints exist as they do. This may be used to point to source materials or specifications that drove the structure of this data element.
Element `TestScript.copyright` is mapped to FHIR R5 element `TestScript.copyright` as `Equivalent`.
Element `TestScript.metadata` is mapped to FHIR R5 element `TestScript.metadata` as `Equivalent`.
Element `TestScript.metadata.link` is mapped to FHIR R5 element `TestScript.metadata.link` as `Equivalent`.
Element `TestScript.metadata.link.url` is mapped to FHIR R5 element `TestScript.metadata.link.url` as `Equivalent`.
Element `TestScript.metadata.link.description` is mapped to FHIR R5 element `TestScript.metadata.link.description` as `Equivalent`.
Element `TestScript.metadata.capability` is mapped to FHIR R5 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. The 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 R5 element `TestScript.metadata.capability.required` as `Equivalent`.
Element `TestScript.metadata.capability.validated` is mapped to FHIR R5 element `TestScript.metadata.capability.validated` as `Equivalent`.
Element `TestScript.metadata.capability.description` is mapped to FHIR R5 element `TestScript.metadata.capability.description` as `Equivalent`.
Element `TestScript.metadata.capability.destination` is mapped to FHIR R5 element `TestScript.metadata.capability.destination` as `Equivalent`.
Element `TestScript.metadata.capability.link` is mapped to FHIR R5 element `TestScript.metadata.capability.link` as `Equivalent`.
Element `TestScript.metadata.capability.conformance` is mapped to FHIR R5 element `TestScript.metadata.capability.capabilities` as `SourceIsBroaderThanTarget`. The mappings for `TestScript.metadata.capability.conformance` do not cover the following types: Reference. The mappings for `TestScript.metadata.capability.conformance` do not cover the following types based on type expansion: display, reference. 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 R5 element `TestScript.fixture` as `Equivalent`.
Element `TestScript.fixture.autocreate` is mapped to FHIR R5 element `TestScript.fixture.autocreate` as `Equivalent`.
Element `TestScript.fixture.autodelete` is mapped to FHIR R5 element `TestScript.fixture.autodelete` as `Equivalent`.
Element `TestScript.fixture.resource` is mapped to FHIR R5 element `TestScript.fixture.resource` as `SourceIsBroaderThanTarget`. The mappings for `TestScript.fixture.resource` do not cover the following types based on type expansion: display, reference. The standard extension `alternate-reference` has been mapped as the representation of FHIR DSTU2 element `TestScript.fixture.resource` with unmapped reference targets: Resource. See http://hl7-fhir.github.io/resourcelist.html for complete list of resource types.
Element `TestScript.profile` is mapped to FHIR R5 element `TestScript.profile` as `SourceIsBroaderThanTarget`. The mappings for `TestScript.profile` do not cover the following types: Reference. The mappings for `TestScript.profile` do not cover the following types based on type expansion: display, reference. See http://hl7-fhir.github.io/resourcelist.html for complete list of resource types.
Element `TestScript.variable` is mapped to FHIR R5 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 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 R5 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.headerField` is mapped to FHIR R5 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.path` is mapped to FHIR R5 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 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.sourceId` is mapped to FHIR R5 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 R5 element `TestScript.setup` as `Equivalent`.
Element `TestScript.setup.action` is mapped to FHIR R5 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 R5 element `TestScript.setup.action.operation` as `Equivalent`.
Element `TestScript.setup.action.operation.type` is mapped to FHIR R5 element `TestScript.setup.action.operation.type` as `Equivalent`. See http://hl7-fhir.github.io/http.html for list of server interactions.
Element `TestScript.setup.action.operation.resource` is mapped to FHIR R5 element `TestScript.setup.action.operation.resource` as `RelatedTo`. The mappings for `TestScript.setup.action.operation.resource` do not cover the following types: code. The mappings for `TestScript.setup.action.operation.resource` do not cover the following types based on type expansion: value. 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 R5 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 R5 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 R5 element `TestScript.setup.action.operation.accept` as `SourceIsNarrowerThanTarget`. If this is specified, then test engine shall set the 'Accept' header to the corresponding value. If 'xml' is specified, then 'Accept' header of 'application/xml+fhir' will be set. If 'json' is specified, then 'application/json+fhir' will be used. 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 R5 element `TestScript.setup.action.operation.contentType` as `SourceIsNarrowerThanTarget`. If this is specified, then test engine shall set the 'Content-Type' header to the corresponding value. If 'xml' is specified, then 'Content-Type' header of 'application/xml+fhir' will be set. If 'json' is specified, then 'application/json+fhir' will be used. 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 R5 element `TestScript.setup.action.operation.destination` as `Equivalent`.
Element `TestScript.setup.action.operation.encodeRequestUrl` is mapped to FHIR R5 element `TestScript.setup.action.operation.encodeRequestUrl` as `Equivalent`.
Element `TestScript.setup.action.operation.params` is mapped to FHIR R5 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 R5 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://hl7-fhir.github.io/http.html#2.1.0.5.1 - "If-Match" header. See http://hl7-fhir.github.io/http.html#2.1.0.11 - Conditional Create using "If-None-Exist". See http://hl7-fhir.github.io/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 R5 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 R5 element `TestScript.setup.action.operation.requestHeader.value` as `Equivalent`. If header element is specified, then value is required. No conversions will be done by Test Engine e.g. "xml" to "application/xml+fhir". 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.responseId` is mapped to FHIR R5 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 sourceId in subsequent assertions when assertion path and/or headerField is specified and sourceId is not specified.
Element `TestScript.setup.action.operation.sourceId` is mapped to FHIR R5 element `TestScript.setup.action.operation.sourceId` as `Equivalent`.
Element `TestScript.setup.action.operation.targetId` is mapped to FHIR R5 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 R5 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 R5 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 R5 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 R5 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 R5 element `TestScript.setup.action.assert.direction` as `Equivalent`.
Element `TestScript.setup.action.assert.compareToSourceId` is mapped to FHIR R5 element `TestScript.setup.action.assert.compareToSourceId` as `Equivalent`. The id of the fixture used to make comparisons to.
Element `TestScript.setup.action.assert.compareToSourcePath` is mapped to FHIR R5 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 R5 element `TestScript.setup.action.assert.contentType` as `SourceIsNarrowerThanTarget`. 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 'xml' is specified, then 'Content-Type' header of 'application/xml+fhir' will be confirmed. If 'json' is specified, then 'application/json+fhir' will be used. If you'd like to have more control over the string, then use 'assert.headerField' instead.
Element `TestScript.setup.action.assert.headerField` is mapped to FHIR R5 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 R5 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 R5 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 R5 element `TestScript.setup.action.assert.operator` as `SourceIsNarrowerThanTarget`. The mappings for `TestScript.setup.action.assert.operator` do not allow expression of the necessary codes, per the bindings on the source and target. Operators come handy 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 R5 element `TestScript.setup.action.assert.path` as `Equivalent`. If both "path" and "fixtureId" are specified, then the path will be evaluated against the responseBody mapped to the fixtureId. If "path" is specified and "fixtureId" is not, then the path will be evaluated against the responseBody of the last operation. Test engines are to store the response body and headers of the last operation at all times for subsequent assertions.
Element `TestScript.setup.action.assert.resource` is mapped to FHIR R5 element `TestScript.setup.action.assert.resource` as `RelatedTo`. The mappings for `TestScript.setup.action.assert.resource` do not cover the following types: code. The mappings for `TestScript.setup.action.assert.resource` do not cover the following types based on type expansion: value. This will be expected resource type in response body e.g. in read, vread, search, etc. See http://hl7-fhir.github.io/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 R5 element `TestScript.setup.action.assert.response` as `RelatedTo`. The mappings for `TestScript.setup.action.assert.response` do not allow expression of the necessary codes, per the bindings on the source and target. 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 R5 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 R5 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 R5 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 R5 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 R5 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 R5 element `TestScript.test` as `Equivalent`.
Element `TestScript.test.name` is mapped to FHIR R5 element `TestScript.test.name` as `Equivalent`.
Element `TestScript.test.description` is mapped to FHIR R5 element `TestScript.test.description` as `Equivalent`.
Element `TestScript.test.action` is mapped to FHIR R5 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 R5 element `TestScript.test.action.operation` as `Equivalent`.
Element `TestScript.test.action.assert` is mapped to FHIR R5 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 R5 element `TestScript.teardown` as `Equivalent`.
Element `TestScript.teardown.action` is mapped to FHIR R5 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 R5 element `TestScript.teardown.action.operation` as `Equivalent`.
Element `TestScript.contact.name` has a context of TestScript.contact based on following the parent source element upwards and mapping to `TestScript`. Element `TestScript.contact.name` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element). If there is no named individual, the telecom is for the organization as a whole.
Element `TestScript.contact.telecom` has a context of TestScript.contact based on following the parent source element upwards and mapping to `TestScript`. Element `TestScript.contact.telecom` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element).
Element `TestScript.multiserver` has a context of TestScript based on following the parent source element upwards and mapping to `TestScript`. Element `TestScript.multiserver` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element).