Internally, Interactive PMCube Explorer stores the loaded event logs in the usual hierarchical structure: An event log consists of a set of cases while each case owns an ordered set of events (the trace). Both, cases and events may have arbitrary attributes. When reading the data from the database, the scope tells the parser whether to attach an attribute value to an event or a case. Therefore, for each dimension and simple attribute defines default scope in the meta-data. However, if there are more than one case id candidates, the scope may vary depending on the selected case id. If, for example, each stay is selected as the case id of a hospital event log, the admittance date needs to be mapped to the case because it is the same for all events of the same case. If the patient himself is selected as the case id, there may be multiple admittance dates which need to be mapped to the events. Consequently, for each dimension and simple attribute in the meta-data, you can define alternative scopes for particular case ids.

You can add an alternative scope by clicking on  in the tool bar of the Alternative Scopes section. In the pop-up window, you can select the case id (only attributes annotated as case id are shown) and the respective scope. The new mapping will then be displayed in the list. You can edit / remove the selected mapping by clicking in the tool bar.

  • No labels