pub struct TestReportTest {
pub id: Option<String>,
pub extension: Vec<Extension>,
pub modifier_extension: Vec<Extension>,
pub name: Option<String>,
pub name_ext: Option<FieldExtension>,
pub description: Option<String>,
pub description_ext: Option<FieldExtension>,
pub action: Vec<Option<TestReportTestAction>>,
pub action_ext: Vec<Option<FieldExtension>>,
}
Expand description
Sub-fields of the test field in TestReport
Fields§
§id: Option<String>
Unique id for inter-element referencing
Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
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 element. 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 even if unrecognized
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 in which it is contained 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 can 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.
name: Option<String>
Tracking/logging name of this test
The name of this test used for tracking/logging purposes by test engines.
name_ext: Option<FieldExtension>
Extension field.
description: Option<String>
Tracking/reporting short description of the test
A short description of the test used by test engines for tracking and reporting purposes.
description_ext: Option<FieldExtension>
Extension field.
action: Vec<Option<TestReportTestAction>>
A test operation or assert that was performed
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.
action_ext: Vec<Option<FieldExtension>>
Extension field.
Implementations§
Source§impl TestReportTest
impl TestReportTest
Sourcepub fn builder() -> TestReportTestBuilder
pub fn builder() -> TestReportTestBuilder
Start building a new instance
Trait Implementations§
Source§impl Clone for TestReportTest
impl Clone for TestReportTest
Source§fn clone(&self) -> TestReportTest
fn clone(&self) -> TestReportTest
1.0.0 · Source§fn clone_from(&mut self, source: &Self)
fn clone_from(&mut self, source: &Self)
source
. Read more