R2-TestScript-element-map-to-R5
type: ConceptMap
node role: treeRoot
id:
  v: R2-TestScript-element-map-to-R5
text:
  status:
    v: generated
  div:
    v: 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…
extension:
  url:
    v: http://hl7.org/fhir/StructureDefinition/structuredefinition-wg
    l: structuredefinition-wg
  value: Code
    v: fhir
extension:
  url:
    v: http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm
    l: structuredefinition-fmm
  value: Integer
    v: 0
    extension:
      url:
        v: http://hl7.org/fhir/StructureDefinition/structuredefinition-conformance-derivedFrom
        l: structuredefinition-conformance-derivedFrom
      value: Canonical
        v: http://hl7.org/fhir/uv/xver/ImplementationGuide/hl7.fhir.uv.xver-r2.r5
        l: hl7.fhir.uv.xver-r2.r5
extension:
  url:
    v: http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status
    l: structuredefinition-standards-status
  value: Code
    v: trial-use
    extension:
      url:
        v: http://hl7.org/fhir/StructureDefinition/structuredefinition-conformance-derivedFrom
        l: structuredefinition-conformance-derivedFrom
      value: Canonical
        v: http://hl7.org/fhir/uv/xver/ImplementationGuide/hl7.fhir.uv.xver-r2.r5
        l: hl7.fhir.uv.xver-r2.r5
url:
  v: http://hl7.org/fhir/uv/xver/ConceptMap/R2-TestScript-element-map-to-R5
  l: R2-TestScript-element-map-to-R5
version:
  v: 0.1.0
name:
  v: R2TestScriptElementMapToR5
title:
  v: Cross-version mapping for FHIR DSTU2 TestScript to FHIR R5 TestScript
status:
  v: active
experimental:
  v: false
date:
  v: 2026-03-17T16:05:26.5006898-05:00
contact:
  name:
    v: FHIR Infrastructure
  telecom:
    system:
      v: url
    value:
      v: http://www.hl7.org/Special/committees/fiwg
description:
  v: This ConceptMap represents cross-version mappings for elements from a FHIR DSTU2 TestScript to FHIR R5.
jurisdiction:
  coding:
    system:
      v: http://unstats.un.org/unsd/methods/m49/m49.htm
      l: m49.htm
    code:
      v: 001
    display:
      v: World
source scope: Canonical
  v: http://hl7.org/fhir/1.0
  l: http://hl7.org/fhir/1.0
target scope: Uri
  v: http://hl7.org/fhir/5.0
  l: http://hl7.org/fhir/5.0
group:
  source:
    v: http://hl7.org/fhir/StructureDefinition/TestScript|1.0.2
    l: http://hl7.org/fhir/StructureDefinition/TestScript
  target:
    v: http://hl7.org/fhir/StructureDefinition/TestScript|5.0.0
    l: http://hl7.org/fhir/StructureDefinition/TestScript
  element:
    code:
      v: TestScript.meta
    display:
      v: meta
    target:
      code:
        v: TestScript.meta
      display:
        v: TestScript.meta
      relationship:
        v: source-is-broader-than-target
      comment:
        v: 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:
    code:
      v: TestScript.implicitRules
    display:
      v: implicitRules
    target:
      code:
        v: TestScript.implicitRules
      display:
        v: TestScript.implicitRules
      relationship:
        v: equivalent
      comment:
        v: 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:
    code:
      v: TestScript.language
    display:
      v: language
    target:
      code:
        v: TestScript.language
      display:
        v: TestScript.language
      relationship:
        v: equivalent
      comment:
        v: 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:
    code:
      v: TestScript.text
    display:
      v: text
    target:
      code:
        v: TestScript.text
      display:
        v: TestScript.text
      relationship:
        v: source-is-broader-than-target
      comment:
        v: 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:
    code:
      v: TestScript.contained
    display:
      v: contained
    target:
      code:
        v: TestScript.contained
      display:
        v: TestScript.contained
      relationship:
        v: equivalent
      comment:
        v: 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:
    code:
      v: TestScript.url
    display:
      v: url
    target:
      code:
        v: TestScript.url
      display:
        v: TestScript.url
      relationship:
        v: equivalent
      comment:
        v: Element `TestScript.url` is mapped to FHIR R5 element `TestScript.url` as `Equivalent`.
  element:
    code:
      v: TestScript.version
    display:
      v: version
    target:
      code:
        v: TestScript.version
      display:
        v: TestScript.version
      relationship:
        v: equivalent
      comment:
        v: Element `TestScript.version` is mapped to FHIR R5 element `TestScript.version` as `Equivalent`.
  element:
    code:
      v: TestScript.name
    display:
      v: name
    target:
      code:
        v: TestScript.name
      display:
        v: TestScript.name
      relationship:
        v: equivalent
      comment:
        v: Element `TestScript.name` is mapped to FHIR R5 element `TestScript.name` as `Equivalent`. Not expected to be globally unique.
  element:
    code:
      v: TestScript.status

v: status

code:
  v: TestScript.status
display:
  v: TestScript.status
relationship:
  v: equivalent
comment:
  v: 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.

code:
  v: TestScript.identifier
display:
  v: identifier
target:
  code:
    v: TestScript.identifier
  display:
    v: TestScript.identifier
  relationship:
    v: source-is-broader-than-target
  comment:
    v: 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.

code:
  v: TestScript.experimental
display:
  v: experimental
target:
  code:
    v: TestScript.experimental
  display:
    v: TestScript.experimental
  relationship:
    v: equivalent
  comment:
    v: Element `TestScript.experimental` is mapped to FHIR R5 element `TestScript.experimental` as `Equivalent`.

code:
  v: TestScript.publisher
display:
  v: publisher
target:
  code:
    v: TestScript.publisher
  display:
    v: TestScript.publisher
  relationship:
    v: equivalent
  comment:
    v: 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.

code:
  v: TestScript.contact
display:
  v: contact
target:
  code:
    v: TestScript.contact
  display:
    v: TestScript.contact
  relationship:
    v: source-is-broader-than-target
  comment:
    v: 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.

code:
  v: TestScript.date
display:
  v: date
target:
  code:
    v: TestScript.date
  display:
    v: TestScript.date
  relationship:
    v: equivalent
  comment:
    v: Element `TestScript.date` is mapped to FHIR R5 element `TestScript.date` as `Equivalent`. Additional specific dates may be added as extensions.

code:
  v: TestScript.description
display:
  v: description
target:
  code:
    v: TestScript.description
  display:
    v: TestScript.description
  relationship:
    v: equivalent
  comment:
    v: 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.

code:
  v: TestScript.useContext
display:
  v: useContext
target:
  code:
    v: TestScript.useContext
  display:
    v: TestScript.useContext
  relationship:
    v: source-is-broader-than-target
  comment:
    v: 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.

code:
  v: TestScript.requirements
display:
  v: requirements
target:
  code:
    v: TestScript.purpose
  display:
    v: TestScript.purpose
  relationship:
    v: equivalent
  comment:
    v: 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.

code:
  v: TestScript.copyright
display:
  v: copyright
target:
  code:
    v: TestScript.copyright
  display:
    v: TestScript.copyright
  relationship:
    v: equivalent
  comment:
    v: Element `TestScript.copyright` is mapped to FHIR R5 element `TestScript.copyright` as `Equivalent`.

code:
  v: TestScript.metadata
display:
  v: metadata
target:
  code:
    v: TestScript.metadata
  display:
    v: TestScript.metadata
  relationship:
    v: source-is-broader-than-target
  comment:
    v: Element `TestScript.metadata` is mapped to FHIR R5 element `TestScript.metadata` as `Equivalent`.

code:
  v: TestScript.metadata.link
display:
  v: link
target:
  code:
    v: TestScript.metadata.link
  display:
    v: TestScript.metadata.link
  relationship:
    v: source-is-broader-than-target
  comment:
    v: Element `TestScript.metadata.link` is mapped to FHIR R5 element `TestScript.metadata.link` as `Equivalent`.

code:
  v: TestScript.metadata.link.url
display:
  v: url
target:
  code:
    v: TestScript.metadata.link.url
  display:
    v: TestScript.metadata.link.url
  relationship:
    v: equivalent
  comment:
    v: Element `TestScript.metadata.link.url` is mapped to FHIR R5 element `TestScript.metadata.link.url` as `Equivalent`.

code:
  v: TestScript.metadata.link.description
display:
  v: description
target:
  code:
    v: TestScript.metadata.link.description
  display:
    v: TestScript.metadata.link.description
  relationship:
    v: equivalent
  comment:
    v: Element `TestScript.metadata.link.description` is mapped to FHIR R5 element `TestScript.metadata.link.description` as `Equivalent`.

code:
  v: TestScript.metadata.capability
display:
  v: capability
target:
  code:
    v: TestScript.metadata.capability
  display:
    v: TestScript.metadata.capability
  relationship:
    v: source-is-broader-than-target
  comment:
    v: 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.

code:
  v: TestScript.metadata.capability.required
display:
  v: required
target:
  code:
    v: TestScript.metadata.capability.required
  display:
    v: TestScript.metadata.capability.required
  relationship:
    v: equivalent
  comment:
    v: Element `TestScript.metadata.capability.required` is mapped to FHIR R5 element `TestScript.metadata.capability.required` as `Equivalent`.

code:
  v: TestScript.metadata.capability.validated
display:
  v: validated
target:
  code:
    v: TestScript.metadata.capability.validated
  display:
    v: TestScript.metadata.capability.validated
  relationship:
    v: equivalent
  comment:
    v: Element `TestScript.metadata.capability.validated` is mapped to FHIR R5 element `TestScript.metadata.capability.validated` as `Equivalent`.

code:
  v: TestScript.metadata.capability.description
display:
  v: description
target:
  code:
    v: TestScript.metadata.capability.description
  display:
    v: TestScript.metadata.capability.description
  relationship:
    v: equivalent
  comment:
    v: Element `TestScript.metadata.capability.description` is mapped to FHIR R5 element `TestScript.metadata.capability.description` as `Equivalent`.

code:
  v: TestScript.metadata.capability.destination
display:
  v: destination
target:
  code:
    v: TestScript.metadata.capability.destination
  display:
    v: TestScript.metadata.capability.destination
  relationship:
    v: equivalent
  comment:
    v: Element `TestScript.metadata.capability.destination` is mapped to FHIR R5 element `TestScript.metadata.capability.destination` as `Equivalent`.

code:
  v: TestScript.metadata.capability.link
display:
  v: link
target:
  code:
    v: TestScript.metadata.capability.link
  display:
    v: TestScript.metadata.capability.link
  relationship:
    v: equivalent
  comment:
    v: Element `TestScript.metadata.capability.link` is mapped to FHIR R5 element `TestScript.metadata.capability.link` as `Equivalent`.

code:
  v: TestScript.metadata.capability.conformance
display:
  v: conformance
target:
  code:
    v: TestScript.metadata.capability.capabilities
  display:
    v: TestScript.metadata.capability.capabilities
  relationship:
    v: source-is-broader-than-target
  comment:
    v: 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.

code:
  v: TestScript.fixture
display:
  v: fixture
target:
  code:
    v: TestScript.fixture
  display:
    v: TestScript.fixture
  relationship:
    v: source-is-broader-than-target
  comment:
    v: Element `TestScript.fixture` is mapped to FHIR R5 element `TestScript.fixture` as `Equivalent`.

code:
  v: TestScript.fixture.autocreate
display:
  v: autocreate
target:
  code:
    v: TestScript.fixture.autocreate
  display:
    v: TestScript.fixture.autocreate
  relationship:
    v: equivalent
  comment:
    v: Element `TestScript.fixture.autocreate` is mapped to FHIR R5 element `TestScript.fixture.autocreate` as `Equivalent`.

code:
  v: TestScript.fixture.autodelete
display:
  v: autodelete
target:
  code:
    v: TestScript.fixture.autodelete
  display:
    v: TestScript.fixture.autodelete
  relationship:
    v: equivalent
  comment:
    v: Element `TestScript.fixture.autodelete` is mapped to FHIR R5 element `TestScript.fixture.autodelete` as `Equivalent`.

code:
  v: TestScript.fixture.resource
display:
  v: resource
target:
  code:
    v: TestScript.fixture.resource
  display:
    v: TestScript.fixture.resource
  relationship:
    v: source-is-broader-than-target
  comment:
    v: 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.

code:
  v: TestScript.profile
display:
  v: profile
target:
  code:
    v: TestScript.profile
  display:
    v: TestScript.profile
  relationship:
    v: source-is-broader-than-target
  comment:
    v: 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.

code:
  v: TestScript.variable
display:
  v: variable
target:
  code:
    v: TestScript.variable
  display:
    v: TestScript.variable
  relationship:
    v: source-is-broader-than-target
  comment:
    v: 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.

code:
  v: TestScript.variable.name
display:
  v: name
target:
  code:
    v: TestScript.variable.name
  display:
    v: TestScript.variable.name
  relationship:
    v: equivalent
  comment:
    v: 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.

code:
  v: TestScript.variable.headerField
display:
  v: headerField
target:
  code:
    v: TestScript.variable.headerField
  display:
    v: TestScript.variable.headerField
  relationship:
    v: equivalent
  comment:
    v: 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.

code:
  v: TestScript.variable.path
display:
  v: path
target:
  code:
    v: TestScript.variable.path
  display:
    v: TestScript.variable.path
  relationship:
    v: equivalent
  comment:
    v: 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.

code:
  v: TestScript.variable.sourceId
display:
  v: sourceId
target:
  code:
    v: TestScript.variable.sourceId
  display:
    v: TestScript.variable.sourceId
  relationship:
    v: equivalent
  comment:
    v: 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.

code:
  v: TestScript.setup
display:
  v: setup
target:
  code:
    v: TestScript.setup
  display:
    v: TestScript.setup
  relationship:
    v: source-is-broader-than-target
  comment:
    v: Element `TestScript.setup` is mapped to FHIR R5 element `TestScript.setup` as `Equivalent`.

code:
  v: TestScript.setup.action
display:
  v: action
target:
  code:
    v: TestScript.setup.action
  display:
    v: TestScript.setup.action
  relationship:
    v: source-is-broader-than-target
  comment:
    v: 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.

code:
  v: TestScript.setup.action.operation
display:
  v: operation
target:
  code:
    v: TestScript.setup.action.operation
  display:
    v: TestScript.setup.action.operation
  relationship:
    v: source-is-broader-than-target
  comment:
    v: Element `TestScript.setup.action.operation` is mapped to FHIR R5 element `TestScript.setup.action.operation` as `Equivalent`.

code:
  v: TestScript.setup.action.operation.type
display:
  v: type
target:
  code:
    v: TestScript.setup.action.operation.type
  display:
    v: TestScript.setup.action.operation.type
  relationship:
    v: equivalent
  comment:
    v: 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.

code:
  v: TestScript.setup.action.operation.resource
display:
  v: resource
target:
  code:
    v: TestScript.setup.action.operation.resource
  display:
    v: TestScript.setup.action.operation.resource
  relationship:
    v: source-is-broader-than-target
  comment:
    v: 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.

code:
  v: TestScript.setup.action.operation.label
display:
  v: label
target:
  code:
    v: TestScript.setup.action.operation.label
  display:
    v: TestScript.setup.action.operation.label
  relationship:
    v: equivalent
  comment:
    v: 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.

code:
  v: TestScript.setup.action.operation.description
display:
  v: description
target:
  code:
    v: TestScript.setup.action.operation.description
  display:
    v: TestScript.setup.action.operation.description
  relationship:
    v: equivalent
  comment:
    v: 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.

code:
  v: TestScript.setup.action.operation.accept
display:
  v: accept
target:
  code:
    v: TestScript.setup.action.operation.accept
  display:
    v: TestScript.setup.action.operation.accept
  relationship:
    v: equivalent
  comment:
    v: 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.

code:
  v: TestScript.setup.action.operation.contentType
display:
  v: contentType
target:
  code:
    v: TestScript.setup.action.operation.contentType
  display:
    v: TestScript.setup.action.operation.contentType
  relationship:
    v: equivalent
  comment:
    v: 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.

code:
  v: TestScript.setup.action.operation.destination
display:
  v: destination
target:
  code:
    v: TestScript.setup.action.operation.destination
  display:
    v: TestScript.setup.action.operation.destination
  relationship:
    v: equivalent
  comment:
    v: Element `TestScript.setup.action.operation.destination` is mapped to FHIR R5 element `TestScript.setup.action.operation.destination` as `Equivalent`.

code:
  v: TestScript.setup.action.operation.encodeRequestUrl
display:
  v: encodeRequestUrl
target:
  code:
    v: TestScript.setup.action.operation.encodeRequestUrl
  display:
    v: TestScript.setup.action.operation.encodeRequestUrl
  relationship:
    v: equivalent
  comment:
    v: Element `TestScript.setup.action.operation.encodeRequestUrl` is mapped to FHIR R5 element `TestScript.setup.action.operation.encodeRequestUrl` as `Equivalent`.

code:
  v: TestScript.setup.action.operation.params
display:
  v: params
target:
  code:
    v: TestScript.setup.action.operation.params
  display:
    v: TestScript.setup.action.operation.params
  relationship:
    v: equivalent
  comment:
    v: 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.

code:
  v: TestScript.setup.action.operation.requestHeader
display:
  v: requestHeader
target:
  code:
    v: TestScript.setup.action.operation.requestHeader
  display:
    v: TestScript.setup.action.operation.requestHeader
  relationship:
    v: source-is-broader-than-target
  comment:
    v: 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.

code:
  v: TestScript.setup.action.operation.requestHeader.field
display:
  v: field
target:
  code:
    v: TestScript.setup.action.operation.requestHeader.field
  display:
    v: TestScript.setup.action.operation.requestHeader.field
  relationship:
    v: equivalent
  comment:
    v: 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.

code:
  v: TestScript.setup.action.operation.requestHeader.value
display:
  v: value
target:
  code:
    v: TestScript.setup.action.operation.requestHeader.value
  display:
    v: TestScript.setup.action.operation.requestHeader.value
  relationship:
    v: equivalent
  comment:
    v: 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.

code:
  v: TestScript.setup.action.operation.responseId
display:
  v: responseId
target:
  code:
    v: TestScript.setup.action.operation.responseId
  display:
    v: TestScript.setup.action.operation.responseId
  relationship:
    v: equivalent
  comment:
    v: 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.

code:
  v: TestScript.setup.action.operation.sourceId
display:
  v: sourceId
target:
  code:
    v: TestScript.setup.action.operation.sourceId
  display:
    v: TestScript.setup.action.operation.sourceId
  relationship:
    v: equivalent
  comment:
    v: Element `TestScript.setup.action.operation.sourceId` is mapped to FHIR R5 element `TestScript.setup.action.operation.sourceId` as `Equivalent`.

code:
  v: TestScript.setup.action.operation.targetId
display:
  v: targetId
target:
  code:
    v: TestScript.setup.action.operation.targetId
  display:
    v: TestScript.setup.action.operation.targetId
  relationship:
    v: equivalent
  comment:
    v: 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.

code:
  v: TestScript.setup.action.operation.url
display:
  v: url
target:
  code:
    v: TestScript.setup.action.operation.url
  display:
    v: TestScript.setup.action.operation.url
  relationship:
    v: equivalent
  comment:
    v: 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.

code:
  v: TestScript.setup.action.assert
display:
  v: assert
target:
  code:
    v: TestScript.setup.action.assert
  display:
    v: TestScript.setup.action.assert
  relationship:
    v: source-is-broader-than-target
  comment:
    v: 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.

code:
  v: TestScript.setup.action.assert.label
display:
  v: label
target:
  code:
    v: TestScript.setup.action.assert.label
  display:
    v: TestScript.setup.action.assert.label
  relationship:
    v: equivalent
  comment:
    v: 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.

code:
  v: TestScript.setup.action.assert.description
display:
  v: description
target:
  code:
    v: TestScript.setup.action.assert.description
  display:
    v: TestScript.setup.action.assert.description
  relationship:
    v: equivalent
  comment:
    v: 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.

code:
  v: TestScript.setup.action.assert.direction
display:
  v: direction
target:
  code:
    v: TestScript.setup.action.assert.direction
  display:
    v: TestScript.setup.action.assert.direction
  relationship:
    v: equivalent
  comment:
    v: Element `TestScript.setup.action.assert.direction` is mapped to FHIR R5 element `TestScript.setup.action.assert.direction` as `Equivalent`.

code:
  v: TestScript.setup.action.assert.compareToSourceId
display:
  v: compareToSourceId
target:
  code:
    v: TestScript.setup.action.assert.compareToSourceId
  display:
    v: TestScript.setup.action.assert.compareToSourceId
  relationship:
    v: equivalent
  comment:
    v: 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.

code:
  v: TestScript.setup.action.assert.compareToSourcePath
display:
  v: compareToSourcePath
target:
  code:
    v: TestScript.setup.action.assert.compareToSourcePath
  display:
    v: TestScript.setup.action.assert.compareToSourcePath
  relationship:
    v: equivalent
  comment:
    v: 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.

code:
  v: TestScript.setup.action.assert.contentType
display:
  v: contentType
target:
  code:
    v: TestScript.setup.action.assert.contentType
  display:
    v: TestScript.setup.action.assert.contentType
  relationship:
    v: equivalent
  comment:
    v: 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.

code:
  v: TestScript.setup.action.assert.headerField
display:
  v: headerField
target:
  code:
    v: TestScript.setup.action.assert.headerField
  display:
    v: TestScript.setup.action.assert.headerField
  relationship:
    v: equivalent
  comment:
    v: 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.

code:
  v: TestScript.setup.action.assert.minimumId
display:
  v: minimumId
target:
  code:
    v: TestScript.setup.action.assert.minimumId
  display:
    v: TestScript.setup.action.assert.minimumId
  relationship:
    v: equivalent
  comment:
    v: 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.

code:
  v: TestScript.setup.action.assert.navigationLinks
display:
  v: navigationLinks
target:
  code:
    v: TestScript.setup.action.assert.navigationLinks
  display:
    v: TestScript.setup.action.assert.navigationLinks
  relationship:
    v: equivalent
  comment:
    v: 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.

code:
  v: TestScript.setup.action.assert.operator
display:
  v: operator
target:
  code:
    v: TestScript.setup.action.assert.operator
  display:
    v: TestScript.setup.action.assert.operator
  relationship:
    v: equivalent
  comment:
    v: 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> .

code:
  v: TestScript.setup.action.assert.path
display:
  v: path
target:
  code:
    v: TestScript.setup.action.assert.path
  display:
    v: TestScript.setup.action.assert.path
  relationship:
    v: equivalent
  comment:
    v: 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.

code:
  v: TestScript.setup.action.assert.resource
display:
  v: resource
target:
  code:
    v: TestScript.setup.action.assert.resource
  display:
    v: TestScript.setup.action.assert.resource
  relationship:
    v: source-is-broader-than-target
  comment:
    v: 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>.

code:
  v: TestScript.setup.action.assert.response
display:
  v: response
target:
  code:
    v: TestScript.setup.action.assert.response
  display:
    v: TestScript.setup.action.assert.response
  relationship:
    v: source-is-broader-than-target
  comment:
    v: 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>.

code:
  v: TestScript.setup.action.assert.responseCode
display:
  v: responseCode
target:
  code:
    v: TestScript.setup.action.assert.responseCode
  display:
    v: TestScript.setup.action.assert.responseCode
  relationship:
    v: equivalent
  comment:
    v: 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.

code:
  v: TestScript.setup.action.assert.sourceId
display:
  v: sourceId
target:
  code:
    v: TestScript.setup.action.assert.sourceId
  display:
    v: TestScript.setup.action.assert.sourceId
  relationship:
    v: equivalent
  comment:
    v: 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.

code:
  v: TestScript.setup.action.assert.validateProfileId
display:
  v: validateProfileId
target:
  code:
    v: TestScript.setup.action.assert.validateProfileId
  display:
    v: TestScript.setup.action.assert.validateProfileId
  relationship:
    v: equivalent
  comment:
    v: 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.

code:
  v: TestScript.setup.action.assert.value
display:
  v: value
target:
  code:
    v: TestScript.setup.action.assert.value
  display:
    v: TestScript.setup.action.assert.value
  relationship:
    v: equivalent
  comment:
    v: 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.

code:
  v: TestScript.setup.action.assert.warningOnly
display:
  v: warningOnly
target:
  code:
    v: TestScript.setup.action.assert.warningOnly
  display:
    v: TestScript.setup.action.assert.warningOnly
  relationship:
    v: equivalent
  comment:
    v: 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.

code:
  v: TestScript.test
display:
  v: test
target:
  code:
    v: TestScript.test
  display:
    v: TestScript.test
  relationship:
    v: source-is-broader-than-target
  comment:
    v: Element `TestScript.test` is mapped to FHIR R5 element `TestScript.test` as `Equivalent`.

code:
  v: TestScript.test.name
display:
  v: name
target:
  code:
    v: TestScript.test.name
  display:
    v: TestScript.test.name
  relationship:
    v: equivalent
  comment:
    v: Element `TestScript.test.name` is mapped to FHIR R5 element `TestScript.test.name` as `Equivalent`.

code:
  v: TestScript.test.description
display:
  v: description
target:
  code:
    v: TestScript.test.description
  display:
    v: TestScript.test.description
  relationship:
    v: equivalent
  comment:
    v: Element `TestScript.test.description` is mapped to FHIR R5 element `TestScript.test.description` as `Equivalent`.

code:
  v: TestScript.test.action
display:
  v: action
target:
  code:
    v: TestScript.test.action
  display:
    v: TestScript.test.action
  relationship:
    v: source-is-broader-than-target
  comment:
    v: 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.

code:
  v: TestScript.test.action.operation
display:
  v: operation
target:
  code:
    v: TestScript.test.action.operation
  display:
    v: TestScript.test.action.operation
  relationship:
    v: equivalent
  comment:
    v: Element `TestScript.test.action.operation` is mapped to FHIR R5 element `TestScript.test.action.operation` as `Equivalent`.

code:
  v: TestScript.test.action.assert
display:
  v: assert
target:
  code:
    v: TestScript.test.action.assert
  display:
    v: TestScript.test.action.assert
  relationship:
    v: equivalent
  comment:
    v: 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.

code:
  v: TestScript.teardown
display:
  v: teardown
target:
  code:
    v: TestScript.teardown
  display:
    v: TestScript.teardown
  relationship:
    v: source-is-broader-than-target
  comment:
    v: Element `TestScript.teardown` is mapped to FHIR R5 element `TestScript.teardown` as `Equivalent`.

code:
  v: TestScript.teardown.action
display:
  v: action
target:
  code:
    v: TestScript.teardown.action
  display:
    v: TestScript.teardown.action
  relationship:
    v: source-is-broader-than-target
  comment:
    v: 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.

code:
  v: TestScript.teardown.action.operation
display:
  v: operation
target:
  code:
    v: TestScript.teardown.action.operation
  display:
    v: TestScript.teardown.action.operation
  relationship:
    v: equivalent
  comment:
    v: Element `TestScript.teardown.action.operation` is mapped to FHIR R5 element `TestScript.teardown.action.operation` as `Equivalent`.

source:
  v: http://hl7.org/fhir/StructureDefinition/TestScript|1.0.2
  l: http://hl7.org/fhir/StructureDefinition/TestScript
target:
  v: http://hl7.org/fhir/1.0/StructureDefinition/extension-TestScript.meta|0.1.0
  l: http://hl7.org/fhir/1.0/StructureDefinition/extension-TestScript.meta
element:
  code:
    v: TestScript.meta
  display:
    v: meta
  target:
    code:
      v: Extension
    relationship:
      v: equivalent
    comment:
      v: 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.

source:
  v: http://hl7.org/fhir/StructureDefinition/TestScript|1.0.2
  l: http://hl7.org/fhir/StructureDefinition/TestScript
target:
  v: http://hl7.org/fhir/1.0/StructureDefinition/extension-TestScript.text|0.1.0
  l: http://hl7.org/fhir/1.0/StructureDefinition/extension-TestScript.text
element:
  code:
    v: TestScript.text
  display:
    v: text
  target:
    code:
      v: Extension
    relationship:
      v: equivalent
    comment:
      v: 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.

source:
  v: http://hl7.org/fhir/StructureDefinition/TestScript|1.0.2
  l: http://hl7.org/fhir/StructureDefinition/TestScript
target:
  v: http://hl7.org/fhir/1.0/StructureDefinition/extension-TestScript.identifier|0.1.0
  l: http://hl7.org/fhir/1.0/StructureDefinition/extension-TestScript.identifier
element:
  code:
    v: TestScript.identifier
  display:
    v: identifier
  target:
    code:
      v: Extension
    relationship:
      v: equivalent
    comment:
      v: 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.

source:
  v: http://hl7.org/fhir/StructureDefinition/TestScript|1.0.2
  l: http://hl7.org/fhir/StructureDefinition/TestScript
target:
  v: http://hl7.org/fhir/1.0/StructureDefinition/extension-TestScript.contact.name|0.1.0
  l: http://hl7.org/fhir/1.0/StructureDefinition/extension-TestScript.contact.name
element:
  code:
    v: TestScript.contact.name
  display:
    v: name
  target:
    code:
      v: Extension
    relationship:
      v: source-is-broader-than-target
    comment:
      v: 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.

source:
  v: http://hl7.org/fhir/StructureDefinition/TestScript|1.0.2
  l: http://hl7.org/fhir/StructureDefinition/TestScript
target:
  v: http://hl7.org/fhir/1.0/StructureDefinition/extension-TestScript.contact.telecom|0.1.0
  l: http://hl7.org/fhir/1.0/StructureDefinition/extension-TestScript.contact.telecom
element:
  code:
    v: TestScript.contact.telecom
  display:
    v: telecom
  target:
    code:
      v: Extension
    relationship:
      v: source-is-broader-than-target
    comment:
      v: 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).

source:
  v: http://hl7.org/fhir/StructureDefinition/TestScript|1.0.2
  l: http://hl7.org/fhir/StructureDefinition/TestScript
target:
  v: http://hl7.org/fhir/1.0/StructureDefinition/extension-TestScript.useContext|0.1.0
  l: http://hl7.org/fhir/1.0/StructureDefinition/extension-TestScript.useContext
element:
  code:
    v: TestScript.useContext
  display:
    v: useContext
  target:
    code:
      v: Extension
    relationship:
      v: equivalent
    comment:
      v: 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.

source:
  v: http://hl7.org/fhir/StructureDefinition/TestScript|1.0.2
  l: http://hl7.org/fhir/StructureDefinition/TestScript
target:
  v: http://hl7.org/fhir/1.0/StructureDefinition/extension-TestScript.metadata|0.1.0
  l: http://hl7.org/fhir/1.0/StructureDefinition/extension-TestScript.metadata
element:
  code:
    v: TestScript.metadata
  display:
    v: metadata
  target:
    code:
      v: Extension
    relationship:
      v: equivalent
    comment:
      v: Element `TestScript.metadata` is mapped to FHIR R5 element `TestScript.metadata` as `Equivalent`.
element:
  code:
    v: TestScript.metadata.link
  display:
    v: link
  target:
    code:
      v: Extension.extension:link
    relationship:
      v: equivalent
    comment:
      v: Element `TestScript.metadata.link` is mapped to FHIR R5 element `TestScript.metadata.link` as `Equivalent`.
element:
  code:
    v: TestScript.metadata.link.url
  display:
    v: url
  target:
    code:
      v: Extension.extension:link.extension:url
    relationship:
      v: equivalent
    comment:
      v: Element `TestScript.metadata.link.url` is mapped to FHIR R5 element `TestScript.metadata.link.url` as `Equivalent`.
element:
  code:
    v: TestScript.metadata.link.description
  display:
    v: description
  target:
    code:
      v: Extension.extension:link.extension:description
    relationship:
      v: equivalent
    comment:
      v: Element `TestScript.metadata.link.description` is mapped to FHIR R5 element `TestScript.metadata.link.description` as `Equivalent`.
element:
  code:
    v: TestScript.metadata.capability
  display:
    v: capability
  target:
    code:
      v: Extension.extension:capability
    relationship:
      v: equivalent
    comment:
      v: 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:
  code:
    v: TestScript.metadata.capability.required
  display:
    v: required
  target:
    code:
      v: Extension.extension:capability.extension:required
    relationship:
      v: equivalent
    comment:
      v: Element `TestScript.metadata.capability.required` is mapped to FHIR R5 element `TestScript.metadata.capability.required` as `Equivalent`.
element:
  code:
    v: TestScript.metadata.capability.validated
  display:
    v: validated
  target:
    code:
      v: Extension.extension:capability.extension:validated
    relationship:
      v: equivalent
    comment:
      v: Element `TestScript.metadata.capability.validated` is mapped to FHIR R5 element `TestScript.metadata.capability.validated` as `Equivalent`.
element:
  code:
    v: TestScript.metadata.capability.description
  display:
    v: description
  target:
    code:
      v: Extension.extension:capability.extension:description
    relationship:
      v: equivalent
    comment:
      v: Element `TestScript.metadata.capability.description` is mapped to FHIR R5 element `TestScript.metadata.capability.description` as `Equivalent`.
element:
  code:
    v: TestScript.metadata.capability.destination
  display:
    v: destination
  target:
    code:
      v: Extension.extension:capability.extension:destination
    relationship:
      v: equivalent
    comment:
      v: Element `TestScript.metadata.capability.destination` is mapped to FHIR R5 element `TestScript.metadata.capability.destination` as `Equivalent`.
element:
  code:
    v: TestScript.metadata.capability.link
  display:
    v: link
  target:
    code:
      v: Extension.extension:capability.extension:link
    relationship:
      v: equivalent
    comment:
      v: Element `TestScript.metadata.capability.link` is mapped to FHIR R5 element `TestScript.metadata.capability.link` as `Equivalent`.
element:
  code:
    v: TestScript.metadata.capability.conformance
  display:
    v: conformance
  target:
    code:
      v: Extension.extension:capability.extension:conformance
    relationship:
      v: source-is-broader-than-target
    comment:
      v: 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.

source:
  v: http://hl7.org/fhir/StructureDefinition/TestScript|1.0.2
  l: http://hl7.org/fhir/StructureDefinition/TestScript
target:
  v: http://hl7.org/fhir/1.0/StructureDefinition/extension-TestScript.metadata.capability.conformance|0.1.0
  l: http://hl7.org/fhir/1.0/StructureDefinition/extension-TestScript.metadata.capability.conformance
element:
  code:
    v: TestScript.metadata.capability.conformance
  display:
    v: conformance
  target:
    code:
      v: Extension
    relationship:
      v: source-is-broader-than-target
    comment:
      v: 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.

source:
  v: http://hl7.org/fhir/StructureDefinition/TestScript|1.0.2
  l: http://hl7.org/fhir/StructureDefinition/TestScript
target:
  v: http://hl7.org/fhir/1.0/StructureDefinition/extension-TestScript.multiserver|0.1.0
  l: http://hl7.org/fhir/1.0/StructureDefinition/extension-TestScript.multiserver
element:
  code:
    v: TestScript.multiserver
  display:
    v: multiserver
  target:
    code:
      v: Extension
    relationship:
      v: equivalent
    comment:
      v: 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).

source:
  v: http://hl7.org/fhir/StructureDefinition/TestScript|1.0.2
  l: http://hl7.org/fhir/StructureDefinition/TestScript
target:
  v: http://hl7.org/fhir/1.0/StructureDefinition/extension-TestScript.profile|0.1.0
  l: http://hl7.org/fhir/1.0/StructureDefinition/extension-TestScript.profile
element:
  code:
    v: TestScript.profile
  display:
    v: profile
  target:
    code:
      v: Extension
    relationship:
      v: equivalent
    comment:
      v: 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.

source:
  v: http://hl7.org/fhir/StructureDefinition/TestScript|1.0.2
  l: http://hl7.org/fhir/StructureDefinition/TestScript
target:
  v: http://hl7.org/fhir/1.0/StructureDefinition/extension-TestScript.setup.action.operation.resource|0.1.0
  l: http://hl7.org/fhir/1.0/StructureDefinition/extension-TestScript.setup.action.operation.resource
element:
  code:
    v: TestScript.setup.action.operation.resource
  display:
    v: resource
  target:
    code:
      v: Extension
    relationship:
      v: equivalent
    comment:
      v: 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.

source:
  v: http://hl7.org/fhir/StructureDefinition/TestScript|1.0.2
  l: http://hl7.org/fhir/StructureDefinition/TestScript
target:
  v: http://hl7.org/fhir/1.0/StructureDefinition/extension-TestScript.setup.action.assert.resource|0.1.0
  l: http://hl7.org/fhir/1.0/StructureDefinition/extension-TestScript.setup.action.assert.resource
element:
  code:
    v: TestScript.setup.action.assert.resource
  display:
    v: resource
  target:
    code:
      v: Extension
    relationship:
      v: equivalent
    comment:
      v: 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>.

source:
  v: http://hl7.org/fhir/StructureDefinition/TestScript|1.0.2
  l: http://hl7.org/fhir/StructureDefinition/TestScript
target:
  v: http://hl7.org/fhir/1.0/StructureDefinition/extension-TestScript.setup.action.assert.response|0.1.0
  l: http://hl7.org/fhir/1.0/StructureDefinition/extension-TestScript.setup.action.assert.response
element:
  code:
    v: TestScript.setup.action.assert.response
  display:
    v: response
  target:
    code:
      v: Extension
    relationship:
      v: equivalent
    comment:
      v: 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>.