Instruction State Machine SCHEDULED -> EXPIRED

Technical (archive)
1

Hi!

I just want to check if I understand the ISM intentions correctly…

In “FIGURE 24 openEHR standard Instruction State Machine” in http://www.openehr.org/releases/1.0.2/architecture/rm/ehr_im.pdf there is no path from SCHEDULED to EXPIRED.
Of course if something is scheduled but not done, it in reality is likely postponed or rescheduled…

…but from an EHR-algorithm’s perspective, if an action’s scheduled time passes and nothing has been reported to the EHR system yet (none of the allowed ACTIVE, POSTPONED or re-SCEDULED) what should the algorithm then conclude?
I assume the EHR state for the action stays on SCHEDULED but having a passed date. Is that correct? If so I guess out-of-date-finding mechanisms need to look both for EXPIRED-marked things and for SCHEDULED things past due date. Is that correct?

Best regards,
Erik Sundvall
erik.sundvall@liu.se http://www.imt.liu.se/~erisu/ Tel: +46-13-286733

2

this path is missing.... it obviously should be there. Erik, can you
raise this as an issue on http://www.openehr.org/issues/browse/SPECPR .
If you want to put some text with the issue that would end up in a new
version of the EHR IM spec, please do.

thanks

- thomas