pub struct SubscriptionTopicEventTrigger {
pub id: Option<String>,
pub extension: Vec<Extension>,
pub modifier_extension: Vec<Extension>,
pub description: Option<String>,
pub description_ext: Option<FieldExtension>,
pub event: CodeableConcept,
pub event_ext: Option<FieldExtension>,
pub resource: String,
pub resource_ext: Option<FieldExtension>,
}
Expand description
Sub-fields of the eventTrigger field in SubscriptionTopic
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.
description: Option<String>
Text representation of the event trigger
The human readable description of an event to trigger a notification for the SubscriptionTopic - for example, “Patient Admission, as defined in HL7v2 via message ADT^A01”. Multiple values are considered OR joined (e.g., matching any single event listed).
Implementation of particular subscription topics might not use a computable definition and instead base their design on the definition.
description_ext: Option<FieldExtension>
Extension field.
event: CodeableConcept
SubscriptionTopicEventTrigger; Event which can trigger a notification from the SubscriptionTopic
A well-defined event which can be used to trigger notifications from the SubscriptionTopic.
event_ext: Option<FieldExtension>
Extension field.
resource: String
FHIRTypes; Data Type or Resource (reference to definition) for this trigger definition
URL of the Resource that is the focus type used in this event trigger. Relative URLs are relative to the StructureDefinition root of the implemented FHIR version (e.g., http://hl7.org/fhir/StructureDefinition). For example, “Patient” maps to http://hl7.org/fhir/StructureDefinition/Patient. For more information, see ElementDefinition.type.code.
resource_ext: Option<FieldExtension>
Extension field.
Implementations§
Source§impl SubscriptionTopicEventTrigger
impl SubscriptionTopicEventTrigger
Sourcepub fn builder() -> SubscriptionTopicEventTriggerBuilder
pub fn builder() -> SubscriptionTopicEventTriggerBuilder
Start building a new instance
Trait Implementations§
Source§impl Clone for SubscriptionTopicEventTrigger
impl Clone for SubscriptionTopicEventTrigger
Source§fn clone(&self) -> SubscriptionTopicEventTrigger
fn clone(&self) -> SubscriptionTopicEventTrigger
1.0.0 · Source§fn clone_from(&mut self, source: &Self)
fn clone_from(&mut self, source: &Self)
source
. Read moreSource§impl<'de> Deserialize<'de> for SubscriptionTopicEventTrigger
impl<'de> Deserialize<'de> for SubscriptionTopicEventTrigger
Source§fn deserialize<__D>(
__deserializer: __D,
) -> Result<SubscriptionTopicEventTrigger, <__D as Deserializer<'de>>::Error>where
__D: Deserializer<'de>,
fn deserialize<__D>(
__deserializer: __D,
) -> Result<SubscriptionTopicEventTrigger, <__D as Deserializer<'de>>::Error>where
__D: Deserializer<'de>,
Source§impl PartialEq for SubscriptionTopicEventTrigger
impl PartialEq for SubscriptionTopicEventTrigger
Source§fn eq(&self, other: &SubscriptionTopicEventTrigger) -> bool
fn eq(&self, other: &SubscriptionTopicEventTrigger) -> bool
self
and other
values to be equal, and is used by ==
.