Generated Narrative: StructureDefinition ext-R3-TestScript.rule Name Flags Card. Type Description & Constraints Extension 0..* Extension(4.0.1) Assert rule used within the test script #xD; Slices for extension 1..* Extension Extension Slice: Unordered, Closed by value:url #xD; extension:resource 1..1 Extension Assert rule resource reference #xD; url 1..1 uri "resource" #xD; value[x] 0..1 Reference() Assert rule resource reference #xD; extension:param 0..* Extension Rule parameter template #xD; Slices for extension 1..* Extension Extension Slice: Unordered, Closed by value:url #xD; extension:name 1..1 Extension Parameter name matching external assert rule parameter #xD; url 1..1 uri "name" #xD; value[x] 0..1 string Parameter name matching external assert rule parameter #xD; extension:value 0..1 Extension Parameter value defined either explicitly or dynamically #xD; url 1..1 uri "value" #xD; value[x] 0..1 string Parameter value defined either explicitly or dynamically #xD; url 1..1 uri "param" #xD; url 1..1 uri "http://hl7.org/fhir/3.0/StructureDefinition/extension-TestScript.rule" #xD; Documentation for this format
Cross-version Extension for R3.TestScript.rule for use in FHIR R4
This cross-version extension represents TestScript.rule from http://hl7.org/fhir/StructureDefinition/TestScript|3.0.2 for use in FHIR R4.
Assert rule to be used in one or more asserts within the test script.
`TestScript.rule` has no related element in R4:TestScript
All FHIR elements must have a @value or children
hasValue() or (children().count() > id.count())
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
exists(f:extension)!=exists(f:*[starts-with(local-name(.), "value")])
Reference to the resource (containing the contents of the rule needed for assertions).
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.
Each rule template can take one or more parameters for rule evaluation.
Parameter name matching external assert rule parameter
Descriptive name for this parameter that matches the external assert rule parameter name.
Parameter value defined either explicitly or dynamically
The explicit or dynamic value for the parameter that will be passed on 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/R4/extensibility.html) for a list).