pub struct TestScriptMetadataBuilder { /* private fields */ }
Expand description
Builder for TestScriptMetadata
.
Implementations§
Source§impl TestScriptMetadataBuilder
impl TestScriptMetadataBuilder
Sourcepub fn id(self, value: String) -> TestScriptMetadataBuilder
pub fn id(self, value: String) -> TestScriptMetadataBuilder
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.
Sourcepub fn extension(self, value: Vec<Extension>) -> TestScriptMetadataBuilder
pub fn extension(self, value: Vec<Extension>) -> TestScriptMetadataBuilder
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.
Sourcepub fn modifier_extension(
self,
value: Vec<Extension>,
) -> TestScriptMetadataBuilder
pub fn modifier_extension( self, value: Vec<Extension>, ) -> TestScriptMetadataBuilder
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.
Sourcepub fn link(
self,
value: Vec<Option<TestScriptMetadataLink>>,
) -> TestScriptMetadataBuilder
pub fn link( self, value: Vec<Option<TestScriptMetadataLink>>, ) -> TestScriptMetadataBuilder
Links to the FHIR specification
A link to the FHIR specification that this test is covering.
Sourcepub fn link_ext(
self,
value: Vec<Option<FieldExtension>>,
) -> TestScriptMetadataBuilder
pub fn link_ext( self, value: Vec<Option<FieldExtension>>, ) -> TestScriptMetadataBuilder
Extension field.
Sourcepub fn capability(
self,
value: Vec<Option<TestScriptMetadataCapability>>,
) -> TestScriptMetadataBuilder
pub fn capability( self, value: Vec<Option<TestScriptMetadataCapability>>, ) -> TestScriptMetadataBuilder
Capabilities that are assumed to function correctly on the FHIR server being tested
Capabilities that must exist and are assumed to function correctly on the FHIR server being tested.
When the metadata capabilities section is defined at TestScript.metadata or at TestScript.setup.metadata, and the server’s conformance statement does not contain the elements defined in the minimal conformance statement, then all the tests in the TestScript are skipped. When the metadata capabilities section is defined at TestScript.test.metadata and the server’s conformance statement does not contain the elements defined in the minimal conformance statement, then only that test is skipped. The “metadata.capabilities.required” and “metadata.capabilities.validated” elements only indicate whether the capabilities are the primary focus of the test script or not. They do not impact the skipping logic. Capabilities whose “metadata.capabilities.validated” flag is true are the primary focus of the test script.
Sourcepub fn capability_ext(
self,
value: Vec<Option<FieldExtension>>,
) -> TestScriptMetadataBuilder
pub fn capability_ext( self, value: Vec<Option<FieldExtension>>, ) -> TestScriptMetadataBuilder
Extension field.