| Literature DB >> 30642000 |
Antonio Martinez-Millana1, Aroa Lizondo2, Roberto Gatta3, Salvador Vera4, Vicente Traver Salcedo5,6, Carlos Fernandez-Llatas7,8.
Abstract
The widespread adoption of real-time location systems is boosting the development of software applications to track persons and assets in hospitals. Among the vast amount of applications, real-time location systems in operating rooms have the advantage of grounding advanced data analysis techniques to improve surgical processes, such as process mining. However, such applications still find entrance barriers in the clinical context. In this paper, we aim to evaluate the preferred features of a process mining-based dashboard deployed in the operating rooms of a hospital equipped with a real-time location system. The dashboard allows to discover and enhance flows of patients based on the location data of patients undergoing an intervention. Analytic hierarchy process was applied to quantify the prioritization of the dashboard features (filtering data, enhancement, node selection, statistics, etc.), distinguishing the priorities that each of the different roles in the operating room service assigned to each feature. The staff in the operating rooms (n = 10) was classified into three groups: Technical, clinical, and managerial staff according to their responsibilities. Results showed different weights for the features in the process mining dashboard for each group, suggesting that a flexible process mining dashboard is needed to boost its potential in the management of clinical interventions in operating rooms. This paper is an extension of a communication presented in the Process-Oriented Data Science for Health Workshop in the Business Process Management Conference 2018.Entities:
Keywords: analytic hierarchy process; co-design; operating rooms; process mining; software; usability
Mesh:
Year: 2019 PMID: 30642000 PMCID: PMC6352092 DOI: 10.3390/ijerph16020199
Source DB: PubMed Journal: Int J Environ Res Public Health ISSN: 1660-4601 Impact factor: 3.390
Figure 1Composition of the operating room service.
Figure 2Example of the inferred and enhanced work flows of patients across the operating room service [11].
Figure 3Areas of the process mining dashboard.
Structure and items of the filters area in the process mining dashboard under evaluation.
| Item ID | Name | Area | Description |
|---|---|---|---|
| L1.1 | Date | Filter | To select a specific range of dates (e.g., a day, a week, a month). |
| L1.2 | Time | Filter | To select a specific time interval from the corpus (e.g., 9:00–14:00). |
| L1.3 | Duration | Filter | Allows to filter traces that have a specific minimum and maximum duration (e.g., ≥ 60 min) |
| L1.4 | Level | Filter | The real-time location system (RTLS) aggregates operating rooms (ORs) into different levels. There are levels that contain the small areas and levels that group different areas, generating more global location zones, for example, on one level, we can find “Operating Room 1”, “Operating Room 2”, etc. and on another level, these areas are grouped within the “Operating Rooms Level 0”. This filter allows users to define the granularity of the area for the process mining analysis. More than one level can be selected at the same time. |
| L1.5 | Name of the nodes | Filter | This filter shows the names of the nodes or areas within the location of the system (e.g., |
| L1.6 | Features | Filter | This filter allows to select and display only the data that comply with all the characteristics that are selected (e.g., type of surgical procedure, surgeon). Such data are typically available as metadata of the RTLS. |
| L1.7 | Stretch | Filter | This filter allows to select samples/traces which go through a given node or which go from one given source node to a given target node. It is also possible to limit the number nodes in the trace (e.g., samples with more than 3 nodes). |
| L1.8 | Dis-gregation | Filter | This filter allows to divide the corpus of data into several corpus, grouping the samples by their percentage of similarity. Samples not matching the similarity index are grouped into an outliers pool. |
| L1.9 | Statistics | Filter | This filters allows to display the percentage of samples of the flows that meet a given characteristic. In addition, these percentages can be grouped if they are less than a given value. |
Structure and items of the mining area in the process mining dashboard under evaluation.
| Item ID | Name | Area | Description |
|---|---|---|---|
| L2.1 | Frequency | Mining | Shows the work flow in the form of a heat map, indicating which elements occur more frequently or for a longer time. |
| L2.2 | Occupation | Mining | Shows the work flow in the form of a heat map, indicating which nodes/locations are most occupied at a moment in time. |
| L2.3 | Transitions | Mining | Highlights in the work flow round-trip steps (jumps) for a node. |
| L2.4 | List of samples | Mining | Shows a list of all the samples that are in a trace or work flow. By clicking on a sample, the pathway is highlighted on the display. |
Structure and items of the information area in the process mining dashboard under evaluation.
| Item ID | Name | Area | Description |
|---|---|---|---|
| L3.1 | Sample cleaning | Information | Information related to the correction of the corpus by erasing automatically implausible samples or samples with incorrect data. |
| L3.2 | Wrong Selection | Information | Console to display error messages in the configuration of filters, sample identification or mining. |
| L3.3 | Evolution of process | Information | A log of actions executed when the inference engine starts (e.g., selecting data, filtering dates, filtering times, grouping samples). |
| L3.4 | Error Messages | Information | Error messages while the inference engine is being executed (e.g., the configuration of filters entails the in-existence of samples). |
| L3.5 | Extra information | Information | Extra information about the entire process (e.g., console messages, warnings). |
Questionnaire for the qualitative study of the dashboard usability.
| Item ID | Question | Type of Response |
|---|---|---|
| Q1 | I think that I would like to use the dashboard in my daily routine | 5-item Likert |
| Q2 | I found the dashboard to be simple | 5-item Likert |
| Q3 | I think the dashboard is easy to use | 5-item Likert |
| Q4 | I think I could use the dashboard without the support of a technical person | 5-item Likert |
| Q5 | I found the functions of the dashboard well integrated | 5-item Likert |
| Q6 | I thought there was a lot of consistency in the dashboard | 5-item Likert |
| Q7 | I am missing some functionalities in the dashboard | Open answer |
| Q8 | I would remove the following functionalities from the dashboard | Open answer |
| Q9 | I felt very confident using the dashboard and it was very intuitive | 5-item Likert |
| Q10 | I would use the dashboard in other hospital processes | Open answer |
Profiles of the participants in the analytic hierarchy process (AHP) study.
| Variable | Type | Distribution |
|---|---|---|
| Role | Manager | 20 % |
| Clinical staff | 60 % | |
| Technical | 20 % | |
| Age | 46.2 ±10.3 | |
| Gender | Male | 40% |
| Female | 60% | |
| Years of expertise | 21.2 ±10.7 | |
| Computer literacy | Low | 0% |
| Medium | 70% | |
| High | 30% |
Figure 4Assigned priorities for the functional areas.
Figure 5Priorities for filter functional module features.
Figure 6Priorities for miner functional module features.
Figure 7Priorities for information functional module features.
Figure 8Priorities for information functional module features.