Versions Compared

Old Version 13

changes.mady.by.user Erik Nielsen

Saved on

compared with

New Version 14

changes.mady.by.user Erik Nielsen

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

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

Trigger Actions and Trigger Conditions

In the example below, the PlanDefinition contains trigger conditions where activity “action[2]” has an actionTrigger with dependencies to “action[0]” and “action[1]”. When applied to a CarePlan and ServiceRequest, these triggering conditions manifest themselves in the ServiceRequest resources as follows (and shown in the figure below):

  • A depending ServiceRequest (related to an ActivityDefinition, here AD2, with trigger conditions set) depending on trigger conditions to be met in other ServiceRequest has trigger-enablement set to TRIGGER_ENABLED.

    • In this case, the trigger condition for the 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.

  • A triggering ServiceRequest (related to an ActivityDefinition, here this applies to AD0 and AD1, which another ActivityDefinition is depending on in its action trigger

Image Added

Note

It is expected that a Telemedicine Solution intended for employees guides the user in setting starting date/time for ServiceRequest even when initially set with status on-hold (as is the case for ServiceRequest referencing ActivityDefinition with trigger dependency expressed in PlanDefinition).

Note

It is expected that a Telemedicine Solution in some form provides information about the intended time-wise layout of activities captured in the PlanDefinition and ActivityDefinition resources which the citizen’s plan is based on. This includes intention captured in:

  • PlanDefinition.action.timing[x] (which is copied to ServiceRequest.occurrence[x] initially, if present)

  • PlanDefinition.action.relatedAction (actionId, relationship and possible offset[x])

  • ActivityDefinition.timing[x] in ActivityDefinition referenced from ServiceRequest.instantiatesCanonical - This timing could specify a duration.

...