Struct ExampleScenarioProcessStepBuilder

pub struct ExampleScenarioProcessStepBuilder { /* private fields */ }

Builder for ExampleScenarioProcessStep.

Implementations

impl ExampleScenarioProcessStepBuilder

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

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>, ) -> ExampleScenarioProcessStepBuilder

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>, ) -> ExampleScenarioProcessStepBuilder

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 number(self, value: String) -> ExampleScenarioProcessStepBuilder

Sequential number of the step

The sequential number of the step, e.g. 1.2.5.

If step numbers are simultaneous, they will be the same. Numbers don’t have to be numeric. E.g. ‘2c)’ is a valid step number

pub fn number_ext( self, value: FieldExtension, ) -> ExampleScenarioProcessStepBuilder

Extension field.

pub fn process( self, value: ExampleScenarioProcess, ) -> ExampleScenarioProcessStepBuilder

Step is nested process

Indicates that the step is a complex sub-process with its own steps.

pub fn process_ext( self, value: FieldExtension, ) -> ExampleScenarioProcessStepBuilder

Extension field.

pub fn workflow(self, value: String) -> ExampleScenarioProcessStepBuilder

Step is nested workflow

Indicates that the step is defined by a seaparate scenario instance.

pub fn workflow_ext( self, value: FieldExtension, ) -> ExampleScenarioProcessStepBuilder

Extension field.

pub fn operation( self, value: ExampleScenarioProcessStepOperation, ) -> ExampleScenarioProcessStepBuilder

Step is simple action

The step represents a single operation invoked on receiver by sender.

pub fn operation_ext( self, value: FieldExtension, ) -> ExampleScenarioProcessStepBuilder

Extension field.

pub fn alternative( self, value: Vec<Option<ExampleScenarioProcessStepAlternative>>, ) -> ExampleScenarioProcessStepBuilder

Alternate non-typical step action

Indicates an alternative step that can be taken instead of the sub-process, scenario or operation. E.g. to represent non-happy-path/exceptional/atypical circumstances.

pub fn alternative_ext( self, value: Vec<Option<FieldExtension>>, ) -> ExampleScenarioProcessStepBuilder

Extension field.

pub fn pause(self, value: bool) -> ExampleScenarioProcessStepBuilder

Pause in the flow?

If true, indicates that, following this step, there is a pause in the flow and the subsequent step will occur at some later time (triggered by some event).

pub fn pause_ext( self, value: FieldExtension, ) -> ExampleScenarioProcessStepBuilder

Extension field.

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

Builds a new ExampleScenarioProcessStep.

Errors

If a required field has not been initialized.

Trait Implementations

impl Default for ExampleScenarioProcessStepBuilder

fn default() -> ExampleScenarioProcessStepBuilder

Returns the “default value” for a type.