Struct CapabilityStatementRestResourceOperationBuilder

pub struct CapabilityStatementRestResourceOperationBuilder { /* private fields */ }

Builder for CapabilityStatementRestResourceOperation.

Implementations

impl CapabilityStatementRestResourceOperationBuilder

pub fn id( self, value: String, ) -> CapabilityStatementRestResourceOperationBuilder

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.

pub fn extension( self, value: Vec<Extension>, ) -> CapabilityStatementRestResourceOperationBuilder

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.

pub fn modifier_extension( self, value: Vec<Extension>, ) -> CapabilityStatementRestResourceOperationBuilder

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.

pub fn name( self, value: String, ) -> CapabilityStatementRestResourceOperationBuilder

Name by which the operation/query is invoked

The name of the operation or query. For an operation, this name is prefixed with $ and used in the URL. For a query, this is the name used in the _query parameter when the query is called. This SHOULD be the same as the OperationDefinition.code of the defining OperationDefinition. However, it can sometimes differ if necessary to disambiguate when a server supports multiple OperationDefinition that happen to share the same code.

The name here SHOULD be the same as the OperationDefinition.code in the referenced OperationDefinition, unless there is a name clash and the OperationDefinition.code cannot be used. The name does not include the “$” portion that is always included in the URL. There is no correspondence whatsoever between CapabilityStatement’s operation.name and OperationDefinition.name - the latter is used as a class name when generating code for the operation. HL7 will never define operations that have conflicting names.

pub fn name_ext( self, value: FieldExtension, ) -> CapabilityStatementRestResourceOperationBuilder

Extension field.

pub fn definition( self, value: String, ) -> CapabilityStatementRestResourceOperationBuilder

The defined operation/query

Where the formal definition can be found. If a server references the base definition of an Operation (i.e. from the specification itself such as texthttp://hl7.org/fhir/OperationDefinition/ValueSet-expand), that means it supports the full capabilities of the operation - e.g. both GET and POST invocation. If it only supports a subset, it must define its own custom OperationDefinition with a ‘base’ of the original OperationDefinition. The custom definition would describe the specific subset of functionality supported.

This can be used to build an HTML form to invoke the operation, for instance.

pub fn definition_ext( self, value: FieldExtension, ) -> CapabilityStatementRestResourceOperationBuilder

Extension field.

pub fn documentation( self, value: String, ) -> CapabilityStatementRestResourceOperationBuilder

Specific details about operation behavior

Documentation that describes anything special about the operation behavior, possibly detailing different behavior for system, type and instance-level invocation of the operation.

pub fn documentation_ext( self, value: FieldExtension, ) -> CapabilityStatementRestResourceOperationBuilder

Extension field.

pub fn build( self, ) -> Result<CapabilityStatementRestResourceOperation, BuilderError>

Builds a new CapabilityStatementRestResourceOperation.

Errors

If a required field has not been initialized.

Trait Implementations

impl Default for CapabilityStatementRestResourceOperationBuilder

fn default() -> CapabilityStatementRestResourceOperationBuilder

Returns the “default value” for a type.