Cost analysis is another type of specialized module, like Protocols or Workflow. However, unlike them, if the costs structure is defined, it has multiple implications throughout the application, not just on one panel.
In a simple form, the cost analysis allows user to associate each event with its own unique monetary value.
The Costs, average and total, therefore becomes two new metrics, like Duration or Event Count. As a result, Cost metrics are displayed in the metric boxes and can be built into dashboards. Costs will also be displayed to the user as one of the selected metrics on top of the columns in Path Analysis, on top of the paths, in addition to the counts for each path.
Keep in mind, the metric Total Costs doesn’t have the histogram and could not be used as a filter. It could still be displayed in the metric box or dashboard.
As a result, unlike other “analysis”, the Cost Analysis is basically a configuration. Once the costs metric is defined, it’s used in other analysis and panels.
Once the costs are defined (it means it has either fixed or time costs or both), the costs metrics, Total and Average Costs, appear everywhere – where there are metrics.
Definition of costs
Costs are defined per 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 number entered by the user into a field (for example – $10 for PatientArrived event), and
- The amount comes from an attribute of the event (for example – attribute SurgeryPrice from Surgery event), and
- The amount comes from the lookup table based on the values of some attributes of the event. The table could be:
- Populated by user on screen, or
- Loaded from the file.
- The time costs defined by interval and rate.
- The interval could be defined by:
- Second timestamp attribute in the event.
- Next event (any kind)
Specific event could be any subsequent event or defined as one or more specific events. Also in this and the previous cases, the user could specify the matching attribute, like we do it interval measurement.
If the tine is defined by second timestamp or any next event, the time rate depends on the attributes of the event. If the time comes from the specific second event, the rate could be defined by the attributes of both events, exactly like described above for the fixed cost.
Example Video Demonstration
For the event TriageStarted, the fixed cost consists of value of attribute SupplyCost and the value which comes from the look up table based on the attribute AcuityLevel. For the time cost, the time interval is defined from this event to next TriageCompleted event. The time rate depends on the attribute TriageCompleted.DoctorName.
Add and Define new cost: