Page Comparison

...

A PlanDefinition is applied through the PlanDefinition$apply operation. This creates a number of CarePlan resources (typically one) and a ServiceRequest resource for each non-group action in the PlanDefinition.action (please note that PlanDefinition.action enables a recursive construct through its PlanDefinition.action.action).

...

• a reference to its corresponding ActivityDefinition

• status set to draft, with the following exception:

  • status is set to on-hold when the ServiceRequest is a depending ServiceRequest (see below)

• a copy of the corresponding ActivityDefinition reuse criteria, if any

• a copy of the corresponding ActivityDefinition sharing policy, if any

• a copy of the corresponding ActivityDefinition Sharing Approval Policydocument registering approval policy, if any

• a copy of the corresponding ActivityDefinition measurement ranges, if any

• an initial, relative measurement regime in ServiceRequest.occurrence[x] which is a copy of the measurement regime appearing for the action, if any. Note that the measurement regime in PlanDefinition.action.timing[x] takes precedence over ActivityDefinition.timing[x] for ActivityDefinition referenced in PlanDefinition.action.definition.

• a copy of the includeAsExtra extension for the corresponding PlanDefinition.action . If the PlanDefinition.action does not contain the extension, and extension with value false is added to the ServiceRequest

At some point before a ServiceRequest has status set to active, its measurement regime must be defined with a starting date/time.

...

In the PlanDefinition.action[i].actionTrigger (see https://docs.ehealth.sundhed.dk/latest-releasedfhir/ig/StructureDefinition-ehealth-plandefinition-definitions.html#PlanDefinition.action.extension:ehealth-actionTrigger )

• a depending action is the action for which the actionTrigger is defined.

• one or more triggering actions are those that the depending action is depending on and for which trigger conditions and behavior is defined in the trigger action.

...

• 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/igfhir/CodeSystem-ehealth-action-type.html ).

In the example below, a PlanDefinition containing an action trigger where activity “action[2]” has dependencies to “action[0]” and “action[1]” has been applied to a CarePlan and ServiceRequest resources:

...