Issues

Absolutely. Just made a care flow step which matches the intention with the corresponding state (completed or suspended).

I am on this topic because we have seen the same need on Taskplan. We've found the need to be able to actually close some processes as opposed to hibernate or suspend it.

For some activities, e.g. medication, completing and continuing are definite clinical decisions for which the “overhead” of a new request is fine. For some activities going on in a careplan we find this to produce “overhead” that feels very unnecessary. The request is to open up for some pragmatism in the modelling, where judged appropriate. In fact, in some situations the suggested approach seems to even match better with how users actually think of it.

This is the same as continuation or adjustment of a dose. The way to handle this is to issue a new request based on the previous and start the new activity. You might want to add a order_id or some other identification to tell that the INSTRUCTION is correlated or a follow up from a previous one.

@Bjørn Næss well normally, 'suspend' is a clinical decision that the patient can no longer have this medication or treatment at the moment, e.g. aspirin and other anti-coagulants will be suspended for surgery etc. This case I understand to be where the patient no longer needed the medication, but later on did, and the original order was still active/usable.

Why not use SUSPENDED and a CAREFLOW_STEP which covers the semantic of such a clinical decision?