Struct TriggerDefinitionInner

pub struct TriggerDefinitionInner {

    pub id: Option<String>,
    pub extension: Vec<Extension>,
    pub type: TriggerType,
    pub type_ext: Option<FieldExtension>,
    pub name: Option<String>,
    pub name_ext: Option<FieldExtension>,
    pub code: Option<CodeableConcept>,
    pub code_ext: Option<FieldExtension>,
    pub subscription_topic: Option<String>,
    pub subscription_topic_ext: Option<FieldExtension>,
    pub timing: Option<TriggerDefinitionTiming>,
    pub timing_ext: Option<TriggerDefinitionTimingExtension>,
    pub data: Vec<Option<DataRequirement>>,
    pub data_ext: Vec<Option<FieldExtension>>,
    pub condition: Option<Expression>,
    pub condition_ext: Option<FieldExtension>,
}

TriggerDefinition Type: A description of a triggering event. Triggering events can be named events, data events, or periodic, as determined by the type element.

TriggerDefinition v5.0.0

Defines an expected trigger for a module

A description of a triggering event. Triggering events can be named events, data events, or periodic, as determined by the type element.

If an event is a named-event, it means the event is completely pre-coordinated, and no other information can be specified for the event. If the event is one of the data- events, the data and condition elements specify the triggering criteria. The data element specifies the structured component, and the condition element provides additional optional refinement of that structured component. If the event is periodic, the timing element defines when the event is triggered. For both data- and periodic events, a name can be provided as a shorthand for the formal semantics provided by the other elements.

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.

type: TriggerType

TriggerType; named-event | periodic | data-changed | data-added | data-modified | data-removed | data-accessed | data-access-ended

The type of triggering event.

type_ext: Option<FieldExtension>

Extension field.

name: Option<String>

Name or URI that identifies the event

A formal name for the event. This may be an absolute URI that identifies the event formally (e.g. from a trigger registry), or a simple relative URI that identifies the event in a local context.

An event name can be provided for all event types, but is required for named events. If a name is provided for a type other than named events, it is considered to be a shorthand for the semantics described by the formal description of the event.

name_ext: Option<FieldExtension>

Extension field.

code: Option<CodeableConcept>

Coded definition of the event

A code that identifies the event.

code_ext: Option<FieldExtension>

Extension field.

subscription_topic: Option<String>

What event

A reference to a SubscriptionTopic resource that defines the event. If this element is provided, no other information about the trigger definition may be supplied.

subscription_topic_ext: Option<FieldExtension>

Extension field.

timing: Option<TriggerDefinitionTiming>

Timing of the event

The timing of the event (if this is a periodic trigger).

timing_ext: Option<TriggerDefinitionTimingExtension>

Extension field.

data: Vec<Option<DataRequirement>>

Triggering data of the event (multiple = ‘and’)

The triggering data of the event (if this is a data trigger). If more than one data is requirement is specified, then all the data requirements must be true.

This element shall be present for any data type trigger.

data_ext: Vec<Option<FieldExtension>>

Extension field.

condition: Option<Expression>

Whether the event triggers (boolean expression)

A boolean-valued expression that is evaluated in the context of the container of the trigger definition and returns whether or not the trigger fires.

This element can be only be specified for data type triggers and provides additional semantics for the trigger. The context available within the condition is based on the type of data event. For all events, the current resource will be available as context. In addition, for modification events, the previous resource will also be available. The expression may be inlined, or may be a simple absolute URI, which is a reference to a named expression within a logic library referenced by a library element or extension within the containing resource. If the expression is a FHIR Path expression, it evaluates in the context of a resource of one of the type identified in the data requirement, and may also refer to the variable %previous for delta comparisons on events of type data-changed, data-modified, and data-deleted which will always have the same type.

condition_ext: Option<FieldExtension>

Extension field.

Trait Implementations

impl Clone for TriggerDefinitionInner

fn clone(&self) -> TriggerDefinitionInner

Returns a duplicate of the value.

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

Performs copy-assignment from source.

impl Debug for TriggerDefinitionInner

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

Formats the value using the given formatter.

impl<'de> Deserialize<'de> for TriggerDefinitionInner

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

where __D: Deserializer<'de>,

Deserialize this value from the given Serde deserializer.

impl From<TriggerDefinitionInner> for TriggerDefinition

fn from(inner: TriggerDefinitionInner) -> TriggerDefinition

Converts to this type from the input type.

impl PartialEq for TriggerDefinitionInner

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

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 TriggerDefinitionInner