Generated Narrative: StructureDefinition ext-R5-TestScript.scope Name Flags Card. Type Description & Constraints Extension 0..* Extension(4.3.0) Indication of the artifact(s) that are tested by this test case #xD; Slices for extension 1..* Extension Extension Slice: Unordered, Closed by value:url #xD; extension:artifact 1..1 Extension The specific conformance artifact being tested #xD; url 1..1 uri "artifact" #xD; value[x] 0..1 canonical() The specific conformance artifact being tested #xD; <a href="StructureDefinition-ext-R5-TestScript.scope-definitions.html#Extension.extension:conformance" title="Slice conformance: The expectation of whether the test must pass for the system to be considered conformant with the artifact: required - all tests are expected to pass, optional - all test are expected to pass but non-pass status may be allowed, strict - all tests are expected to pass and warnings are treated as a failure.">extension:conformance 0..1 Extension required | optional | strict #xD; url 1..1 uri "conformance" #xD; <a href="StructureDefinition-ext-R5-TestScript.scope-definitions.html#Extension.extension:conformance.value[x]" title="The expectation of whether the test must pass for the system to be considered conformant with the artifact: required - all tests are expected to pass, optional - all test are expected to pass but non-pass status may be allowed, strict - all tests are expected to pass and warnings are treated as a failure.">value[x] 0..1 CodeableConcept required | optional | strict Binding: R5_testscript_scope_conformance_codes_for_R4B (0.0.1-snapshot-2) (extensible): The expectation of whether the test must pass for the system to be considered conformant with the artifact. #xD; extension:phase 0..1 Extension unit | integration | production #xD; url 1..1 uri "phase" #xD; value[x] 0..1 CodeableConcept unit | integration | production Binding: R5_testscript_scope_phase_codes_for_R4B (0.0.1-snapshot-2) (extensible): The phase of testing for this artifact. #xD; url 1..1 uri "http://hl7.org/fhir/5.0/StructureDefinition/extension-TestScript.scope" #xD; Documentation for this format
Cross-version Extension for R5.TestScript.scope for use in FHIR R4B
This cross-version extension represents TestScript.scope from http://hl7.org/fhir/StructureDefinition/TestScript|5.0.0 for use in FHIR R4B.
Indication of the artifact(s) that are tested by this test case
The scope indicates a conformance artifact that is tested by the test(s) within this test case and the expectation of the test outcome(s) as well as the intended test phase inclusion.
`TestScript.scope` has no related element in R4B:TestScript
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")])
The specific conformance artifact being tested
The specific conformance artifact being tested. The canonical reference can be version-specific.
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.
The expectation of whether the test must pass for the system to be considered conformant with the artifact: required - all tests are expected to pass, optional - all test are expected to pass but non-pass status may be allowed, strict - all tests are expected to pass and warnings are treated as a failure.
The expectation of whether the test must pass for the system to be considered conformant with the artifact.
The phase of testing for this artifact: unit - development / implementation phase, integration - internal system to system phase, production - live system to system phase (Note, this may involve pii/phi data).
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).