ArticleHNO2026
[Web-based translation software in clinical practice : A survey in a German university hospital including a data protection and liability perspective].
Article in HNO, 2026. The graph could read no effect estimate from its abstract, so it casts no vote on the map. Not yet cited in PubMed.
What it found
Each row is one number read from the abstract, on the scale the paper reported it, with its interval. Left of the dashed line favours the treatment, right favours the comparator. Under each row is the sentence it came from. New to these charts? A ten-minute tutorial.
The abstract states no effect estimate the extractor could read, or names no intervention and outcome on the map, so this paper lights no cell and moves no belief. It is still indexed, cited and linked below.
The trial behind it
Trials whose registry record cites this paper, or whose number appears in the abstract. A trial that started after this paper was published is citing it as background, not reporting it.
Neither the registry nor the abstract names a trial number. If this is a trial report, that itself is worth knowing.
Who cites it
0 citing papers in PubMed.
No citing paper in PubMed yet.
Corrections and comments
PubMed lists nothing against this paper. Absence here is not a guarantee, only a check that was made.
Authors and funding
9 authors.
Funding
No grant is acknowledged in the PubMed record.
Abstract
backgroundLanguage barriers are an obstacle in everyday clinical practice. Webbased translation software can offer a low-barrier solution. This study examines the attitudes of employees at a German university hospital towards language barriers and web-based translation software. Furthermore, general data protection aspects for their application in everyday clinical practice are adressed.
methodsEmployees of a university hospital were surveyed on language barriers, their occurrence, strategies for overcoming them, as well as their use of web-based translation software. Furthermore, the use of such software was analyzed from a data protection and liability perspective.
resultsA majority of 80% (111/138) stated that they encountered language barriers in less than half of all patient contacts. Translation software was used in at least half of such cases by 22% (31/138) of respondents. The usefulness of translation software was rated as predominantly positive by 49% (68/138). From a legal perspective, it is strongly recommended that personal data be excluded when using web-based translation software. The use of anonymized data is permissible under data protection regulations. In emergencies or similar exceptional situations, the processing of personal data is also subject to the applicable data protection legislation in these situations. Provided that data protection legislation requirements are met, the use of personal data is permissible. A general assessment of liability during the use of webbased translation software to fulfill the duty of informed consent is not possible, as it is highly dependent on case-specific factors. However, since translation errors may be attributable in individual cases, a human interpreter should be consulted whenever the treating professional has doubts regarding the patient's understanding or the comprehensibility of the information provided.
conclusionLanguage barriers pose a potential risk in everyday clinical practice. Webbased translation software is easily accessible and could improve patient safety and treatment outcomes. As the use of anonymized data is feasible in most cases, there are no data protection obstacles to using webbased translation software with such data. In the event of any doubt regarding the patient's understanding of the information provided, the involvement of a human translator is recommended to minimize liability risks.
Indexed as
Identifiers
42557408What OpenQuestion holds
Registered trials
Read under generation 80e0d062 · epoch 390. Bibliography from PubMed, PubMed Central and OpenAlex; grants from NIH RePORTER; trial links from ClinicalTrials.gov; estimates, votes and beliefs from the OpenQuestion graph.