clarify tasks can be continuous

[joostholslag]

Many care plan tasks "e.g. call doctor when blood pressure is above 180", are continuous, can be open for years until death. the sequence diagrams to me imply these tasks are only for short term tasks. please clarify.

[joostholslag]

also: be careful with mixing a technical status (message received) with a clinical status (patient accepted).

[jorritspee]

In your example I think "call doctor when blood pressure is above 180" should maybe not be modeled using a Task but using a Request-resource (using e.g. ServiceRequest.orderDetail). If a party agrees to do "call doctor when blood pressure is above 180" it can accept the Task that is linked to that Request-resource, and the Request-resource can get the status "active". And it will probably stay "active" for as long as the policy "call doctor when blood pressure is above 180" is in place.

Technical statusses (message received) are modelled in the Task.status. Clinical statuses (patient accepted) are modelled in the ServiceRequest.status.

Could you check this answer @bramwesselo?

[bramwesselo]

Agree. Sidenote for clinical-status 'patient accepted': This status does not exist in Task.status nor in ServiceRequest.status. However, it could be (implicit) part/prerequisite of the ServiceRequest.status 'active'.