Skip to content

Competence Is Not Protection: Prompt-Channel Demographic Bias in Pathology Vision-Language Models, and the Geometry That Predicts It

Aug 2026 · Zenodo (CERN European Organization for Nuclear Research) · 4 references
AI in cancer detection

Abstract

Part IV of a series on equity and reliability in medical imaging AI. Part III of this series showed that naming a demographic group in the text prompt of a medical vision–language model changes its diagnosis on a fixed chest radiograph, that the perturbation is exactly rank one in the standard positive/negative pair readout, and that group-specific thresholds therefore provably cannot remove it. Two questions were left open: whether any of this survives a change of imaging domain, and whether it matters for a model that is actually good at its task — Part III's strongest encoder reached a mean AUC of 0.687. This paper audits four pathology vision–language models (PLIP, QuiltNet-B-32, CONCH, and the slide-level TITAN) under the descriptor set from Part III, unchanged, and combines them with Part III's three radiology encoders for a seven-model comparison spanning two imaging domains and both patch and slide granularity. On TITAN the audit runs at full strength: 8,010 whole-slide images from 6,582 patients across 25 TCGA cancer types, every interval clustered on patient, mean neutral-prompt AUC 0.982 with all 25 projects clearing the utility floor. Four results. The rank-one identity transfers exactly — verified to 5.2×10−8 on real slide embeddings, two orders of magnitude tighter than Part III because TITAN has no learned logit scale to amplify float error. Part III's threshold-irremovability corollary therefore holds for whole-slide pathology. Diagnostic competence does not protect against prompt-channel bias. Across seven encoders, neutral-prompt AUC does not predict the effect (r = −0.443, p = 0.32): CONCH at AUC 0.849 shows 21.1 points of mean absolute excess false-negative rate, indistinguishable from OpenAI CLIP at AUC 0.518. What predicts it is a purely geometric quantity, the descriptor perturbation measured against the diagnostic contrast (r = +0.780, p = 0.039), reported as a hypothesis with n = 7 rather than a law. The model answers the token and not its truth, including for race. Part III could test congruence only for sex and age, because NIH ChestX-ray14 records no race; TCGA does, and the difference-in-differences estimator gives a median 0.0045 logits for race and 0.0010 for sex, against a specimen-site positive control 164–730× larger in 4 of 4 pairs at tighter precision. Anatomically impossible descriptors — "a male patient showing endometrial carcinoma" — move the score as much as coherent ones. Prompt symmetrisation is a domain-dependent intervention rather than a general one: it removes 59–63% of the effect on radiology encoders, 26–34% on pathology patch encoders, and amplifies the effect by 94% on TITAN. The text-side symmetry residual separates the two domains completely (Mann–Whitney p = 0.029). The practical consequence is a correction to how this series has framed mitigation. A deployer cannot infer prompt-channel robustness from a model's accuracy, and cannot assume a mitigation validated in one imaging domain transfers to another — including on the strength of Part III. Honest scope. Unlike Parts II, IIb, and III, this part is not preregistered; PROTOCOL_PART4.md is retrospective and says so in its first line, recording which hypotheses preceded their endpoints and which did not. Only TITAN carries interval estimates: the public CRC-VAL-HE-7K mirror records no patient identifiers, so the three patch-level encoders are reported as point estimates only. The anatomically-impossible result rests on five cells and is a demonstration of mechanism, not an estimate of magnitude. This paper also supplies the out-of-domain evidence behind amendment 8 to Part III's protocol, which withdrew Part III's proposed text-only predictor of symmetrisation failure. Files. The manuscript PDF (21 pp, 4 figures); the retrospective protocol; and an artifact archive containing all 13 analysis scripts and every result table as CSV/JSON. Model weights are not redistributed — TITAN, CONCH, and UNI are CC-BY-NC-ND-4.0 and were obtained through the gated Hugging Face process. Ethics. No patient data was collected. TCGA is a public consortium dataset; CRC-VAL-HE-7K is public and de-identified. This is an audit of a model property, not a clinical study, and makes no claim about patient outcomes.

View source

Similar papers

#computer vision Open access Jun 2016

Software Development in Startup Companies: The Greenfield Startup Model

Software startups are newly created companies with no operating history and oriented towards producing cutting-edge products. However, despite the increasing importance of startups in the economy, few scientific studies attempt to address software engineering issues, especially for early-stage startups. If anything, startups need engineering practices of the same level or better than those of larger companies, as their time and resources are more scarce, and one failed project can put them out of business. In this study we aim to improve understanding of the software development strategies employed by startups. We performed this state-of-practice investigation using a grounded theory approach. We packaged the results in the Greenfield Startup Model (GSM), which explains the priority of startups to release the product as quickly as possible. This strategy allows startups to verify product and market fit, and to adjust the product trajectory according to early collected user feedback. The need to shorten time-to-market, by speeding up the development through low-precision engineering activities, is counterbalanced by the need to restructure the product before targeting further growth. The resulting implications of the GSM outline challenges and gaps, pointing out opportunities for future research to develop and validate engineering practices in the startup context.

Carmine Giardino, Nicolò Paternoster, M. Unterkalmsteiner et al. · 179 citations · ⚡14
#computer vision Open access Oct 2016

Software Startups - A Research Agenda

Software startup companies develop innovative, software-intensive products within limited timeframes and with few resources, searching for sustainable and scalable business models. Software startup ...

M. Unterkalmsteiner, P. Abrahamsson, Xiaofeng Wang et al. · 157 citations · ⚡17
#machine learning Review Open access Oct 2016

“Failures” to be celebrated: an analysis of major pivots of software startups

In the context of software startups, project failure is embraced actively and considered crucial to obtain validated learning that can lead to pivots. A pivot is the strategic change of a business concept, product or the different elements of a business model. A better understanding is needed on different types of pivots and different factors that lead to failures and trigger pivots, for software entrepreneurial teams to make better decisions under chaotic and unpredictable environment. Due to the nascent nature of the topic, the existing research and knowledge on the pivots of software startups are very limited. In this study, we aimed at identifying the major types of pivots that software startups make during their startup processes, and highlighting the factors that fail software projects and trigger pivots. To achieve this, we conducted a case survey study based on the secondary data of the major pivots happened in 49 software startups. 10 pivot types and 14 triggering factors were identified. The findings show that customer need pivot is the most common among all pivot types. Together with customer segment pivot, they are common market related pivots. The major product related pivots are zoom-in and technology pivots. Several new pivot types were identified, including market zoom-in, complete and side project pivots. Our study also demonstrates that negative customer reaction and flawed business model are the most common factors that trigger pivots in software startups. Our study extends the research knowledge on software startup pivot types and pivot triggering factors. Meanwhile it provides practical knowledge to software startups, which they can utilize to guide their effective decisions on pivoting.

Sohaib Shahid Bajwa, Xiaofeng Wang, Anh Nguyen-Duc et al. · 127 citations · ⚡15
#computer vision Review Open access May 2015

A survey study on major technical barriers affecting the decision to adopt cloud services

In the context of cloud computing, risks associated with underlying technologies, risks involving service models and outsourcing, and enterprise readiness have been recognized as potential barriers for the adoption. To accelerate cloud adoption, the concrete barriers negatively influencing the adoption decision need to be identified. Our study aims at understanding the impact of technical and security-related barriers on the organizational decision to adopt the cloud. We analyzed data collected through a web survey of 352 individuals working for enterprises consisting of decision makers as well as employees from other levels within an organization. The comparison of adopter and non-adopter sample reveals three potential adoption inhibitor, security, data privacy, and portability. The result from our logistic regression analysis confirms the criticality of the security concern, which results in an up to 26-fold increase in the non-adoption likelihood. Our study underlines the importance of the technical and security perspectives for research investigating the adoption of technology.

Nattakarn Phaphoom, Xiaofeng Wang, S. Samuel et al. · 111 citations · ⚡8
#computer vision Conference Open access Dec 2013

Affordable and Energy-Efficient Cloud Computing Clusters: The Bolzano Raspberry Pi Cloud Cluster Experiment

We present our ongoing work building a Raspberry Pi cluster consisting of 300 nodes. The unique characteristics of this single board computer pose several challenges, but also offer a number of interesting opportunities. On the one hand, a single Raspberry Pi can be purchased cheaply and has a low power consumption, which makes it possible to create an affordable and energy-efficient cluster. On the other hand, it lacks in computing power, which makes it difficult to run computationally intensive software on it. Nevertheless, by combining a large number of Raspberries into a cluster, this drawback can be (partially) offset. Here we report on the first important steps of creating our cluster: how to set up and configure the hardware and the system software, and how to monitor and maintain the system. We also discuss potential use cases for our cluster, the two most important being an inexpensive and green test bed for cloud computing research and a robust and mobile data center for operating in adverse environments.

P. Abrahamsson, S. Helmer, Nattakarn Phaphoom et al. · 110 citations · ⚡7
#computer vision Book Open access Mar 2017

On the Unhappiness of Software Developers

The happy-productive worker thesis states that happy workers are more productive. Recent research in software engineering supports the thesis, and the ideal of flourishing happiness among software developers is often expressed among industry practitioners. However, the literature suggests that a cost-effective way to foster happiness and productivity among workers could be to limit unhappiness. Psychological disorders such as job burnout and anxiety could also be reduced by limiting the negative experiences of software developers. Simultaneously, a baseline assessment of (un)happiness and knowledge about how developers experience it are missing. In this paper, we broaden the understanding of unhappiness among software developers in terms of (1) the software developer population distribution of (un)happiness, and (2) the causes of unhappiness while developing software. We conducted a large-scale quantitative and qualitative survey, incorporating a psychometrically validated instrument for measuring (un)happiness, with 2 220 developers, yielding a rich and balanced sample of 1318 complete responses. Our results indicate that software developers are a slightly happy population, but the need for limiting the unhappiness of developers remains. We also identified 219 factors representing causes of unhappiness while developing software. Our results, which are available as open data, can act as guidelines for practitioners in management positions and developers in general for fostering happiness on the job. We suggest considering happiness in future studies of both human and technical aspects in software engineering.

D. Graziotin, Fabian Fagerholm, Xiaofeng Wang et al. · 84 citations · ⚡6

Related blog posts