Generated Narrative: StructureDefinition ext-R3-TestScript.set.act.ass.ruleset Name Flags Card. Type Description & Constraints Extension 0..1 Extension(4.3.0) STU3: The reference to a TestScript.ruleset (new) #xD; Slices for extension 1..* Extension Extension Slice: Unordered, Open by value:url #xD; extension:rulesetId 1..1 Extension STU3: Id of the TestScript.ruleset (new) #xD; url 1..1 uri "rulesetId" #xD; value[x] 1..1 id Id of the TestScript.ruleset #xD; extension:rule 0..* Extension STU3: The referenced rule within the ruleset (new) #xD; Slices for extension 1..* Extension Extension Slice: Unordered, Open by value:url #xD; extension:ruleId 1..1 Extension STU3: Id of referenced rule within the ruleset (new) #xD; url 1..1 uri "ruleId" #xD; value[x] 1..1 id Id of referenced rule within the ruleset #xD; extension:param 0..* Extension STU3: Rule parameter template (new) #xD; Slices for extension 2..* Extension Extension Slice: Unordered, Open by value:url #xD; extension:name 1..1 Extension STU3: Parameter name matching external assert ruleset rule parameter (new) #xD; url 1..1 uri "name" #xD; value[x] 1..1 string Parameter name matching external assert ruleset rule parameter #xD; extension:value 1..1 Extension STU3: Parameter value defined either explicitly or dynamically (new) #xD; url 1..1 uri "value" #xD; value[x] 1..1 string Parameter value defined either explicitly or dynamically #xD; url 1..1 uri "param" #xD; value[x] 0..0 Value of extension #xD; url 1..1 uri "rule" #xD; value[x] 0..0 Value of extension #xD; url 1..1 uri "http://hl7.org/fhir/3.0/StructureDefinition/extension-TestScript.setup.action.assert.ruleset" #xD; value[x] 0..0 Value of extension #xD; Documentation for this format
STU3: The reference to a TestScript.ruleset (new)
STU3: `TestScript.setup.action.assert.ruleset` (new:BackboneElement)
This extension is part of the cross-version definitions generated to enable use of the element `TestScript.setup.action.assert.ruleset` as defined in FHIR STU3 in FHIR R4B. The source element is defined as: `TestScript.setup.action.assert.ruleset` 0..1 `BackboneElement` Across FHIR versions, the element set has been mapped as: * STU3: `TestScript.setup.action.assert.ruleset` 0..1 `BackboneElement` Following are the generation technical comments: Element `TestScript.setup.action.assert.ruleset` has a context of TestScript.setup.action.assert based on following the parent source element upwards and mapping to `TestScript`. Element `TestScript.setup.action.assert.ruleset` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).
Element `TestScript.setup.action.assert.ruleset` has a context of TestScript.setup.action.assert based on following the parent source element upwards and mapping to `TestScript`. Element `TestScript.setup.action.assert.ruleset` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element). Each rule within a ruleset should get evaluated by test engines as a separate assertion. The impact of negative rule evaluation on test script execution is the same as an assertion failure which is descibed elsewhere in the TestScript resource. If the first rule within the ruleset results in a failed assertion, then test engines do not have to evaluate the rest of the rules within the ruleset.
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")])
STU3: Id of the TestScript.ruleset (new)
STU3: `TestScript.setup.action.assert.ruleset.rulesetId` (new:id)
Element `TestScript.setup.action.assert.ruleset.rulesetId` is part of an existing definition because parent element `TestScript.setup.action.assert.ruleset` requires a cross-version extension. Element `TestScript.setup.action.assert.ruleset.rulesetId` has a context of TestScript.setup.action.assert based on following the parent source element upwards and mapping to `TestScript`. Element `TestScript.setup.action.assert.ruleset.rulesetId` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).
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 TestScript.ruleset id value this assert will evaluate.
STU3: The referenced rule within the ruleset (new)
STU3: `TestScript.setup.action.assert.ruleset.rule` (new:BackboneElement)
Element `TestScript.setup.action.assert.ruleset.rule` is part of an existing definition because parent element `TestScript.setup.action.assert.ruleset` requires a cross-version extension. Element `TestScript.setup.action.assert.ruleset.rule` has a context of TestScript.setup.action.assert based on following the parent source element upwards and mapping to `TestScript`. Element `TestScript.setup.action.assert.ruleset.rule` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element). This qualifies each param name so that a parameter with the same name can be used differently by the different rules with the ruleset.
Element `TestScript.setup.action.assert.ruleset.rule` is part of an existing definition because parent element `TestScript.setup.action.assert.ruleset` requires a cross-version extension. Element `TestScript.setup.action.assert.ruleset.rule` has a context of TestScript.setup.action.assert based on following the parent source element upwards and mapping to `TestScript`. Element `TestScript.setup.action.assert.ruleset.rule` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).
STU3: Id of referenced rule within the ruleset (new)
STU3: `TestScript.setup.action.assert.ruleset.rule.ruleId` (new:id)
Element `TestScript.setup.action.assert.ruleset.rule.ruleId` is part of an existing definition because parent element `TestScript.setup.action.assert.ruleset.rule` requires a cross-version extension. Element `TestScript.setup.action.assert.ruleset.rule.ruleId` has a context of TestScript.setup.action.assert based on following the parent source element upwards and mapping to `TestScript`. Element `TestScript.setup.action.assert.ruleset.rule.ruleId` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).
Id of referenced rule within the ruleset
Id of the referenced rule within the external ruleset template.
STU3: `TestScript.setup.action.assert.ruleset.rule.param` (new:BackboneElement)
Element `TestScript.setup.action.assert.ruleset.rule.param` is part of an existing definition because parent element `TestScript.setup.action.assert.ruleset.rule` requires a cross-version extension. Element `TestScript.setup.action.assert.ruleset.rule.param` has a context of TestScript.setup.action.assert based on following the parent source element upwards and mapping to `TestScript`. Element `TestScript.setup.action.assert.ruleset.rule.param` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element). The parameter value can be dynamic at runtime.
Element `TestScript.setup.action.assert.ruleset.rule.param` is part of an existing definition because parent element `TestScript.setup.action.assert.ruleset.rule` requires a cross-version extension. Element `TestScript.setup.action.assert.ruleset.rule.param` has a context of TestScript.setup.action.assert based on following the parent source element upwards and mapping to `TestScript`. Element `TestScript.setup.action.assert.ruleset.rule.param` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).
STU3: Parameter name matching external assert ruleset rule parameter (new)
STU3: `TestScript.setup.action.assert.ruleset.rule.param.name` (new:string)
Element `TestScript.setup.action.assert.ruleset.rule.param.name` is part of an existing definition because parent element `TestScript.setup.action.assert.ruleset.rule.param` requires a cross-version extension. Element `TestScript.setup.action.assert.ruleset.rule.param.name` has a context of TestScript.setup.action.assert based on following the parent source element upwards and mapping to `TestScript`. Element `TestScript.setup.action.assert.ruleset.rule.param.name` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element). The external rule template would be looking for the parameter by this name.
Element `TestScript.setup.action.assert.ruleset.rule.param.name` is part of an existing definition because parent element `TestScript.setup.action.assert.ruleset.rule.param` requires a cross-version extension. Element `TestScript.setup.action.assert.ruleset.rule.param.name` has a context of TestScript.setup.action.assert based on following the parent source element upwards and mapping to `TestScript`. Element `TestScript.setup.action.assert.ruleset.rule.param.name` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).
Parameter name matching external assert ruleset rule parameter
Descriptive name for this parameter that matches the external assert ruleset rule parameter name.
The external rule template would be looking for the parameter by this name.
STU3: Parameter value defined either explicitly or dynamically (new)
STU3: `TestScript.setup.action.assert.ruleset.rule.param.value` (new:string)
Element `TestScript.setup.action.assert.ruleset.rule.param.value` is part of an existing definition because parent element `TestScript.setup.action.assert.ruleset.rule.param` requires a cross-version extension. Element `TestScript.setup.action.assert.ruleset.rule.param.value` has a context of TestScript.setup.action.assert based on following the parent source element upwards and mapping to `TestScript`. Element `TestScript.setup.action.assert.ruleset.rule.param.value` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element). This value overwrites the value (if any) specified in TestScript.ruleset.rule.param.value. The param value can be a 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 supplying this value to the external rule template.
Element `TestScript.setup.action.assert.ruleset.rule.param.value` is part of an existing definition because parent element `TestScript.setup.action.assert.ruleset.rule.param` requires a cross-version extension. Element `TestScript.setup.action.assert.ruleset.rule.param.value` has a context of TestScript.setup.action.assert based on following the parent source element upwards and mapping to `TestScript`. Element `TestScript.setup.action.assert.ruleset.rule.param.value` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).
Parameter value defined either explicitly or dynamically
The value for the parameter that will be passed on to the external ruleset rule template.
This value overwrites the value (if any) specified in TestScript.ruleset.rule.param.value. The param value can be a 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 supplying this value to the external rule template.
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).