...
At some point before a ServiceRequest has status set to active, its measurement regime must be defined with a starting date/time.
| 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.
|
| Note |
|---|
It is expected that a Telemedicine Solution intended for employees guides the user in setting ServiceRequest starting date/time even when initially set with status on-hold as is the case for a depending ServiceRequest. A depending ServiceRequest with status set to on-hold (as described below) can have its status changed automatically to active when its trigger conditions are met. See https://ehealth-dk.atlassian.net/wiki/spaces/EDTW/pages/538935313/Behind+the+Scenes#Automated-Processing-of-Triggering-Conditions for further details on this automatic change. |
Action Triggers and Trigger Conditions
...
| 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.
|