Generated Narrative: StructureDefinition profile-TestReport Name Flags Card. Type Description & Constraints TestReport 0..* TestReport Describes the results of a TestScript execution #xD; testScript #xD; Slices for extension 0..* Extension Extension Slice: Unordered, Open by value:url #xD; extension:testScript 0..1 uri R5: Canonical URL to the version-specific TestScript that was executed to produce this TestReport additional types URL: http://hl7.org/fhir/5.0/StructureDefinition/extension-TestReport.testScript #xD; setup #xD; action #xD; assert #xD; Slices for extension 0..* Extension Extension Slice: Unordered, Open by value:url #xD; extension:requirement 0..* (Complex) R5: Links or references to the testing requirements (new) URL: http://hl7.org/fhir/5.0/StructureDefinition/extension-TestReport.setup.action.assert.requirement #xD; Documentation for this format
Cross-version Profile for R5.TestReport for use in FHIR STU3
This cross-version profile allows R5 TestReport content to be represented via FHIR STU3 TestReport resources.
Describes the results of a TestScript execution
A summary of information based on the results of executing a TestScript.
If the resource is contained in another resource, it SHALL NOT contain nested Resources
not(parent::f:contained and f:contained)
If the resource is contained in another resource, it SHALL NOT contain any narrative
If a resource is contained in another resource, it SHALL NOT have a meta.versionId or a meta.lastUpdated
contained.meta.versionId.empty() and contained.meta.lastUpdated.empty()
not(exists(f:contained/*/f:meta/f:versionId)) and not(exists(f:contained/*/f:meta/f:lastUpdated))
If the resource is contained in another resource, it SHALL be referred to from elsewhere in the resource
contained.where(('#'+id in %resource.descendants().reference).not()).empty()
not(exists(for $id in f:contained/*/@id return $id[not(ancestor::f:contained/parent::*/descendant::f:reference/@value=concat('#', $id))]))
The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes.
The only time that a resource does not have an id is when it is being submitted to the server using a create operation.
The metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content may not always be associated with version changes to the resource.
A set of rules under which this content was created
A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content.
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. This element is labelled as a modifier because the implicit rules may provide additional knowledge about the resource that modifies it's meaning or interpretation.
The base language in which the resource is written.
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).
Text summary of the resource, for human interpretation
A human-readable narrative that contains a summary of the resource, and may be used to represent the content of the resource to a human. The narrative need not encode all the structured data, but is required to contain sufficient detail to make it "clinically safe" for a human to just read the narrative. Resource definitions may define what content should be represented in the narrative to ensure clinical safety.
Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a "text blob" or where text is additionally entered raw or narrated and encoded in formation is added later.
These resources do not have an independent existence apart from the resource that contains them - they cannot be identified independently, and nor can they have their own independent transaction scope.
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.
Additional Content defined by implementations
May be used to represent additional information that is not part of the basic definition of the resource. In order 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 is allowed to 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.
May be used to represent additional information that is not part of the basic definition of the resource, and that modifies the understanding of the element that contains it. Usually modifier elements provide negation or qualification. In order 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 is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions.
Identifier for the TestScript assigned for external purposes outside the context of FHIR.
Informal name of the executed TestScript
A free text natural language name identifying the executed TestScript.
completed | in-progress | waiting | stopped | entered-in-error
The status represents where the execution is currently within the test script execution life cycle. This element is labeled as a modifier because the status contains codes that mark the resource as not currently valid.
Reference to the version-specific TestScript that was executed to produce this TestReport
Ideally this is an absolute URL that is used to identify the version-specific TestScript that was executed, matching the `TestScript.url`.
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
R5: Canonical URL to the version-specific TestScript that was executed to produce this TestReport additional types
R5: `TestReport.testScript` additional types (canonical(http://hl7.org/fhir/StructureDefinition/TestScript)) additional types from child elements (value)
Element `TestReport.testScript` is mapped to FHIR STU3 element `TestReport.testScript` as `SourceIsBroaderThanTarget`. The mappings for `TestReport.testScript` do not cover the following types: canonical. The mappings for `TestReport.testScript` do not cover the following types based on type expansion: value.
Literal reference, Relative, internal or absolute URL
A reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources.
Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server.
Logical reference, when literal reference is not known
An identifier for the other resource. This is used when there is no way to reference the other resource directly, either because the entity is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference.
When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy. When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it.
Plain text narrative that identifies the resource in addition to the resource reference.
This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it.
The overall result from the execution of the TestScript.
The pass and fail result represents a completed test script execution. The pending result represents a test script execution that has not yet started or is currently in progress.
The final score (percentage of tests passed) resulting from the execution of the TestScript
The final score (percentage of tests passed) resulting from the execution of the TestScript.
Name of the tester producing this report (Organization or individual)
Name of the tester producing this report (Organization or individual).
Usually an organization, but may be an individual. This item SHOULD be populated unless the information is available from context.
Helps establish the "authority/credibility" of the TestReport. May also allow for contact.
When the TestScript was executed and this TestReport was generated
When the TestScript was executed and this TestReport was generated.
Additional specific dates may be added as extensions.
A participant in the test execution, either the execution engine, a client, or a server
A participant in the test execution, either the execution engine, a client, or a server.
All FHIR elements must have a @value or children
hasValue() | (children().count() > id.count())
May be used to represent additional information that is not part of the basic definition of the element. In order 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 is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.
May be used to represent additional information that is not part of the basic definition of the element, and that modifies the understanding of the element that contains it. Usually modifier elements provide negation or qualification. In order 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 is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions.
The uri of the participant. An absolute URL is preferred
The uri of the participant. An absolute URL is preferred.
The results of the series of required setup operations before the tests were executed
The results of the series of required setup operations before the tests were executed.
A setup operation or assert that was executed
Action would contain either an operation or an assertion.
An action should contain either an operation or an assertion but not both. It can contain any number of variables.
Setup action SHALL contain either an operation or assert but not both.
(f:operation or f:assert) and not(f:operation and f:assert)
An explanatory message associated with the result.
A link to further details on the result.
The results of the assertion performed on the previous operations.
R5: Links or references to the testing requirements (new)
R5: `TestReport.setup.action.assert.requirement` (new:BackboneElement)
Element `TestReport.setup.action.assert.requirement` has a context of TestReport.setup.action.assert based on following the parent source element upwards and mapping to `TestReport`. Element `TestReport.setup.action.assert.requirement` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). TestScript and TestReport instances are typically (and expected to be) based on known, defined test requirements and documentation. These links provide traceability from the executable/executed TestScript and TestReport tests to these requirements.
Must have either extensions or value[x], not both
exists(f:extension)!=exists(f:*[starts-with(local-name(.), 'value')])
The name of this test used for tracking/logging purposes by test engines.
Tracking/reporting short description of the test
A short description of the test used by test engines for tracking and reporting purposes.
A test operation or assert that was performed
Test action SHALL contain either an operation or assert but not both.
An operation would involve a REST request to a server.
The results of running the series of required clean up steps
The results of the series of operations required to clean up after the all the tests were executed (successfully or otherwise).
One or more teardown operations performed
The teardown action will only contain an operation.