Name Flags Card. Type Description & Constraints TriggerDefinition ΣN Element Defines an expected trigger for a module + Rule: Either timing, or a data requirement, but not both + Rule: A named event requires a name or code, a periodic event requires timing, a data event requires data, and a subscription topic requires a reference to a subscription topic Elements defined in Ancestors: id, <a href="types.html#Element" title="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.">extension #xD; type ΣC 1..1 code named-event | periodic | data-changed | data-added | data-modified | data-removed | data-accessed | data-access-ended | subscription-topic Binding: TriggerType (Required) #xD; name ΣC 0..1 string Name or URI that identifies the event #xD; code ΣC 0..1 CodeableConcept Coded definition of the event #xD; subscriptionTopic ΣC 0..1 canonical(SubscriptionTopic) What event #xD; timing[x] ΣC 0..1 Timing of the event #xD; timingTiming Timing #xD; timingDate date #xD; timingDateTime dateTime #xD; data ΣC 0..* DataRequirement Triggering data of the event (multiple = 'and') #xD; condition Σ 0..1 Expression Whether the event triggers (boolean expression) #xD; Documentation for this format
TriggerDefinition Type: A description of a triggering event. Triggering events can be named events, data events, or periodic, as determined by the type element.
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.
All FHIR elements must have a @value or children
hasValue() or (children().count() > id.count())
Either timing, or a data requirement, but not both
A named event requires a name or code, a periodic event requires timing, a data event requires data, and a subscription topic requires a reference to a subscription topic
(type = 'named-event' implies (name.exists() or code.exists())) and (type = 'periodic' implies timing.exists()) and (type.startsWith('data-') implies data.exists()) and (type = 'subscription-topic' implies subscriptionTopic.exists())
Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
Extensions are always sliced by (at least) url
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.
named-event | periodic | data-changed | data-added | data-modified | data-removed | data-accessed | data-access-ended | subscription-topic
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.
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.
The timing of the event (if this is a periodic trigger).
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.
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 specified for any type of trigger and provides additional criteria for the trigger. The context available within the condition is based on the type of 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.
Need to be able to formally describe the triggering criteria.