Skip to content

An Ontology for Workplace Violence: Protocol to support Cross-sector Incident Reporting in Public Services.

Feb 2026 · JMIR Research Protocols · 0 citations · 20 references
Medicine

Abstract

Background

Underreporting is a defining problem in the registration of workplace violence across public services. This is reinforced by inconsistent, often poor incident descriptions and the absence of a clear, shared nomenclature. Without an ontology-backed structure, similar events are recorded differently across settings or remain uncodable and effectively invisible. Moreover, WPV is typically registered and studied within sector- and even organization-specific categories and local reporting logics rather than through a shared semantic framework, limiting comparability and cumulative understanding across sectors. To address this, we propose creating and publicizing a workplace violence ontology (WPV-ONTO) to unify the representation of WPV events across public services.

Objective

The objective of this protocol is to describe and justify a research methodology for developing a cross-sector ontology and reference nomenclature for WPV in public services (WPV-ONTO), including the scoping review, expert-consensus, and evaluation procedures used to build it. Promoting openness and high standards during its creation and encouraging its uptake once available are broader project goals that this protocol is designed to support, rather than measurable objectives that this protocol itself tests.

Methods

Using the Protégé ontology editor and the METHONTOLOGY ontology development life-cycle guidelines, we will create an ontology that captures the cross-sector WPV domain in Web Ontology Language (OWL). In order to find common WPV concepts, definitions, and synonyms, the modeling process will employ a methodologically defined, iterative workflow that combines (1) focused scoping searches (Web of Science/PubMed/APA PsycInfo/ERIC/Sociological Abstracts); (2) structured extraction from industry-standard incident reporting tools and code lists; and (3) expert consensus. Based on iterative rounds of scientific literature reviews and industry-standard code lists, a team of domain experts will use a hybrid top-down and bottom-up approach to define and identify key ideas and relationships. A small pilot with 6-8 frontline workers from two sectors will test the prototype reporting form against usability criteria before version 1.0 release.

Results

The primary output will be a comprehensive, versioned WPV-ONTO accommodating key WPV concepts relevant to public services, augmented with synonyms, definitions, and references. WPV-ONTO will include an explicit hierarchical structure and relations supporting inheritance and compositional incident encoding. WPV-ONTO seeks to integrate the needs and conceptualizations of frontline workers, safety and aftercare professionals, sector policymakers, WPV researchers, and health/information systems experts. Recruitment of the expert panel is planned to begin in March 2027, and WPV-ONTO version 1.0 is expected at the end of the 24-month development period.

Conclusions

WPV-ONTO is expected to enable reasoning, inference, and consistent representation of relationships among WPV concepts for application in multiple contexts, including cross-sector reporting harmonization, software and API development, research data integration, and evaluation of prevention and aftercare initiatives. By providing a shared vocabulary and explicit structure, WPV-ONTO may also facilitate linkage with other relevant information systems, such as electronic medical records, and justice and police information systems, reducing methodological fragmentation and supporting coordinated cross-sector learning while retaining the contextual specificity necessary for public service environments. CLINICALTRIAL Not applicable.

Read PDF

Similar papers

#computer vision Review Sep 2017

Agile Software Development Methods: Review and Analysis

Agile - denoting "the quality of being agile, readiness for motion, nimbleness, activity, dexterity in motion" - software development methods are attempting to offer an answer to the eager business community asking for lighter weight along with faster and nimbler software development processes. This is especially the case with the rapidly growing and volatile Internet software industry as well as for the emerging mobile application environment. The new agile methods have evoked substantial amount of literature and debates. However, academic research on the subject is still scarce, as most of existing publications are written by practitioners or consultants. The aim of this publication is to begin filling this gap by systematically reviewing the existing literature on agile software development methodologies. This publication has three purposes. First, it proposes a definition and a classification of agile software development approaches. Second, it analyses ten software development methods that can be characterized as being "agile" against the defined criterion. Third, it compares these methods and highlights their similarities and differences. Based on this analysis, future research needs are identified and discussed.

P. Abrahamsson, O. Salo, Jussi Ronkainen et al. · 728 citations · ⚡54
#machine learning Review Open access Oct 2014

Software development in startup companies: A systematic mapping study

Context: Software startups are newly created companies with no operating history and fast in producing cutting-edge technologies. These companies develop software under highly uncertain conditions, tackling fast-growing markets under severe lack of resources. Therefore, software startups present a unique combination of characteristics which pose several challenges to software development activities. Objective: This study aims to structure and analyze the literature on software development in startup companies, determining thereby the potential for technology transfer and identifying software development work practices reported by practitioners and researchers. Method: We conducted a systematic mapping study, developing a classification schema, ranking the selected primary studies according their rigor and relevance, and analyzing reported software development work practices in startups. Results: A total of 43 primary studies were identified and mapped, synthesizing the available evidence on software development in startups. Only 16 studies are entirely dedicated to software development in startups, of which 10 result in a weak contribution (advice and implications (6); lesson learned (3); tool (1)). Nineteen studies focus on managerial and organizational factors. Moreover, only 9 studies exhibit high scientific rigor and relevance. From the reviewed primary studies, 213 software engineering work practices were extracted, categorized and analyzed. Conclusion: This mapping study provides the first systematic exploration of the state-of-art on software startup research. The existing body of knowledge is limited to a few high quality studies. Furthermore, the results indicate that software engineering work practices are chosen opportunistically, adapted and configured to provide value under the constrains imposed by the startup context.

Nicolò Paternoster, Carmine Giardino, M. Unterkalmsteiner et al. · 394 citations · ⚡54
#computer vision Open access Jul 2017

What happens when software developers are (un)happy

The growing literature on affect among software developers mostly reports on the linkage between happiness, software quality, and developer productivity. Understanding happiness and unhappiness in all its components -- positive and negative emotions and moods -- is an attractive and important endeavor. Scholars in industrial and organizational psychology have suggested that understanding happiness and unhappiness could lead to cost-effective ways of enhancing working conditions, job performance, and to limiting the occurrence of psychological disorders. Our comprehension of the consequences of (un)happiness among developers is still too shallow, being mainly expressed in terms of development productivity and software quality. In this paper, we study what happens when developers are happy and unhappy while developing software. Qualitative data analysis of responses given by 317 questionnaire participants identified 42 consequences of unhappiness and 32 of happiness. We found consequences of happiness and unhappiness that are beneficial and detrimental for developers' mental well-being, the software development process, and the produced artifacts. Our classification scheme, available as open data enables new happiness research opportunities of cause-effect type, and it can act as a guideline for practitioners for identifying damaging effects of unhappiness and for fostering happiness on the job.

D. Graziotin, Fabian Fagerholm, Xiaofeng Wang et al. · 236 citations · ⚡13
#computer vision Open access Oct 2004

Mobile-D: an agile approach for mobile application development

Mobile phones have been closed environments until recent years. The change brought by open platform technologies such as the Symbian operating system and Java technologies has opened up a significant business opportunity for anyone to develop application software such as games for mobile terminals. However, developing mobile applications is currently a challenging task due to the specific demands and technical constraints of mobile development. Furthermore, at the moment very little is known about the suitability of the different development processes for mobile application development. Due to these issues, we have developed an agile development approach called Mobile-D. The Mobile-D approach is briefly outlined here and the experiences gained from four case studies are discussed.

P. Abrahamsson, Antti Hanhineva, H. Hulkko et al. · 225 citations · ⚡18

Related blog posts