Struct TestReportInner

pub struct TestReportInner {

    pub id: Option<String>,
    pub meta: Option<Meta>,
    pub implicit_rules: Option<String>,
    pub language: Option<String>,
    pub text: Option<Narrative>,
    pub contained: Vec<Resource>,
    pub extension: Vec<Extension>,
    pub modifier_extension: Vec<Extension>,
    pub identifier: Option<Identifier>,
    pub identifier_ext: Option<FieldExtension>,
    pub name: Option<String>,
    pub name_ext: Option<FieldExtension>,
    pub status: TestReportStatus,
    pub status_ext: Option<FieldExtension>,
    pub test_script: String,
    pub test_script_ext: Option<FieldExtension>,
    pub result: TestReportResult,
    pub result_ext: Option<FieldExtension>,
    pub score: Option<f64>,
    pub score_ext: Option<FieldExtension>,
    pub tester: Option<String>,
    pub tester_ext: Option<FieldExtension>,
    pub issued: Option<DateTime>,
    pub issued_ext: Option<FieldExtension>,
    pub participant: Vec<Option<TestReportParticipant>>,
    pub participant_ext: Vec<Option<FieldExtension>>,
    pub setup: Option<TestReportSetup>,
    pub setup_ext: Option<FieldExtension>,
    pub test: Vec<Option<TestReportTest>>,
    pub test_ext: Vec<Option<FieldExtension>>,
    pub teardown: Option<TestReportTeardown>,
    pub teardown_ext: Option<FieldExtension>,
    /* private fields */
}

A summary of information based on the results of executing a TestScript.

TestReport v5.0.0

Describes the results of a TestScript execution

A summary of information based on the results of executing a TestScript.

Fields

id: Option<String>

Logical id of this artifact

The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes.

Within the context of the FHIR RESTful interactions, the resource has an id except for cases like the create and conditional update. Otherwise, the use of the resouce id depends on the given use case.

meta: Option<Meta>

Metadata about the resource

The metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content might not always be associated with version changes to the resource.

implicit_rules: Option<String>

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. Often, this is a reference to an implementation guide that defines the special rules along with other profiles etc.

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. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of its narrative along with other profiles, value sets, etc.

language: Option<String>

Language; Language of the resource content

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: Option<Narrative>

Text summary of the resource, for human interpretation

A human-readable narrative that contains a summary of the resource and can 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 a 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 information is added later.

contained: Vec<Resource>

Contained, inline Resources

These resources do not have an independent existence apart from the resource that contains them - they cannot be identified independently, nor can they have their own independent transaction scope. This is allowed to be a Parameters resource if and only if it is referenced by a resource that provides context/meaning.

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. Contained resources may have profiles and tags in their meta elements, but SHALL NOT have security labels.

extension: Vec<Extension>

Additional content defined by implementations

May be used to represent additional information that is not part of the basic definition of the resource. To make the use of extensions safe and managable, 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.

modifier_extension: Vec<Extension>

Extensions that cannot be ignored

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 and/or the understanding of the containing element’s descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and managable, 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.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).

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.

identifier: Option<Identifier>

External identifier

Identifier for the TestReport assigned for external purposes outside the context of FHIR.

identifier_ext: Option<FieldExtension>

Extension field.

name: Option<String>

Informal name of the executed TestReport

A free text natural language name identifying the executed TestReport.

Not expected to be globally unique.

name_ext: Option<FieldExtension>

Extension field.

status: TestReportStatus

TestReportStatus; completed | in-progress | waiting | stopped | entered-in-error

The current state of this test report.

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.

status_ext: Option<FieldExtension>

Extension field.

test_script: String

Canonical URL 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.

test_script_ext: Option<FieldExtension>

Extension field.

result: TestReportResult

TestReportResult; pass | fail | pending

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.

result_ext: Option<FieldExtension>

Extension field.

score: Option<f64>

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.

score_ext: Option<FieldExtension>

Extension field.

tester: Option<String>

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.

tester_ext: Option<FieldExtension>

Extension field.

issued: Option<DateTime>

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.

issued_ext: Option<FieldExtension>

Extension field.

participant: Vec<Option<TestReportParticipant>>

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.

participant_ext: Vec<Option<FieldExtension>>

Extension field.

setup: Option<TestReportSetup>

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.

setup_ext: Option<FieldExtension>

Extension field.

test: Vec<Option<TestReportTest>>

A test executed from the test script

A test executed from the test script.

test_ext: Vec<Option<FieldExtension>>

Extension field.

teardown: Option<TestReportTeardown>

The results of running the series of required clean up steps

The results of the series of operations required to clean up after all the tests were executed (successfully or otherwise).

teardown_ext: Option<FieldExtension>

Extension field.

Trait Implementations

impl Clone for TestReportInner

fn clone(&self) -> TestReportInner

Returns a duplicate of the value.

fn clone_from(&mut self, source: &Self)

Performs copy-assignment from source.

impl Debug for TestReportInner

fn fmt(&self, f: &mut Formatter<'_>) -> Result<(), Error>

Formats the value using the given formatter.

impl<'de> Deserialize<'de> for TestReportInner

fn deserialize<__D>( __deserializer: __D, ) -> Result<TestReportInner, <__D as Deserializer<'de>>::Error>

where __D: Deserializer<'de>,

Deserialize this value from the given Serde deserializer.

impl From<TestReportInner> for TestReport

fn from(inner: TestReportInner) -> TestReport

Converts to this type from the input type.

impl PartialEq for TestReportInner

fn eq(&self, other: &TestReportInner) -> bool

Tests for self and other values to be equal, and is used by ==.

fn ne(&self, other: &Rhs) -> bool

Tests for !=. The default implementation is almost always sufficient, and should not be overridden without very good reason.

impl Serialize for TestReportInner

fn serialize<__S>( &self, __serializer: __S, ) -> Result<<__S as Serializer>::Ok, <__S as Serializer>::Error>

where __S: Serializer,

Serialize this value into the given Serde serializer.

impl StructuralPartialEq for TestReportInner