跳到正文
原文
Nature 健康护理主题·· 2026-10-05AI 评分31

DermaView 黑色素瘤临床仪表盘的用户中心迭代评估

Iterative user-centered evaluation of a context-driven clinical dashboard for melanoma treatment

AI 导读

针对黑色素瘤治疗场景,研究对临床仪表盘 DermaView 进行了迭代式用户中心评估。研究通过点击次数和程序切换次数衡量交互效率,采用标准化后研系统可用性问卷(PSSUQ)评估用户满意度,并结合Think-Aloud 会话和亲和图分析定性工作流整合情况。

正文

Introduction

In recent decades, the implementation of electronic health records (EHRs) at medical facilities has been aimed at making medical data more accessible for billing, research, and treatment support. To further enhance this process in Germany, data integration centers (DIC) were established at selected university hospitals1,2. These centers prioritize integrating data from disparate hospital information systems (HISs) into a hospital-wide platform, thereby enabling data accessibility across different software. At the University Hospital Essen (UME), this platform is known as the Smart Hospital Information Platform (SHIP), which accumulates data from the most relevant medical information systems into a fast healthcare interoperability resource (FHIR) server. While HISs primarily support billing processes, the data of these interoperable platforms are used mainly for medical research. The opportunities offered by implementing information access points for physicians at the point of care, however, have not been seized2.

A context analysis was conducted in a prior study, revealing that HISs used at the point of care scatter relevant information in different submodules and hierarchies of the program, which does not allow a direct overview of the patient’s status. In recent years, numerous clinical dashboards have been implemented to address this issue of information fragmentation. A recent review3 revealed 116 publications describing the development, implementation, and evaluation of 118 clinical dashboards from 2018 to 2020. Among these dashboards, 40% were designed to support direct patient care, whereas 70% were developed with physicians as the primary user group. Of these dashboards, 18 were developed in Europe, with no dashboards originating from Germany. Among the dashboards implemented for direct patient care, 43.5% were designed with user participation.

Although the number of clinical information systems and dashboards is growing, many of their development phases are still technology-driven rather than user or context-driven, resulting in software that is not sufficiently case specific4,5. In the context of patient care, where the need for immediate and accurate information is critical, clinicians need to focus on the information that is relevant to the current patient scenario while still offering immediate access to all other data related to that patient. Consequently, it is essential to build a solution that fits the sociotechnical context in which it will be used by conducting a workflow analysis5,6,7,8 and identifying workflow-dependent prioritized data and functionality9. Understanding and integrating the mental model of the users analyzed in these steps allows for workflow integrity10,11. The term “mental model” refers to the abstract cognitive representation of a task that users construct from knowledge, interpretation, and experience12. In the domain of human-computer interaction, these cognitive structures describe the understanding users have of their conceptual approach to a task. Therefore, in this study, the physicians’ mental model can be understood as their shared conceptualization of how to organize and access treatment-relevant patient information during tumor board preparation. In the absence of integration of a mental model, users have been observed to abandon systems where possible11,13 because systems with insufficient context integration cost additional time14 and cause more mental load14,15, leading to burnout16,17 and stress18 among physicians. In contrast, software that supports workflow and context integration improves patient safety7 by reducing workarounds19,20 and increasing the applicability of evidence-based treatment and decision making14. A context- and user-driven design allows the right information to be available at the right time and in the right format5,21, reducing redundant and ineffective activities5 and thereby increasing efficiency.

Therefore, the objective of this project is to evaluate the usability and workflow integration of DermaView, a patient dashboard (PDB) designed and implemented for physicians at the point of care in the treatment of melanoma patients. The evaluation specifically addresses the following points: The efficiency of interaction was measured by the number of clicks and program switches required to access treatment-relevant information. Perceived user satisfaction was assessed via the standardized Post-Study System Usability Questionnaire (PSSUQ). The qualitative workflow integration was analyzed through iterative Think-Aloud sessions and Affinity Diagrams. The development of the dashboard was founded upon a preliminary context analysis, which identified the mental model, pain points22, and workflow requirements23 of dermatology physicians interacting with established hospital information systems (HIS).

Methods

Ethics statement

This study was approved by the Ethics Committee of the Medical Faculty (approval number 22–10814-BO) of the University of Duisburg-Essen. The TA of the prior context analysis, on which the design of the dashboard was based, was also subject to approval by the Ethics Committee of the Faculty of Engineering (approval number 2111SPKA9493) of the same university. All procedures were performed in accordance with the ethical standards of the institutional research committee, the 1964 Helsinki Declaration, and its later amendments or comparable ethical standards. All the subjects provided their informed consent in written form for inclusion in the think-aloud method. The questionnaire did not include any personal data.

Approach

The development of PDB DermaView was founded on the findings from two prior studies that explored physicians’ workflow and information needs22,23 (see “Prior context analysis” section below). Figure 1 provides a schematic representation of the complete study design, including the initial context analysis, the design and implementation of the dashboard, and its iterative evaluation. Subsequent sections will concentrate on the evaluation phase, introducing only the results of the prior context analysis that influenced the design of the dashboard under evaluation.

The evaluation of the dashboard was conducted via the think-aloud method (TA). We employed this method in three iterations, involving a total of eleven sessions and nine different participants. The objective of this approach was to gain insights into the user’s interaction with the dashboard. The voices and screens of the participants were recorded. Owing to technical issues encountered during the first iteration, only the voice could be recorded. Additionally, after finishing the task, the participants completed the Post-Study System Usability Questionnaire (PSSUQ), a standardized questionnaire used to analyze perceived user satisfaction with the dashboard.

Fig. 1

Study design of the DermaView PDB project, spanning context analysis, design and implementation, and iterative evaluation. The figure is divided into two columns (Methods; Outputs/Artefacts) across three color-coded phases: Prior Context Analysis (grey22,23), Design & Implementation (orange), and Evaluation (green). In this context, Chevron shapes represent methods, and rounded rectangles represent outputs and artefacts. Solid arrows indicate the linkages between methods, artefacts and derived outputs. Dashed arrows denote feedback cycles across phases. Finally, dotted arrows mark inter-study relationships spanning the cross-study comparison.

For the purpose of analysis, the voice recordings were anonymized and transcribed. For comparability, they were then deductively annotated with the same catalogs of information about focus information and work steps that had been inductively created during the context analysis. During this process, new categories were inductively added to allow for the analysis of new features and marking of orientation times. The screen recordings were screened for switches between programs and added to the transcripts as annotations of programs in use, again using and extending the context analysis catalog deductively. These annotations were used to conduct a qualitative content analysis of the program usage, the information in focus, the work steps taken, and their relationships. A comparison was done between these results and the findings from the context analysis about how the PDB DermaView was used, looking specifically at the software, modules, and the interactions needed to get important case information. For deeper insights, the qualitative data were modeled via an affinity diagram (AD) to identify the topics most relevant to the users during the TA.

Prior context analysis

The present evaluation is founded on the contributions of two prior publications22,23, which collectively form the basis of the context analysis phase. As the dashboard design is developed based on these findings, a summary of the results is provided. This summary encompasses the study design, methods, key findings, and the influence of these findings on the dashboard.

Participants and task

A group of ten dermatologists from the skin cancer unit of the University Hospital Essen participated in a concurrent think-aloud (CTA) study in March 2022. The participants in the study ranged from residents with a few weeks of experience to senior consultants with over a decade of experience. Each participant was assigned the task of gathering information and preparing the registration of a patient with advanced metastatic melanoma for a fictitious interdisciplinary tumor board discussion within a 15-minute time limit. The study was conducted using real patient data on a standard clinical workstation.

Methods

Subsequent to this, the voice and screen recordings were transcribed and inductively annotated using the three defined categories: “work step,” “information in focus,” and “program used.” To further expand upon these findings and the various work settings, a series of contextual inquiries and interviews were conducted. The user statements were then organized into an affinity diagram to derive and prioritize 135 requirements for a melanoma-specific dashboard23. In addition, a sequence diagram was employed to illustrate the mental model of the physicians. A qualitative context analysis was executed to reveal the workflow and pain points22.

Key findings

Of the 135 derived requirements, the four most frequently referenced functional requirements were as follows: a comprehensive, easily accessible view of all patient data (FR00); search and filter functionality for lists, presenting the patient’s status in chronological order (FR12); direct access to original external and internal reports (FR02); and a comprehensive overview of melanoma-specific aspects such as staging, TNM classification, and metastasis status (FR09). The most frequently referenced non-functional requirement (NFR00) is the requirement for supporting information processing through an overview that remains easily interpretable even under time pressure22.

The workflow is structured into four phases and ten work steps, with an average completion time of 13 min. It was observed that physicians made an average of 25 transitions between three programs. This process required a minimum of 17–23 interactions to access a single piece of information from the HIS once the patient record was open. A substantial portion of the workflow, approximately 55%, was allocated to system interactions and manual data compilation rather than to clinical decision-making. A total of seven fundamental pain points were identified: time-intensive login and patient selection, need for multiple system instances, data fragmentation across systems, hierarchical information modularization, interface structures hindering simultaneous viewing, repetitive data insertion (27% of workflow time), and inappropriate input fields forcing external text editor use (28% of workflow time). The overall workflow was characterized as a comprehensive workaround compensating for data distribution22.

Think aloud

The TA24 is a widespread methodology for examining how well software integrates with the context and workflows for which it was designed25,26,27. The method is typically applied iteratively26 so that the software can be adapted between cycles to address identified problems and new insights. The method’s scope can be applied to both prototypes and implementations25, and it provides important insights with six to ten participants28 in each scenario29. During the process, participants are instructed to perform one or more tasks for which the software has been designed. During their interaction with the software, they are instructed to articulate any thoughts that arise. A variety of data can be collected for the purpose of evaluation, including but not limited to screen capture, voice recordings, interaction logs, and eye movement tracings. These analyses offer a more profound understanding of the user’s processes and interpretation of context, in contrast with a software developer’s interpretation of workflow and context descriptions29.

The TA was executed in three iterations, encompassing a total of eleven sessions. Nine physicians from the Department of Dermatology participated, representing the full range of clinical seniority. This included residents with a few weeks of experience in the department, senior consultants with over a decade of experience, and consultants with varying levels of previous patient knowledge. Two participants were involved in two of the three evaluation iterations and the same two participants had previously participated in the context analysis.

In the first and second iterations, there were four rounds, and in the third iteration, there were three rounds. The participants were tasked with preparing the information for a real patient for a fictitious tumor board in a clinical setting with a time limit of 15 min. In each cycle, a different patient was selected with the objective of ensuring a consistent level of case complexity. This scenario involved tumor board registration being mandatory and the absence of a tumor board conclusion that could potentially modify the physicians’ case analysis. The participants were asked to announce their thoughts aloud during this time, which was recorded along with a screen recording of the software interaction. During the first iteration, there was no screen recording due to technical problems. The voice recordings were then edited for anonymity and transcribed. A search for program switches was performed on the screen recordings and documented with time stamps. The transcripts were then aligned on the basis of the timestamps with the program switches using MAXQDA. We then applied qualitative content analysis to the data and conducted a cross-study comparison with the results of the context analysis.

Qualitative content analysis

Qualitative content analysis is a methodological framework that allows for both qualitative and quantitative interpretations of the results of qualitative methods based on categories30. This provides a broad contextual perspective by interpreting the overlap and frequency of these annotations31, making it one of the most frequently used methods32. The quantitative overview is combined with deeper insights from individual statements and reveals intents and relationships. The catalog can be created inductively from the transcripts to gain new insights on the basis of context. Alternatively, an existing catalog can be used deductively to search for already known aspects. To extend the scope of future research, a combination of both methods is feasible32.

The transcribed and aligned data from the TA’s voice and screen recordings were primarily annotated deductively by a single researcher (EH). The catalogs used were inductively created during context exploration, wherein a previous TA, the physicians were asked to perform the same task using the common HIS instead of the PDB DermaView. Therefore, we can evaluate the level of context adaptation of the PDB DermaView and compare the results of all TAs regarding the information in focus, programs in use, and work steps. Furthermore, the number of steps required to reach a specific datapoint was determined by modeling the system’s retrieval hierarchy for each “information in focus.” Consequently, a metric is generated that can be considered program- rather than case-dependent, thereby enabling a task-independent comparison across the HIS and the PDB DermaView.

Due to the orientation time needed by the participants to familiarize themselves with the PDB DermaView, new opportunities were revealed and needed to be included in the catalog. Those addressed the phase of familiarization and feedback given outside of the task the catalog of work steps needed to be extended. Additionally, we needed to expand the program catalog to encompass the new PDB pages and modules. There was no need to update the focused catalog of information.

Affinity diagram

The affinity diagram (AD)33 is an analysis tool derived from the Contextual Design methodology to illuminate important topics within an explored context. The development of an AD focuses on a content-based sorting of user phrases and insights gathered through qualitative methods. The process consists of critical reflection, deeper insight discovery, reorganization, and group rephrasing when the maximum size per group is reached. These groups are subsequently clustered into subtopics, which are then aggregated into broader topics. The resulting groups, subtopics, and topics are termed affinities, thus explaining the diagram’s name. In the process of modeling, all hierarchical elements—groups, subtopics, and topics—are labeled using I-perspective descriptions. First-person statements are written from the user’s point of view (e.g., “I need to find the current staging quickly” rather than “Staging data access”). This technique, defined within the Contextual Design methodology33,34, fosters empathy by keeping the analytical focus on user intent and experience rather than on system features. This structured approach to message organization facilitates the identification and clarification of interest areas divided into manageable groups34,35.

An AD was created for each iteration of the TA, with each AD highlighting the topics of that particular cycle. In the initial phase of the data analysis, user phrases were grouped according to shared aspects and subdivided into smaller groups when more than six user phrases indicated the same aspect. Therefore, they were interpreted in more detail, looking for deeper aspects and intentions. After a sufficient number of phrases were aggregated to identify common subtopics, the groups were titled from the I’s-perspective. This approach involved naming the common statements of the user phrases and aligning them with other groups of the same subtopic. We either incorporated user statements stepwise into existing groups or added new groups and organized them into subtopics. As the process progressed, the common themes of the subtopics became clearer, so the subtopics were also phrased from the I’s-perspective and clustered into topics. The procedure continued until all the user phrases were grouped and sorted into common subtopics and topics. The hierarchical structuring of an AD, from individual user phrases to groups, subtopics, and topics, is illustrated in Fig. 5, panel a, by reference to the ‘time to familiarize needed’ topic structure of Iteration III.

The ADs fulfilled two distinct roles within the evaluation. The initial step was to identify the most pressing problem areas that derived from the current design of each cycle. These problem areas were then prioritized in the subsequent implementation phase. The second step involved a redefinition of the grouping and categorization of the modules. This redefinition was informed by novel insights into the “data in focus” that emerged as physicians interacted with the newly aligned data points in the PDB DermaView.

Post-study system usability questionnaire

The Post-Study System Usability Questionnaire (PSSUQ)36 is a standardized usability questionnaire that focuses on user satisfaction with the program under evaluation. The questionnaire’s frequent utilization is due to its high validity and reliability36,37 as well as its effectiveness for participant sizes smaller than 1538. As was confirmed in scenario-based usability studies, the questionnaire is suitable for post-scenario ratings collected directly after task completion39. The instrument under consideration comprises 19 questions, which address four distinct aspects of “interface quality”, “information quality”, “system usefulness”, and “overall”. This multifaceted approach enables the extraction of more nuanced insights than those achievable with questionnaires that offer a single score. The questions are measured via a seven-point Likert scale ranging from 1 (strongly agree) to 7 (strongly disagree). These responses are then aggregated to generate scores across the four dimensions, from which the mean is calculated. Therefore, the scores can be interpreted as having a very positive tendency if they are approximately 1 and a very negative tendency if they are approximately 736.

In the present study, the PSSUQ was conducted using the German translation directly after the TA’s completion with nine different participants in eleven sessions. This early conduction supports the identification of usability issues before users become habituated to the system and develop workarounds that mask genuine interface deficiencies40. Consequently, the majority of the users had no prior experience with the PDB DermaView at the time of completing the questionnaire. The collected data were exported from the online survey tool LimeSurvey to Microsoft Excel, where the scores were calculated.

Results

In this section, the development and implementation of a dashboard design, which was developed on the basis of findings from the context exploration phase, are described. To ensure that the design still met the requirements and mental model of the users, the implemented version was evaluated. This evaluation revealed the number of interactions required to access a single piece of information, and the switches between programs indicated the easier accessibility of treatment-relevant information. The results of the PSSUQ underscore the constructive adaptation of the dashboard by the physicians and they also highlight the positive effect of the iterative approach by demonstrating improved results with each cycle. The affinity diagrams helped identify the remaining problems with improving the dashboard, which were the lack of modules and the need for better data display.

Dashboard design

The application’s design is grounded in the requirements and mental models that were revealed during the context exploration phase. The 135 requirements were incorporated into the dashboard, resulting in the module structure depicted in Table 1. The top functional requirement (FR00) was identified as a comprehensive, user-friendly view of all patient data. The physicians’ mental model, as illustrated by the workflow sequence diagram, and the affinity diagrams drove the shift from an object/treatment-phenomenon-oriented to a context-oriented data grouping and terming in DermaView.

The workflow analysis revealed a high number of interactions necessary to access treatment-relevant information, thus emphasizing the condensation of all relevant information on a single page as the primary focus of the design. These findings necessitated the development of a dashboard for clinical care, with a focus on prioritized data and the option of accessing further information for detailed inspection only when necessary. This design choice is supported by prior usability research demonstrating that high information density does not inherently cause problems when data is relevant and well-organized, and that grouping display items logically on a single screen can outperform a tabbed, distributed layout41. Notably, no additional interactions are required to access the information once logged in. The login process necessitates a total of five interactions. As demonstrated in Fig. 2, the dashboard draft under review emphasized that the application modules are designed to be reusable across diverse clinical workflows and specialties.

Table 1 New modules of the view optimized for melanoma patients’ treatment and the contained information.

Full size table

Fig. 2

The dashboard design draft, including the nomenclature assigned to the various modules and their configuration for the treatment of melanoma. The utilization of distinct color frames serves to underscore the benefits of the design, namely the consolidation of all necessary information within a single page (dark blue), the facilitation of navigation between disparate perspectives (green), and the reusability of modules (light blue).

At the initiation of the project, a dashboard customized for radiology implementation at the UME was already in place, encompassing modules for patient master data, treatment history, laboratory values, diagnosis, procedures, imaging, documents, and medication. This established dashboard was adopted to develop a view designed for melanoma patients. The mental model was taken into consideration, and the data presentation was shifted from an object/treatment phenomenon-oriented approach to a context-oriented approach. Specifically, data were grouped not only by common resource type but also by their relationship with diagnostics and treatment (see Table 1 for a summary of the information points contained in the added modules of ‘cancer factors’, ‘personal factors’, tumor boards, infusions and ‘cancer treatment’). Additionally, the modules for master data, laboratory values and treatment history were adjusted to the context insights by optimizing the data display and allowing for a focused view of prioritized laboratory values, such as tumor markers, during melanoma treatment.

A selection of modules provides supplementary detailed views, including the option to examine laboratory values as a time-resolved graph in addition to the tabular overview. Furthermore, full clinical documents can be accessed within a dedicated viewer, and the comprehensive list of mutation results is available for review. It should be noted that the overview module displays positive mutation findings exclusively. Within the modules, users have the ability to navigate between tabs in order to access additional information. Color coding is employed in the laboratory to accentuate out-of-range results against the displayed reference range, a practice that is observed in both tabular and graphical representations. The recently implemented modules do not utilize color coding. The initiation of these detailed views or the transition between tabs from a patient record that has already been loaded necessitates an additional interaction.

Dashboard interactions and work steps

The task required the utilization of the PDB DermaView as the primary source of information for completion. Although users were permitted to switch to an alternative source when the PDB could not fulfill the requirements, all users successfully completed the task without additional information sources. The task involved the use of various modules of the PDB DermaView and an external text editor to prepare a case description, which is necessary for the tumor board registration that still needs to be entered using the HIS. Upon completion, most users provided direct feedback on the dashboard. This feedback-related activity was excluded from the analysis of workflow and program usage. The programs utilized are listed in Table 2 and supported by the analysis of the work steps conducted, which are highlighted in Table 3. For a more thorough examination of the annotations please refer to the supplement 1 (supplement.xlsx – tab “annotations”).

Table 2 Detailed statistics on the utilization of different programs and modules of the PDB DermaView, including percentage usage by participants, as well as the proportion of use in relation to the average total time. These statistics are broken down into two categories: those taking into account and those disregarding the use of the program.

Full size table

Most time was allocated to the preparation of the case summary, with 67% of the participants utilizing an external text editor and 27% employing the tumor board registration mask directly. This activity constituted approximately 21% of the overall workflow, encompassing the steps of “formulating a question”, “editing the case summary”, and “completing the tumor board registration”. Accessing and reading the original patient diagnostic reports was an important part of each participant’s workflow, accounting for approximately 19% of the average workflow time. To access these records via PDB DermaView, the participant had to log in by performing three interactions, opening the patient file with another three interactions, and accessing the records from a list with two interactions. Thus, once the patient record is open, zero further interactions are required to access prioritized data, such as tumor specific data, e.g. tumor thickness and the presence of ulceration of the primary tumor, and up to two interactions allow access to detailed information such as full reports, full laboratory history, or complete molecular pathology results. The four modules of the PDB used by the majority of participants were progress documentation (100%), imaging (67%), tumor conference (67%), and medications (67%). The top three modules that users focused on the longest were progress documentation (2:34 min), imaging (00:39 min), and laboratory (00:29 min). On average, each participant used 7.8 different PDB DermaView modules, with a minimum of four and a maximum of nine. This resulted in a total of 27 switches between modules and programs with a minimum variance of 12 and a maximum variance of 38, of which approximately eleven were to external programs such as the HIS or the text editor.

Table 3 Work steps conducted during the participation, alongside the average time spent on each step, the proportion of this time in relation to the total task completion time (excluding the time taken for feedback), and the percentage of the work step occurrence in the different work flows of each participant. Work steps that were added during the annotation to name new interaction options start with“new >”.

Full size table

PSSUQ

Fig. 3

The mean score of the PSSUQ results in conjunction with the results of each iteration for the four groups (“system usefulness”, “information quality”, “interface quality”, and “overall”).

Fig. 4

Distribution of responses for all 19 PSSUQ questions across all sessions. Response values range from 1 (strongly agree/very positive) to 7 (strongly disagree/very negative), with 0 representing “I don’t know” and 8 representing missing answers.

The results of the PSSUQ demonstrate an iterative enhancement of the PDB DermaView across all four groups, as illustrated in Fig. 3. The overall PSSUQ scores below 2.0 indicate strong positive user satisfaction36. The final overall score of 1.8 achieved in Iteration III therefore exceeds this threshold, reflecting a high level of perceived usability. Interface quality showed the most pronounced improvement, with the score decreasing from 2.6 to 1.3 — a 0.5-point improvement also observed in system usefulness and information quality between Iterations I and III. The questions, group building and results of each cycle can be found in the supplement 1 (supplement.xlsx – tab “pssuq”).

Figure 4 shows the mean score for each question, with the highest number of negative responses (2–7) occurring for questions 9–11, which pertain to error messages, handling, and solutions. Notably, these questions also received the least amount of feedback from participants. Conversely, the highest positive ratings (1 and 2) were attributed to Q1, Q2, and Q12, signifying the overall ease of task completion, the simplicity of use, and the accessibility of the necessary information. Notably, the highest positive ratings (1) were observed for Q3, which addresses the effectiveness of task completion using the PDB DermaView, and for Q12, which addresses user confidence in achieving productivity with the system.

Affinity diagrams

Fig. 5

Affinity Diagram construction and representative output. (a) Schematic of the hierarchical construction of an Affinity Diagram, shown exemplarily for the “time to familiarize needed” topic structure (Iteration III). Colors denote the four hierarchy levels (topic, subtopic, group, user phrase); solid connecting lines indicate the aggregation of child elements into their parent category, while dashed lines and boxes shaded in the corresponding hierarchy level’s color denote additional elements not shown for readability. For the topic and subtopic level, both the literal (translated) I-perspective statement used during analysis and the short label used in this publication for conciseness are given. User phrases are verbatim, literally translated participant quotes, labeled with anonymized participant identifiers (e.g., P10); these identifiers carry no demographic information. (b) Treemap of the complete Affinity Diagram for Iteration III, showing all identified topics (overlaying purple rectangle) and subtopics (shaded in orange; shading consistent for one topic); the number of user phrases assigned to each subtopic is given in the cell label following the semicolon, and cell area is proportional to this number.

The development of three ADs resulted in the identification of three topics, including 401 user phrases in Iteration I, 289 user phrases grouped into four topics in Iteration II, and 348 user phrases represented in three topics in Iteration III. The following text will consider only the topics and subtopics of each AD, using Iteration III as an illustrative example (Fig. 5, panel b). The complete hierarchical structure — groups, subtopics, and topics — for all three iterations, both as hierarchical tables and as treemap visualizations equivalent to Fig. 5, panel b, is provided in the supplement 1 (supplement.xlsx – tab ‘affinity diagrams’).

In all iterations, the preparation of the tumor board and information gathering, evaluation and decision-making were the strongest topics, with 176 user phrases in five subtopics in Iteration I. Since the second iteration, a stronger distinction between the topics and subtopics has been made. Iteration II revealed a stronger distinction between information gathering and information processing, resulting in three subtopics with 82 user phrases and two subtopics with another 60 user phrases, and Iteration III presented 131 and 114 user phrases in the four subtopics, respectively. The subtopics address the availability of any necessary information and the support of the workflow by fitting the visualization of the data.

In the first iteration, some ideas for improvement were extracted from 105 user phrases in four subtopics. Furthermore, the time necessary to become familiar with the PDB came to the center of the second and third iterations. The second Iteration Identified 90 user phrases in four subtopics, and the third iteration associated 103 user phrases with three subtopics. Although there was a necessity for a period of adjustment by users to the novel functionalities, the proportion of user phrases expressing frustration or error-related feedback underwent a considerable decline across iterations: from “errors” (120 phrases in four subtopics) in Iteration I, to “error occur while using the PDB” (57 phrases in three subtopics) in Iteration II, down to a single remaining subtopic, “problems getting started” (35 phrases), within the broader “time to familiarize needed” topic in Iteration III. These topics, in rare instances, address errors in the PDB and the potential for enhancing visualization techniques. However, they address primarily the lack of documented data, which could further improve the workflow and quality of documented free text.

The aforementioned PSSUQ scores provide further evidence that validates this shift. Furthermore, the number of user phrases referring to topics outside the assigned task, as well as the number of reported switches to external programs, both decreased between Iteration I and Iteration III. This suggests that physicians were increasingly able to focus on patient treatment rather than on software interactions. This finding aligns with the observation that no participant expressed concerns regarding information density or text legibility (e.g., font size) during the Think-Aloud sessions or in the PSSUQ responses. This is notable given the dashboard’s single-page design, which consolidates a substantially larger volume of information than the previously used HIS.

Cross-study comparison

The interaction efficiency was evaluated against the baseline health information system (HIS) that had previously been assessed during context exploration22,23. In that case, physicians used the existing HIS instead of PDB DermaView to prepare the tumor board. The interaction baseline, defined as the minimum number of clicks required to access a single piece of patient information from a closed record in the existing HIS, serves as the comparator for the present evaluation. The annotation catalogs created during the context analysis were reused deductively, enabling direct comparison of results across both studies. In this cross-study comparison of the interactions required to reach the same type of data point in each system, the number of interactions necessary to access a single piece of patient information was reduced from 17 to 23 to 5–6, including the steps of login and patient file access. Furthermore, when the record was already open, the number of interactions was reduced from 2 to 7 to 0–1, as the relevant information could be surfaced by identifying the corresponding module directly from the dashboard. Beyond the issue of interaction counts, physicians using the HIS also described experiencing a loss of orientation due to the technical instability of the interface (e.g., “It had somehow just closed all the windows.“) (context analysis; P10); no comparable incidents were reported during the present evaluation of PDB DermaView. In contrast, participants who used PDB DermaView described finding the necessary information with relative ease (e.g., “I was able to find the necessary information for this patient well.“) (P01).

Despite the reduction in required interactions, the mean task completion time increased slightly, from 13 min to 16 s (baseline HIS) to 16 min and 10 s (PDB DermaView). Of this increase, 2 min and 3 s were attributable to orientation time with the unfamiliar dashboard; excluding this component, completion time was 14 min and 8 s. Once oriented, physicians were able to swiftly identify the pertinent information, as evidenced by participant feedback (e.g., “[…] the more frequently you use it, the faster you find things again.” (P11).

The number of program switches increased from 25.3, with a variance of 14 minimum and 34 maximum, to 27, with a variance of 12 minimum and 36 maximum. It is important to note that this number includes switching between PDB DermaView modules that do not require user interaction or a changing view. In contrast, when the HIS is used, the majority of these transitions involve the introduction of new overlays and changes in views. As a result, the number of transitions to external programs was only eleven.

Discussion

The objective of the project was to evaluate a dashboard developed to assist physicians in the treatment of melanoma patients. The dashboard in question was implemented in accordance with a prior study, which conducted a thorough context exploration, thereby identifying the most relevant elements to incorporate into the dashboard design. A comparison of the results of the evaluation with those of the preliminary study reveals an enhancement in usability. In context exploration, physicians were tasked with preparing the tumor board using the existing health information system (HIS) instead of the PDB DermaView. Specifically, in this cross-study comparison of the interactions required to reach the same type of data point in each system, the number of interactions necessary to access a single piece of patient information was reduced. A slight increase in the number of switches between programs and modules was observed. On average, eleven of these switches included external programs, while sixteen were linked to changing the focus to a different module on the PDB, predominantly without further interaction. A pronounced decline is evident in the interaction-based switches. It is important to note that the transition in focus requires additional effort during the initial phase of familiarization. However, this investment in effort can lead to a substantial reduction in mental load once users become accustomed to the specific module combination.

The observed increase in completion time despite fewer required interactions (see Results) is attributable primarily to users’ unfamiliarity with the dashboard rather than to inefficiencies in its design; we would expect this gap to narrow with increasing experience, since users were deliberately evaluated before habituating to PDB DermaView, in order to surface genuine usability issues rather than issues masked by learned workarounds.

The qualitative results emphasize a gradually stronger focus of the physicians on the patients’ information rather than software interactions by each iteration, which highlights a higher quality in the time usage regarding the task fulfillment. The evaluation of PDB DermaView underscores the advantages of implementing a dashboard on the basis of a thorough contextual analysis and user involvement during all development phases. While users required a period of familiarization with the program, all participants were able to satisfactorily complete the tumor board preparation task and deepen their insight into the patient’s case at an early stage of orientation. This positive experience led to favorable feedback regarding the system, with users expressing a preference for the PDB DermaView over the HIS.

Helminski et al.3 evaluated the methods used for the development, implementation, and evaluation of medical dashboards published between 2018 and 2020. Their findings revealed variations in the settings, user groups, data focus, and data actuality of the dashboards. The findings of this review indicated that eight of the 43 medical dashboards were evaluated via a combination of methods, whereas 23 of the 43 incorporated user involvement in the design process. Although numerous evaluations of clinical systems and dashboards have been conducted, when all attributes have been identified, no study has described the evaluation of a dashboard for inpatients and clinical ambulance patients, with physicians as a targeted user group, which was developed and evaluated in a user-centered manner3.

Nonetheless, certain studies address the same key aspects. For example, one study developed a dashboard for inpatient treatment, with a focus on supporting physicians in ICU ventilation42. In contrast to our approach, the evaluation of implementation success is based on metrics such as reductions in weaning time and hospitalization, as evidenced by a proof-of-concept study. However, this study does not address the usability and context integration of the software.

Another study focused on workflow support in ICUs by developing a statistical dashboard for identifying inpatients with ventilation-associated pneumonia43. The development of this system is based on the extraction and computation of data collected in the EHR by interdisciplinary teams. The evaluation process is conducted without the involvement of users and utilizes subjective measures rather than standardized instruments or questionnaires.

In contrast, a user-centered approach is used to evaluate the cognitive load and workload of physicians via their inpatient safety dashboard, which was developed in an iterative and user-centered design process44. To validate the dashboard, they also conducted a TA study that recorded voice, screen, and mouse interactions. This approach enabled the observation of a decline in mouse interactions while maintaining constant levels of cognitive and workload, as measured by the NASA-Raw Task Load Index (RTLX).

Utilizing the insights derived from the results and aligning with the findings of prior studies, this evaluation contributes two important aspects to the domain of medical dashboard development. Firstly, the paper demonstrates the feasibility of a holistic, iterative, user-centered evaluation approach in a time-critical clinical setting. Secondly, by integrating DermaView with the FHIR-based data from SHIP, this study provides a practical demonstration of how an existing data integration framework can be adapted into a point-of-care application that directly benefits physicians, rather than being limited to research applications. This distinction is particularly relevant in the German healthcare context, where data integration efforts have been predominantly focused on enabling research rather than directly supporting clinical workflows.

The evaluation process involved a total of nine physicians, who participated in eleven sessions. However, due to the nature of the study, inferential statistical analysis was not feasible. The selected methods are appropriate for small, in-depth samples, with TA providing key insights with six to ten participants per scenario28,29 and the PSSUQ validated for samples below 15 participants38. Accordingly, qualitative content analysis and ADs were used as the primary analytical methods, while PSSUQ scores were interpreted descriptively as an indication of perceived usability, consistent with user-centered design research using small expert cohorts.

The present study is limited by the fact that its qualitative content analysis was conducted by a single annotator. This concern is primarily associated with the interpretive categories of the annotation catalog, such as identified work steps. The categories derived directly from objective data, such as the temporal sequence of program usage from screen recording timestamps or system’s retrieval hierarchy, are less likely to be influenced by coder subjectivity. The majority of categories employed in the deductive annotation process have their origins in the catalog, which was inductively derived in a prior study annotated by four annotators. However, the inter-rater reliability of the qualitative findings was not formally assessed, which limits their reproducibility.

A further limitation concerns the cross-study nature of the comparison. The interaction counts reflect each system’s retrieval hierarchy for a given data point rather than case-specific content. As melanoma treatment follows standardized protocols requiring consideration of the same core data points across patients, the comparison should be largely robust to case-level variation. The primary source of cross-study variability originates from the sequence and number of work steps performed, task completion time and program switches by individual physicians. These factors may vary between cohorts and be dependent on case complexity.

As the project is narrowly focused on melanoma, it will be necessary to evaluate how the contextual findings of this work can be transferred to other areas and other hospitals. The dashboard’s modular design supports the direct transfer of developed modules to various tasks within the same field.

However, slight adjustments may be necessary for other skin cancers. To adapt to other cancers and other fields, more in-depth contextual research is needed. A further limitation of this narrow focus, which also has implications for transferability and future research, is the early evaluation of PDB DermaView in terms of the lack of user familiarity with the dashboard. Consequently, the results also consider the time needed for orientation and evaluation of the new possibilities. This is especially true for the adaptation of the workflow to the easier data collection and options offered by the dashboard. Consequently, minor adjustments may be required to seamlessly integrate the PDB DermaView into the adapted workflow and further enhance patient treatment.

The underlying design-and-evaluation approach, which incorporates an iterative combination of TA sessions, PSSUQ, and ADs, is not only effective for melanoma care but also methodologically transferable to other clinical domains. This finding aligns with the general applicability of the TA29 and with our previous finding that generalizable aspects of dashboard development can inform other medical domains23. Nevertheless, it is not clear if repeating this full evaluation cycle for every additional department represents the most efficient path forward. The results of this study identified a number of factors that appear context-independent rather than specific to melanoma. These include the benefit of a single consolidated view and the importance of grouping information according to clinicians’ own mental models rather than departmental data structures. Further studies in other clinical domains could help substantiate these findings. Given the considerable time investment that TA-based evaluation places on clinicians, we therefore argue that, in the event of extending PDB DermaView to additional clinical departments, the priority should be placed on CI to establish which data are relevant to a given workflow and how clinicians mentally group them. PDB DermaView is currently in routine clinical use and is being extended stepwise to further clinical departments accordingly. A re-evaluation after a longer period of routine use would be a valuable direction for future work, particularly to assess whether workarounds have re-emerged as users become more habituated to the system and to extend the evaluation across multiple sites. This evaluation demonstrates that investing in user-centered, context-driven design is a profitable strategy. It is anticipated that this principle will hold regardless of the clinical domain to which PDB DermaView is extended.

Data availability

The authors confirm that the data supporting the findings of this study is available within the article and its supplementary materials or, upon reasonable request, to the corresponding author.

References

  1. Gierend, K. et al. The status of data management practices across German medical data integration centers: Mixed methods study. J. Med. Internet Res. 25, e48809 (2023).

    Article  PubMed  PubMed Central  Google Scholar 

  2. Prokosch, H.-U. et al. MIRACUM: Medical informatics in research and care in university medicine. Methods Inf. Med. 57, e82–e91 (2018).

    Article  PubMed  PubMed Central  Google Scholar 

  3. Helminski, D. et al. Development, implementation, and evaluation methods for dashboards in health care: Scoping review. JMIR Med. Inform. 12, e59828 (2024).

    Article  PubMed  PubMed Central  Google Scholar 

  4. van Gemert-Pijnen, J. E. W. C. et al. A holistic framework to improve the uptake and impact of eHealth technologies. J. Med. Internet. Res. 13, e111 (2011).

    Article  PubMed  PubMed Central  Google Scholar 

  5. Osheroff, J. Improving outcomes with clinical decision support. An implementer’s guide (HIMSS Publishing an imprint of Taylor and Francis, 2012).

    Google Scholar 

  6. Evans, R. S. Electronic health records: Then, now, and in the future. Yearb. Med. Inform. Suppl 1, S48-61 (2016).

    PubMed  PubMed Central  Google Scholar 

  7. Middleton, B. et al. Enhancing patient safety and quality of care by improving the usability of electronic health record systems: recommendations from AMIA. J. Am. Med. Inf. Assoc. 20, e2–8 (2013).

    Article  Google Scholar 

  8. Kilsdonk, E., Peute, L. W., Jaspers, M. W., Peute, L. W. & Jaspers, M. W. M. Factors influencing implementation success of guideline-based clinical decision support systems: a systematic review and gaps analysis. Int. J. Med. Inform. 98, 56–64 (2017).

    Article  PubMed  Google Scholar 

  9. Norouzi, S., Galavi, Z. & Ahmadian, L. Identifying the data elements and functionalities of clinical decision support systems to administer medication for neonates and pediatrics: A systematic literature review. BMC Med. Inform. Decis. Mak. 23, 263 (2023).

    Article  PubMed  PubMed Central  Google Scholar 

  10. Kushniruk, A. W. & Patel, V. L. Cognitive evaluation of decision making processes and assessment of information technology in medicine. Int. J. Med. Informatics. 51, 83–90 (1998).

    Article  Google Scholar 

  11. Johnson, C. M. et al. EHR usability toolkit. EHR Usability Toolkit: A Background Report on Usability and Electronic Health Records. A background report on usability and electronic health records (Prepared by Westat under Contract No. 290-09-00023I-7). (2011). https://digital.ahrq.gov/ahrq-funded-projects/electronic-health-record-usability-toolkit/citation/ehr-toolkit-background

  12. Norman, D. A. Mental Models (Gentner, D. & Stevens, A. L.) 7–14 (Psychology Press Taylor & Francis Group, 1983).

  13. Eysenbach, G. The law of attrition. J. Med. Internet Res. 7, e11 (2005).

    Article  PubMed  PubMed Central  Google Scholar 

  14. Horsky, J. et al. Interface design principles for usable decision support: a targeted review of best practices for clinical prescribing interventions. J. Biomed. Inform. 45, 1202–1216 (2012).

    Article  PubMed  Google Scholar 

  15. Saitwal, H., Feng, X., Walji, M., Patel, V. & Zhang, J. Assessing performance of an Electronic Health Record (EHR) using cognitive task analysis. Int. J. Med. Inform. 79, 501–506 (2010).

    Article  PubMed  Google Scholar 

  16. Shanafelt, T. D., Dyrbye, L. N. & West, C. P. Addressing physician burnout: The way forward. JAMA 317, 901–902 (2017).

    Article  PubMed  Google Scholar 

  17. Melnick, E. R. et al. The association between perceived electronic health record usability and professional burnout among US physicians. Mayo Clin. Proc. 95, 476–487 (2020).

    Article  PubMed  Google Scholar 

  18. Akbar, F. et al. Physician stress during electronic health record inbox work: In situ measurement with wearable sensors. JMIR Med. Inform. 9, e24014 (2021).

    Article  PubMed  PubMed Central  Google Scholar 

  19. Blijleven, V., Hoxha, F. & Jaspers, M. Workarounds in electronic health record systems and the revised sociotechnical electronic health record workaround analysis framework: Scoping review. J. Med. Internet Res. 24, e33046 (2022).

    Article  PubMed  PubMed Central  Google Scholar 

  20. van Offenbeek, M. A. G., Vos, J. F. J., van den Hooff, B. & Boonstra, A. When workarounds aggravate misfits in the use of electronic health record systems. Inform. Syst. J. 34, 293–326 (2024).

    Article  Google Scholar 

  21. Rundo, L., Pirrone, R., Vitabile, S., Sala, E. & Gambino, O. Recent advances of HCI in decision-making tasks for optimized clinical workflows and precision medicine. J. Biomed. Inform. 108, 103479 (2020).

    Article  PubMed  Google Scholar 

  22. Hartmann, E. M. et al. Revealing the physician’s task conceptualization in melanoma treatment: Qualitative user experience study. JMIR Cancer 12, e79294 (2026).

    Article  PubMed  PubMed Central  Google Scholar 

  23. Hartmann, E. M. et al. Requirements for a dashboard optimized for melanoma patient care through user-centered context exploration. Sci. Rep. https://doi.org/10.1038/s41598-024-67857-2 (2024).

    Article  PubMed  PubMed Central  Google Scholar 

  24. Lewis, C. Using the "thinking-aloud" method in cognitive interface design (1982).

  25. Kip, H. et al. Methods for human-centered eHealth development: Narrative scoping review. J. Med. Internet Res. 24, e31858 (2022).

    Article  PubMed  PubMed Central  Google Scholar 

  26. Maramba, I., Chatterjee, A. & Newman, C. Methods of usability testing in the development of eHealth applications: A scoping review. Int. J. Med. Inform. 126, 95–104 (2019).

    Article  PubMed  Google Scholar 

  27. Wronikowska, M. W. et al. Systematic review of applied usability metrics within usability evaluation methods for hospital electronic healthcare record systems: Metrics and evaluation methods for eHealth systems. J. Eval. Clin. Pract. 27, 1403–1416 (2021).

    Article  PubMed  PubMed Central  Google Scholar 

  28. Hwang, W. & Salvendy, G. Number of people required for usability evaluation. Commun. ACM. 53, 130–133 (2010).

    Article  Google Scholar 

  29. Jacobsen, J. & Meyer, L. Praxisbuch Usability und UX. Was alle wissen sollten, die Websites und Apps entwickeln. 3rd ed. (Rheinwerk Computing; Rheinwerk Verlag, 2022).

    Google Scholar 

  30. Mayring, P. & Fenzl, T. Handbuch Methoden der empirischen Sozialforschung (Baur, N. & Blasius, J. eds) Vol. 2, 633–648 (Springer, 2019).

  31. Elo, S. & Kyngäs, H. The qualitative content analysis process. J. Adv. Nurs. 62, 107–115 (2008).

    Article  PubMed  Google Scholar 

  32. Mayring, P. Mayring P. Qualitative inhaltsanalyse-abgrenzungen, spielarten, weiterentwicklungen. In Forum Qualitative Sozialforschung/Forum: Qualitative Social Research, Vol. 20, No. 3, p. 15. DEU. https://doi.org/10.17169/FQS-20.3.3343 (2019).

  33. Holtzblatt, K. & Beyer, H. Contextual Design. Defining Customer-Centered Systems. 1st ed. (Morgan Kaufmann, 1997).

    Google Scholar 

  34. Beyer, H. & Holtzblatt, K. Contextual design. interactions 6, 32–42 (1999).

    Article  Google Scholar 

  35. Simon, R. W. & Canacari, E. G. A practical guide to applying lean tools and management principles to health care improvement projects. AORN J. 95, 85–100 (2012). quiz 101-3.

    Article  PubMed  Google Scholar 

  36. Lewis, J. R. IBM computer usability satisfaction questionnaires: Psychometric evaluation and instructions for use. Int. J. Hum.–Comput. Interact. 7, 57–78 (1995).

    Article  Google Scholar 

  37. Sauro, J., Lewis, J. R. & Olsen, D. R. Proceedings of the SIGCHI Conference on Human Factors in Computing Systems (Olsen, D. R. eds) 1609–1618 (ACM, 2009).

  38. Tullis, T. S. & Stetson J. N. Usability professional association conference (2004).

  39. Lewis, J. R. Psychometric Evaluation of the Post-Study System Usability Questionnaire: The PSSUQ. In Proceedings of the Human Factors Society Annual Meeting. 36, 1259–1260 (1992).

  40. Corrao, N. J., Robinson, A. G., Swiernik, M. A. & Naeim, A. Importance of testing for usability when selecting and implementing an electronic health or medical record system. J. Oncol. Pract. 6, 120–124 (2010).

    Article  PubMed  PubMed Central  Google Scholar 

  41. Al Ghalayini, M., Antoun, J. & Moacdieh, N. M. Too much or too little? Investigating the usability of high and low data displays of the same electronic medical record. Health Informatics J. 26, 88–103 (2020).

    Article  PubMed  Google Scholar 

  42. Anderson, B. J. et al. Clinical impact of an electronic dashboard and alert system for sedation minimization and ventilator liberation: A before-after study. Crit. Care Explor. 1, e0057 (2019).

    PubMed  PubMed Central  Google Scholar 

  43. Hebert, C., Flaherty, J., Smyer, J., Ding, J. & Mangino, J. E. Development and validation of an automated ventilator-associated event electronic surveillance system: A report of a successful implementation. Am. J. Infect. Control 46, 316–321 (2018).

    Article  PubMed  Google Scholar 

  44. Fuller, T. E. et al. Assessing the cognitive and work load of an inpatient safety dashboard in the context of opioid management. Appl. Ergon. 85, 103047 (2020).

    Article  PubMed  Google Scholar 

Download references

Acknowledgements

We thank the physicians of the Department of Dermatology (University Hospital Essen) for their dedicated participation in the usability studies. We thank Katharina Zeiner (Siemens, Munich) for the mentoring and fruitful discussions on user experience. The data for the PDB DermaView were provided by the Smart Hospital Information Platform (SHIP), which is managed by the Data Integration Center at the University Medicine Essen. SHIP serves as a comprehensive digital health platform for integrating data from all major clinical subsystems via a holistic FHIR-based approach. It enables the purification, analysis, distribution, and visualization of clinical data. All figures in this manuscript were created by the first author Eva Hartmann using miro (https://miro.com/) for Figs. 1 and 5 (panel a), drawio online (https://draw.io/) for Figure 2 and Excel – Office 365 version 2405 (https://www.microsoft.com/en-us/microsoft-365/excel) - for Figs. 3, 4 and 5 (panel b).

Funding

This work was funded by Ph.D. grants from the DFG Research Training Group 2535 ‘Knowledge- and data-based personalization of medicine at the point of care (WisPerMed)’. We acknowledge support from the Open Access Publication Fund of the University of Duisburg-Essen.

Author information

Authors and Affiliations

  1. Data Integration Center, University Hospital Essen, Girardetstraße 2, 45147, Essen, Germany

    Eva Maria Hartmann & Tobias Brieden

  2. Institute for Artificial Intelligence in Medicine, University Hospital Essen, 45147, Essen, Germany

    Katarzyna Borys, Ahmad Idrissi-Yaghir & Felix Nensa

  3. Clinic for Dermatology, University Hospital Essen, 45147, Essen, Germany

    Georg Christian Lodde, Elisabeth Livingstone & Dirk Schadendorf

  4. Department of Computer Science, University of Applied Sciences and Arts Dortmund, 44227, Dortmund, Germany

    Eva Maria Hartmann & Sabine Sachweh

Authors

  1. Eva Maria Hartmann
  2. Katarzyna Borys
  3. Ahmad Idrissi-Yaghir
  4. Georg Christian Lodde
  5. Elisabeth Livingstone
  6. Dirk Schadendorf
  7. Felix Nensa
  8. Tobias Brieden
  9. Sabine Sachweh

Contributions

EH: Conceptualization, Methodology, Investigation, Data curation, Visualization, Formal analysis, Writing- Original draft preparation. KB & AI: Methodology, Data Curation, Writing - Review & Editing. GL, EL, FN, TB & DS: Conceptualization, Resources, Writing - Review & Editing. SS: Supervision, Conceptualization, Methodology, Writing - Review & Editing.

Corresponding author

Correspondence to Eva Maria Hartmann.

Ethics declarations

Competing interests

The authors declare no competing interests.

Additional information

Publisher’s note

Springer Nature remains neutral with regard to jurisdictional claims in published maps and institutional affiliations.

Rights and permissions

Open Access This article is licensed under a Creative Commons Attribution 4.0 International License, which permits use, sharing, adaptation, distribution and reproduction in any medium or format, as long as you give appropriate credit to the original author(s) and the source, provide a link to the Creative Commons licence, and indicate if changes were made. The images or other third party material in this article are included in the article’s Creative Commons licence, unless indicated otherwise in a credit line to the material. If material is not included in the article’s Creative Commons licence and your intended use is not permitted by statutory regulation or exceeds the permitted use, you will need to obtain permission directly from the copyright holder. To view a copy of this licence, visit http://creativecommons.org/licenses/by/4.0/.

Reprints and permissions

About this article

Check for updates. Verify currency and authenticity via CrossMark

Cite this article

Hartmann, E.M., Borys, K., Idrissi-Yaghir, A. et al. Iterative user-centered evaluation of a context-driven clinical dashboard for melanoma treatment. Sci Rep 16, 30848 (2026). https://doi.org/10.1038/s41598-026-74167-2

Download citation

  • Received: 30 April 2025

  • Accepted: 28 September 2026

  • Published: 05 October 2026

  • Version of record: 05 October 2026

  • DOI: https://doi.org/10.1038/s41598-026-74167-2

Keywords

来源:Nature 健康护理主题 · nature.com