Ability to model ism_transitions

[thomas.beale]

@ian.mcnicoll

The Medication Action does work very well if you are trying to capture the actual individual prescribing cycle events ie, in a real prescribing system, burt Medication statement is a good example of a different pattern where all we re recording (or exposing) is essentially a ‘current_status’ summary of a live or recent medication order. That will include some sort of generic status (current. discontinued etc) but that may well be flattened in a slightly arbitrary way, and also include not just the current datetime for that status but other key dates like Date first prescribed, Date last dispensed, Date last authorised, ‘Date of last 5 issues’ depending on the use-case.

I just happened to see this - is the idea here that you would ideally like to have an RM attribute representing something like ‘lifecycle status’ (aka document / authoring status) for prescriptions, and Instructions more generally, and that this should be separate from Actions that actually flow from a confirmed or completed Instruction being performed by others?

This sounds like a sensible addition to me, and would correctly separate ‘actions’ on the prescription itself from actions undertaken to execute the prescription, which is what the Action ISM transition steps and careflow steps are about.

Have I got this right? Would it make sense to add such an attribute to the RM in Release 1.1.0?