Interface ControlAct

An act representing a change to the state of another class, a user event (e.g. query), or a system event (e.g. time-based occurrences).

Examples: Discharging a patient (Encounter from Active to Completed); Stopping a medication (SubstanceAdministration from Active to Aborted); Sending an end-of-day summary (time-based event).

Discussion: This class corresponds to the concept of 'Trigger Event', and as such, must be present as the focus of every messaging interaction (because of the 1..1 association between a trigger event and an interaction.) However, control acts can also appear within a message payload. For example, a set of control acts associated with a Lab Order identifying the events that have occurred against that order (first created, then revised, then suspended, then resumed, then completed.)