Page Comparison

...

• A depending ServiceRequest (related to an ActivityDefinition which is a depending action) has

  • trigger-enablement set to TRIGGER_ENABLED.

• A triggering ServiceRequest (related to an ActivityDefinition which is a triggering action) has

  • trigger-enablement set to NO_TRIGGER

  • meta.tag set to a Coding corresponding to trigger (see https://docs.ehealth.sundhed.dk/latest-released/ig/CodeSystem-ehealth-action-type.html ).

In the example below, the a PlanDefinition contains containing an action trigger where activity “action[2]” has dependencies to “action[0]” and “action[1]” . As a result of applying it to CarePlan and ServiceRequest resources, the action trigger and its trigger conditions manifest themselves in the ServiceRequest resources as follows (and shown in the figure below)has been applied to a CarePlan and ServiceRequest resources:

• The depending ServiceRequest SR2 (related to ActivityDefinition AD2, with has action trigger set) has trigger-enablement set to TRIGGER_ENABLED.

  • In this case, the action trigger for the action[2] (ActivityDefinition AD2) has trigger reaction set to “activation from on-hold to active”, which is why the ServiceRequest SR2 is initially with status set to on-hold.

• The triggering ServiceRequest resources SR0 and SR1 have:

  • trigger-enablement set to NO_TRIGGER (because they themselves are not depending on others)

  • meta.tag set to trigger

...