...
- Can be repeated after 15 mins, then every hour as needed - means to have a monitoring task every hour.
More Kinds of Tasks needed
Reflection on the Moscow Stroke workflow indicates that we should probably hard-model some of the Task subtypes that are implicated, as shown below.
Here we distinguish some specific types of Tasks:
- PROXY_TASK - a kind of LINKED_TASK pointing to another TASK_PLAN in the same Plan Group that is performed by the same performer;
- HAND_OFF - a kind of LINKED_TASK pointing to another TASK_PLAN in the same Plan Group that is performed by a different performer - this probably needs to be distinguished, because any handoff inevitably involves the notion of waiting (or not), time-outs etc;
- EXTERNAL_HANDOFF - a kind of TASK that hands off to a TASK_PLAN outside the current Plan Group - i.e. a request to an organisation / party to do something, such as an order, referral, or simple task, like 'check patient nutrition';
- ACTION_TASK - a kind of DEFINED_TASK that is a 'doing' Task, and would be reported using an ACTION Entry;
- DATA_CAPTURE_TASK - a kind of DEFINED_TASK that involves obtaining data from / about the subject of care, documented with an OBSERVATION;
The names used for these classes could easily be changed, and it is not clear if any / all are needed. To be discussed.
Other
Alternative to single Task Plan 'definition': setup, main, cleanup, all of type TASK_GROUP - would address task plans with that kind of structure, and make repetition clearer.
...