Struct ExampleScenarioProcessStep

pub struct ExampleScenarioProcessStep {

    pub id: Option<String>,
    pub extension: Vec<Extension>,
    pub modifier_extension: Vec<Extension>,
    pub number: Option<String>,
    pub number_ext: Option<FieldExtension>,
    pub process: Option<ExampleScenarioProcess>,
    pub process_ext: Option<FieldExtension>,
    pub workflow: Option<String>,
    pub workflow_ext: Option<FieldExtension>,
    pub operation: Option<ExampleScenarioProcessStepOperation>,
    pub operation_ext: Option<FieldExtension>,
    pub alternative: Vec<Option<ExampleScenarioProcessStepAlternative>>,
    pub alternative_ext: Vec<Option<FieldExtension>>,
    pub pause: Option<bool>,
    pub pause_ext: Option<FieldExtension>,
}

Sub-fields of the step field in ExampleScenarioProcess

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.

number: Option<String>

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

number_ext: Option<FieldExtension>

Extension field.

process: Option<ExampleScenarioProcess>

Step is nested process

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

process_ext: Option<FieldExtension>

Extension field.

workflow: Option<String>

Step is nested workflow

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

workflow_ext: Option<FieldExtension>

Extension field.

operation: Option<ExampleScenarioProcessStepOperation>

Step is simple action

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

operation_ext: Option<FieldExtension>

Extension field.

alternative: Vec<Option<ExampleScenarioProcessStepAlternative>>

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.

alternative_ext: Vec<Option<FieldExtension>>

Extension field.

pause: Option<bool>

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).

pause_ext: Option<FieldExtension>

Extension field.

Implementations

impl ExampleScenarioProcessStep

pub fn builder() -> ExampleScenarioProcessStepBuilder

Start building a new instance

Trait Implementations

impl Clone for ExampleScenarioProcessStep

fn clone(&self) -> ExampleScenarioProcessStep

Returns a duplicate of the value.

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

Performs copy-assignment from source.

impl Debug for ExampleScenarioProcessStep

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

Formats the value using the given formatter.

impl<'de> Deserialize<'de> for ExampleScenarioProcessStep

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

where __D: Deserializer<'de>,

Deserialize this value from the given Serde deserializer.

impl PartialEq for ExampleScenarioProcessStep

fn eq(&self, other: &ExampleScenarioProcessStep) -> 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 ExampleScenarioProcessStep

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 ExampleScenarioProcessStep