Generated Narrative: StructureDefinition ext-R2-TestScript.metadata Name Flags Card. Type Description & Constraints Extension 0..1 Extension(4.3.0) DSTU2: metadata #xD; Slices for extension 1..* Extension Extension Slice: Unordered, Open by value:url #xD; extension:link 0..* Extension DSTU2: link #xD; Slices for extension 1..* Extension Extension Slice: Unordered, Open by value:url #xD; extension:url 1..1 Extension DSTU2: url #xD; url 1..1 uri "url" #xD; value[x] 1..1 uri URL to the specification #xD; extension:description 0..1 Extension DSTU2: description #xD; url 1..1 uri "description" #xD; value[x] 0..1 string Short description #xD; url 1..1 uri "link" #xD; value[x] 0..0 Value of extension #xD; extension:capability 1..* Extension DSTU2: capability #xD; Slices for extension 1..* Extension Extension Slice: Unordered, Open by value:url #xD; extension:required 0..1 Extension DSTU2: required #xD; url 1..1 uri "required" #xD; value[x] 0..1 boolean Are the capabilities required? #xD; extension:validated 0..1 Extension DSTU2: validated #xD; url 1..1 uri "validated" #xD; value[x] 0..1 boolean Are the capabilities validated? #xD; extension:description 0..1 Extension DSTU2: description #xD; url 1..1 uri "description" #xD; value[x] 0..1 string The expected capabilities of the server #xD; extension:destination 0..1 Extension DSTU2: destination #xD; url 1..1 uri "destination" #xD; value[x] 0..1 integer Which server these requirements apply to #xD; extension:link 0..* Extension DSTU2: link #xD; url 1..1 uri "link" #xD; value[x] 0..1 uri Links to the FHIR specification #xD; extension:conformance 1..1 Extension DSTU2: Required Conformance additional types #xD; url 1..1 uri "conformance" #xD; value[x] 1..1 Reference(Cross-version Profile for DSTU2.Conformance for use in FHIR R4B(0.1.0) | CapabilityStatement) Required Conformance #xD; url 1..1 uri "capability" #xD; value[x] 0..0 Value of extension #xD; url 1..1 uri "http://hl7.org/fhir/1.0/StructureDefinition/extension-TestScript.metadata" #xD; value[x] 0..0 Value of extension #xD; Documentation for this format
This extension is part of the cross-version definitions generated to enable use of the element `TestScript.metadata` as defined in FHIR DSTU2 in FHIR R4B. The source element is defined as: `TestScript.metadata` 0..1 `BackboneElement` Across FHIR versions, the element set has been mapped as: * DSTU2: `TestScript.metadata` 0..1 `BackboneElement` * STU3: `TestScript.metadata` 0..1 `BackboneElement` * R4: `TestScript.metadata` 0..1 `BackboneElement` * R4B: `TestScript.metadata` 0..1 `BackboneElement` Following are the generation technical comments: Element `TestScript.metadata` is mapped to FHIR R4B element `TestScript.metadata` as `Equivalent`. Creating extension because element `TestScript.metadata` is a content reference and requires an extesion definition.
Element `TestScript.metadata` is mapped to FHIR R4B element `TestScript.metadata` as `Equivalent`.
All FHIR elements must have a @value or children unless an empty Parameters resource
hasValue() or (children().count() > id.count()) or $this is Parameters
Must have either extensions or value[x], not both
exists(f:extension)!=exists(f:*[starts-with(local-name(.), 'value')])
Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
Extensions are always sliced by (at least) url
All FHIR elements must have a @value or children
hasValue() or (children().count() > id.count())
exists(f:extension)!=exists(f:*[starts-with(local-name(.), "value")])
Element `TestScript.metadata.link` is mapped to FHIR R4B element `TestScript.metadata.link` as `Equivalent`.
Element `TestScript.metadata.link.url` is mapped to FHIR R4B element `TestScript.metadata.link.url` as `Equivalent`.
Additional content defined by implementations
May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Source of the definition for the extension code - a logical name or a URL.
The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension.
URL to a particular requirement or feature within the FHIR specification.
DSTU2: `TestScript.metadata.link.description`
Element `TestScript.metadata.link.description` is mapped to FHIR R4B element `TestScript.metadata.link.description` as `Equivalent`.
Value of extension - must be one of a constrained set of the data types (see [Extensibility](http://hl7.org/fhir/R4B/extensibility.html) for a list).
Element `TestScript.metadata.capability` is mapped to FHIR R4B 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` is mapped to FHIR R4B element `TestScript.metadata.capability` as `Equivalent`.
DSTU2: `TestScript.metadata.capability.required`
Element `TestScript.metadata.capability.required` is mapped to FHIR R4B element `TestScript.metadata.capability.required` as `Equivalent`.
Whether or not the test execution will require the given capabilities of the server in order for this test script to execute.
DSTU2: `TestScript.metadata.capability.validated`
Element `TestScript.metadata.capability.validated` is mapped to FHIR R4B element `TestScript.metadata.capability.validated` as `Equivalent`.
Whether or not the test execution will validate the given capabilities of the server in order for this test script to execute.
DSTU2: `TestScript.metadata.capability.description`
Element `TestScript.metadata.capability.description` is mapped to FHIR R4B element `TestScript.metadata.capability.description` as `Equivalent`.
Description of the capabilities that this test script is requiring the server to support.
DSTU2: `TestScript.metadata.capability.destination`
Element `TestScript.metadata.capability.destination` is mapped to FHIR R4B element `TestScript.metadata.capability.destination` as `Equivalent`.
Which server these requirements apply to
Which server these requirements apply to.
DSTU2: `TestScript.metadata.capability.link`
Element `TestScript.metadata.capability.link` is mapped to FHIR R4B element `TestScript.metadata.capability.link` as `Equivalent`.
Links to the FHIR specification that describes this interaction and the resources involved in more detail.
DSTU2: Required Conformance additional types
DSTU2: `TestScript.metadata.capability.conformance` additional types (Reference(http://hl7.org/fhir/StructureDefinition/Conformance)) additional types from child elements (display, reference)
Element `TestScript.metadata.capability.conformance` is mapped to FHIR R4B 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.metadata.capability.conformance` is mapped to FHIR R4B 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.
Minimum conformance required of server for test script to execute successfully. If server does not meet at a minimum the reference conformance definition, then all tests in this script are skipped.
The conformance statement of the server has to contain at a minimum the contents of the reference pointed to by this element.