Struct SubscriptionTopicResourceTriggerQueryCriteria

pub struct SubscriptionTopicResourceTriggerQueryCriteria {

    pub id: Option<String>,
    pub extension: Vec<Extension>,
    pub modifier_extension: Vec<Extension>,
    pub previous: Option<String>,
    pub previous_ext: Option<FieldExtension>,
    pub result_for_create: Option<CriteriaNotExistsBehavior>,
    pub result_for_create_ext: Option<FieldExtension>,
    pub current: Option<String>,
    pub current_ext: Option<FieldExtension>,
    pub result_for_delete: Option<CriteriaNotExistsBehavior>,
    pub result_for_delete_ext: Option<FieldExtension>,
    pub require_both: Option<bool>,
    pub require_both_ext: Option<FieldExtension>,
}

Sub-fields of the queryCriteria field in SubscriptionTopicResourceTrigger

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.

previous: Option<String>

Rule applied to previous resource state

The FHIR query based rules are applied to the previous resource state (e.g., state before an update).

The rules are search criteria (without the [base] part). Like Bundle.entry.request.url, it has no leading slash character (/).

previous_ext: Option<FieldExtension>

Extension field.

result_for_create: Option<CriteriaNotExistsBehavior>

CriteriaNotExistsBehavior; test-passes | test-fails

For create interactions, should the previous criteria count as an automatic pass or an automatic fail. If not present, the testing behavior during create interactions is unspecified (server discretion).

result_for_create_ext: Option<FieldExtension>

Extension field.

current: Option<String>

Rule applied to current resource state

The FHIR query based rules are applied to the current resource state (e.g., state after an update).

The rules are search criteria (without the [base] part). Like Bundle.entry.request.url, it has no leading slash character (/).

current_ext: Option<FieldExtension>

Extension field.

result_for_delete: Option<CriteriaNotExistsBehavior>

CriteriaNotExistsBehavior; test-passes | test-fails

For ‘delete’ interactions, should the ‘current’ query criteria count as an automatic pass or an automatic fail. If not present, the testing behavior during delete interactions is unspecified (server discretion).

result_for_delete_ext: Option<FieldExtension>

Extension field.

require_both: Option<bool>

Both must be true flag

If set to true, both the current and previous query criteria must evaluate true to trigger a notification for this topic. If set to false or not present, a notification for this topic will be triggered if either the current or previous tests evaluate to true.

Please note the interaction between this element and the resultForCreate/resultForDelete elements during create and delete interactions. For example, if resultForCreate is set to test-passes, setting requireBoth to false means that every create will trigger a notification while setting requireBoth to true will result in notifications if the current test passes. Similarly, if resultForCreate is set to test-fails, setting requireBoth to true means that no create will be able to generate a notification while setting requireBoth to false will result in notifications if the current test passes.

require_both_ext: Option<FieldExtension>

Extension field.

Implementations

impl SubscriptionTopicResourceTriggerQueryCriteria

pub fn builder() -> SubscriptionTopicResourceTriggerQueryCriteriaBuilder

Start building a new instance

Trait Implementations

impl Clone for SubscriptionTopicResourceTriggerQueryCriteria

fn clone(&self) -> SubscriptionTopicResourceTriggerQueryCriteria

Returns a duplicate of the value.

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

Performs copy-assignment from source.

impl Debug for SubscriptionTopicResourceTriggerQueryCriteria

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

Formats the value using the given formatter.

impl<'de> Deserialize<'de> for SubscriptionTopicResourceTriggerQueryCriteria

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

where __D: Deserializer<'de>,

Deserialize this value from the given Serde deserializer.

impl PartialEq for SubscriptionTopicResourceTriggerQueryCriteria

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

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 SubscriptionTopicResourceTriggerQueryCriteria