Struct ExampleScenarioProcess

pub struct ExampleScenarioProcess {

    pub id: Option<String>,
    pub extension: Vec<Extension>,
    pub modifier_extension: Vec<Extension>,
    pub title: String,
    pub title_ext: Option<FieldExtension>,
    pub description: Option<String>,
    pub description_ext: Option<FieldExtension>,
    pub pre_conditions: Option<String>,
    pub pre_conditions_ext: Option<FieldExtension>,
    pub post_conditions: Option<String>,
    pub post_conditions_ext: Option<FieldExtension>,
    pub step: Vec<Option<ExampleScenarioProcessStep>>,
    pub step_ext: Vec<Option<FieldExtension>>,
}

Sub-fields of the process field in ExampleScenario

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.

title: String

Label for procss

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

title_ext: Option<FieldExtension>

Extension field.

description: Option<String>

Human-friendly description of the process

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

description_ext: Option<FieldExtension>

Extension field.

pre_conditions: Option<String>

Status before process starts

Description of the initial state of the actors, environment and data before the process starts.

pre_conditions_ext: Option<FieldExtension>

Extension field.

post_conditions: Option<String>

Status after successful completion

Description of the final state of the actors, environment and data after the process has been successfully completed.

Alternate steps might not result in all post conditions holding

post_conditions_ext: Option<FieldExtension>

Extension field.

step: Vec<Option<ExampleScenarioProcessStep>>

Event within of the process

A significant action that occurs as part of the process.

step_ext: Vec<Option<FieldExtension>>

Extension field.

Implementations

impl ExampleScenarioProcess

pub fn builder() -> ExampleScenarioProcessBuilder

Start building a new instance

Trait Implementations

impl Clone for ExampleScenarioProcess

fn clone(&self) -> ExampleScenarioProcess

Returns a duplicate of the value.

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

Performs copy-assignment from source.

impl Debug for ExampleScenarioProcess

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

Formats the value using the given formatter.

impl<'de> Deserialize<'de> for ExampleScenarioProcess

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

where __D: Deserializer<'de>,

Deserialize this value from the given Serde deserializer.

impl PartialEq for ExampleScenarioProcess

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

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 ExampleScenarioProcess