Cost configuration

Main use

Cost analysis is a specialized module. If the cost structure is defined, it has multiple implications throughout the application, not just on one panel. Simply put, the cost analysis allows users to associate a unique monetary value to each event. This can be a fixed or variable cost.

To use this tool, select the Tool > Cost configuration menu.

Overview

The costs are made up of average and total costs, and are therefore displayed as two separate metrics in the metrics boxes and can be built into dashboards. Costs will also display to the users as one of the selected metrics at the top of the columns in Path analysis.

The Total Costs metric does not include the histogram and cannot be used as a filter. It can still be displayed in the metrics box or dashboard.

As a result, unlike other analysis types, the Cost Analysis tool is basically a configuration. Once the costs metric is defined, it’s used in other analysis tools on the platform.

Visualization

Once the costs are defined (either fixed or time costs or both), the total and average cost metrics appear everywhere where there are metrics.

Definition of costs

Costs are defined by the event. In the most general term, the costs include:

  • The fixed costs per event which could depends on the attributes values. The costs amount comes from:
    • The amount entered by the user into a field (for example – $10 for Patient Arrived event), and
    • The amount comes from an attribute of the event (for example – attribute Surgery Price from Surgery event), and
    • The amount comes from the lookup table based on the values of specified attributes of the event. The table could be:
      • Populated by user on screen, or
      • Loaded from the file.
  • The time based costs defined by interval and rate.
    • The interval could be defined by one of the following options:
      • Second timestamp attribute in the event

      • Any subsequent event

        Specific events could be any subsequent event

      • Specific subsequent event

        In this cases, you could specify the matching attribute.

      • The rate comes from one of the following options:

        • The amount entered by the user into a field, or
        • The amount comes from an attribute of the event, or
        • The amount comes from the lookup table based on the values of specified attributes of the event.