FQL is a query language that allows you to retrieve, filter and project data from any data source containing FHIR Resources. It brings the power of three existing languages together: SQL, JSON and FhirPath. It allows you to create tables and is useful for gaining insight and perform quality control.
-
Default
What is FQL?
-
FQL Query resources
FQL Playground
Try Firely Query Language in our playground by using this scope as data source.
- FQL Documentation
-
FQL Language
Syntax specification
To learn more about FQL syntax choose this menu item.
-
YamlGen Generate resources
YamlGen Playground
Try YamlGen in our playground by using this scope as data source.
-
YamlGen Language
YamlGen Syntax specification
To learn more about YamlGen syntax choose this.
-
FHIRPath Inspect resource
FHIRPath Playground
Try out the FHIRPath playground and navigate inside this resource.
-
FHIRPath Documentation
FHIRPath Documentation
Find out what FHIRPath is or learn how to write FHIRPath scripts.
-
Project FHIR API
This is the location where you can find your resource using a FHIR client.
-
Simplifier FHIR API
The global endpoint is where users can search for all resources in Simplifier. Resources have a globally unique guid Id here.
-
Custom Example generation
Custom Example generation beta
Experiment with resource instance generation using YamlGen and based on this profile.
This feature is in beta. You can help us improve it by giving feedback with the feedback button at the top of the screen.
TriggerDefinition
Base StructureDefinition for TriggerDefinition Type: A description of a triggering event. Triggering events can be named events, data events, or periodic, as determined by the type element.
- type Profile on TriggerDefinition
- FHIR R4
- status Draft
-
version4.0.1
The canonical from this resource does not match any claim in this context and conflicts with a claim from another scope.
http://hl7.org/fhir
Canonical claims are used to verify ownership of your canonical URLs.
TriggerDefinition | I | Element | Element idTriggerDefinition Defines an expected trigger for a module DefinitionA 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.
| |
id | 0..1 | string | There are no (further) constraints on this element Element idTriggerDefinition.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idTriggerDefinition.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay 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. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
type | Σ | 1..1 | codeBinding | Element idTriggerDefinition.type named-event | periodic | data-changed | data-added | data-modified | data-removed | data-accessed | data-access-ended DefinitionThe type of triggering event. The type of trigger.
|
name | Σ | 0..1 | string | Element idTriggerDefinition.name Name or URI that identifies the event DefinitionA 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] | Σ | 0..1 | Element idTriggerDefinition.timing[x] Timing of the event DefinitionThe timing of the event (if this is a periodic trigger).
| |
timingTiming | Timing | Data type | ||
timingDate | date | Data type | ||
timingDateTime | dateTime | Data type | ||
timingReference | Reference(Schedule) | Data type | ||
data | Σ | 0..* | DataRequirement | Element idTriggerDefinition.data Triggering data of the event (multiple = 'and') DefinitionThe 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.
|
condition | Σ I | 0..1 | Expression | Element idTriggerDefinition.condition Whether the event triggers (boolean expression) DefinitionA boolean-valued expression that is evaluated in the context of the container of the trigger definition and returns whether or not the trigger fires. Need to be able to formally describe the triggering criteria. 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.
|