pub struct SubscriptionTopicResourceTriggerQueryCriteriaBuilder { /* private fields */ }
Expand description
Builder for SubscriptionTopicResourceTriggerQueryCriteria
.
Implementations§
Source§impl SubscriptionTopicResourceTriggerQueryCriteriaBuilder
impl SubscriptionTopicResourceTriggerQueryCriteriaBuilder
Sourcepub fn id(
self,
value: String,
) -> SubscriptionTopicResourceTriggerQueryCriteriaBuilder
pub fn id( self, value: String, ) -> SubscriptionTopicResourceTriggerQueryCriteriaBuilder
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.
Sourcepub fn extension(
self,
value: Vec<Extension>,
) -> SubscriptionTopicResourceTriggerQueryCriteriaBuilder
pub fn extension( self, value: Vec<Extension>, ) -> SubscriptionTopicResourceTriggerQueryCriteriaBuilder
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.
Sourcepub fn modifier_extension(
self,
value: Vec<Extension>,
) -> SubscriptionTopicResourceTriggerQueryCriteriaBuilder
pub fn modifier_extension( self, value: Vec<Extension>, ) -> SubscriptionTopicResourceTriggerQueryCriteriaBuilder
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.
Sourcepub fn previous(
self,
value: String,
) -> SubscriptionTopicResourceTriggerQueryCriteriaBuilder
pub fn previous( self, value: String, ) -> SubscriptionTopicResourceTriggerQueryCriteriaBuilder
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 (/
).
Sourcepub fn previous_ext(
self,
value: FieldExtension,
) -> SubscriptionTopicResourceTriggerQueryCriteriaBuilder
pub fn previous_ext( self, value: FieldExtension, ) -> SubscriptionTopicResourceTriggerQueryCriteriaBuilder
Extension field.
Sourcepub fn result_for_create(
self,
value: CriteriaNotExistsBehavior,
) -> SubscriptionTopicResourceTriggerQueryCriteriaBuilder
pub fn result_for_create( self, value: CriteriaNotExistsBehavior, ) -> SubscriptionTopicResourceTriggerQueryCriteriaBuilder
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).
Sourcepub fn result_for_create_ext(
self,
value: FieldExtension,
) -> SubscriptionTopicResourceTriggerQueryCriteriaBuilder
pub fn result_for_create_ext( self, value: FieldExtension, ) -> SubscriptionTopicResourceTriggerQueryCriteriaBuilder
Extension field.
Sourcepub fn current(
self,
value: String,
) -> SubscriptionTopicResourceTriggerQueryCriteriaBuilder
pub fn current( self, value: String, ) -> SubscriptionTopicResourceTriggerQueryCriteriaBuilder
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 (/
).
Sourcepub fn current_ext(
self,
value: FieldExtension,
) -> SubscriptionTopicResourceTriggerQueryCriteriaBuilder
pub fn current_ext( self, value: FieldExtension, ) -> SubscriptionTopicResourceTriggerQueryCriteriaBuilder
Extension field.
Sourcepub fn result_for_delete(
self,
value: CriteriaNotExistsBehavior,
) -> SubscriptionTopicResourceTriggerQueryCriteriaBuilder
pub fn result_for_delete( self, value: CriteriaNotExistsBehavior, ) -> SubscriptionTopicResourceTriggerQueryCriteriaBuilder
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).
Sourcepub fn result_for_delete_ext(
self,
value: FieldExtension,
) -> SubscriptionTopicResourceTriggerQueryCriteriaBuilder
pub fn result_for_delete_ext( self, value: FieldExtension, ) -> SubscriptionTopicResourceTriggerQueryCriteriaBuilder
Extension field.
Sourcepub fn require_both(
self,
value: bool,
) -> SubscriptionTopicResourceTriggerQueryCriteriaBuilder
pub fn require_both( self, value: bool, ) -> SubscriptionTopicResourceTriggerQueryCriteriaBuilder
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.
Sourcepub fn require_both_ext(
self,
value: FieldExtension,
) -> SubscriptionTopicResourceTriggerQueryCriteriaBuilder
pub fn require_both_ext( self, value: FieldExtension, ) -> SubscriptionTopicResourceTriggerQueryCriteriaBuilder
Extension field.
Sourcepub fn build(
self,
) -> Result<SubscriptionTopicResourceTriggerQueryCriteria, BuilderError>
pub fn build( self, ) -> Result<SubscriptionTopicResourceTriggerQueryCriteria, BuilderError>
Builds a new SubscriptionTopicResourceTriggerQueryCriteria
.
§Errors
If a required field has not been initialized.