Struct ExampleScenarioProcessStepOperation

pub struct ExampleScenarioProcessStepOperation {

    pub id: Option<String>,
    pub extension: Vec<Extension>,
    pub modifier_extension: Vec<Extension>,
    pub type: Option<Coding>,
    pub type_ext: Option<FieldExtension>,
    pub title: String,
    pub title_ext: Option<FieldExtension>,
    pub initiator: Option<String>,
    pub initiator_ext: Option<FieldExtension>,
    pub receiver: Option<String>,
    pub receiver_ext: Option<FieldExtension>,
    pub description: Option<String>,
    pub description_ext: Option<FieldExtension>,
    pub initiator_active: Option<bool>,
    pub initiator_active_ext: Option<FieldExtension>,
    pub receiver_active: Option<bool>,
    pub receiver_active_ext: Option<FieldExtension>,
    pub request: Option<ExampleScenarioInstanceContainedInstance>,
    pub request_ext: Option<FieldExtension>,
    pub response: Option<ExampleScenarioInstanceContainedInstance>,
    pub response_ext: Option<FieldExtension>,
}

Sub-fields of the operation field in ExampleScenarioProcessStep

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.

type: Option<Coding>

; Kind of action

The standardized type of action (FHIR or otherwise).

type_ext: Option<FieldExtension>

Extension field.

title: String

Label for step

A short descriptive label the step to be used in tables or diagrams.

title_ext: Option<FieldExtension>

Extension field.

initiator: Option<String>

Who starts the operation

The system that invokes the action/transmits the data.

This must either be the ‘key’ of one of the actors defined in this scenario or the special keyword ‘OTHER’ if the initiator is not one of the actors defined for the scenario. (Multiple references to ‘OTHER’ don’t necessarily indicate the same actor.)

initiator_ext: Option<FieldExtension>

Extension field.

receiver: Option<String>

Who receives the operation

The system on which the action is invoked/receives the data.

This must either be the ‘key’ of one of the actors defined in this scenario or the special keyword ‘OTHER’ if the receiver is not one of the actors defined for the scenario. (Multiple references to ‘OTHER’ don’t necessarily indicate the same actor.) In some cases, receiver could be same as sender if representing a local operation

receiver_ext: Option<FieldExtension>

Extension field.

description: Option<String>

Human-friendly description of the operation

An explanation of what the operation represents and what it does.

This should contain information not already present in the process step. It’s more of a description of what the operation in general does - if not already evident from the operation.type

description_ext: Option<FieldExtension>

Extension field.

initiator_active: Option<bool>

Initiator stays active?

If false, the initiator is deactivated right after the operation.

De-activation of an actor means they have no further role until such time as they are the recipient of an operation.

initiator_active_ext: Option<FieldExtension>

Extension field.

receiver_active: Option<bool>

Receiver stays active?

If false, the receiver is deactivated right after the operation.

De-activation of an actor means they have no further role until such time as they are the recipient of an operation.

receiver_active_ext: Option<FieldExtension>

Extension field.

request: Option<ExampleScenarioInstanceContainedInstance>

Instance transmitted on invocation

A reference to the instance that is transmitted from requester to receiver as part of the invocation of the operation.

request_ext: Option<FieldExtension>

Extension field.

response: Option<ExampleScenarioInstanceContainedInstance>

Instance transmitted on invocation response

A reference to the instance that is transmitted from receiver to requester as part of the operation’s synchronous response (if any).

response_ext: Option<FieldExtension>

Extension field.

Implementations

impl ExampleScenarioProcessStepOperation

pub fn builder() -> ExampleScenarioProcessStepOperationBuilder

Start building a new instance

Trait Implementations

impl Clone for ExampleScenarioProcessStepOperation

fn clone(&self) -> ExampleScenarioProcessStepOperation

Returns a duplicate of the value.

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

Performs copy-assignment from source.

impl Debug for ExampleScenarioProcessStepOperation

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

Formats the value using the given formatter.

impl<'de> Deserialize<'de> for ExampleScenarioProcessStepOperation

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

where __D: Deserializer<'de>,

Deserialize this value from the given Serde deserializer.

impl PartialEq for ExampleScenarioProcessStepOperation

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

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 ExampleScenarioProcessStepOperation