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.
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 manageable, 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
The type of triggering event.
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.
|timing[x]||Timing, Reference<Schedule>, date, dateTime|
Timing of the event
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 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.