<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>unsupervised machine learning in autoimmune diseases &#8211; Science</title>
	<atom:link href="https://scienmag.com/tag/unsupervised-machine-learning-in-autoimmune-diseases/feed/" rel="self" type="application/rss+xml" />
	<link>https://scienmag.com</link>
	<description></description>
	<lastBuildDate>Fri, 16 Oct 2026 23:26:51 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=7.1.3</generator>

<image>
	<url>https://scienmag.com/wp-content/uploads/2024/07/cropped-scienmag_ico-32x32.jpg</url>
	<title>unsupervised machine learning in autoimmune diseases &#8211; Science</title>
	<link>https://scienmag.com</link>
	<width>32</width>
	<height>32</height>
</image> 
<site xmlns="com-wordpress:feed-additions:1">73899611</site>	<item>
		<title>Machine learning reveals four hidden lupus phenotypes among patients starting belimumab</title>
		<link>https://scienmag.com/machine-learning-reveals-four-hidden-lupus-phenotypes-among-patients-starting-belimumab/</link>
		
		<dc:creator><![CDATA[Teresa Odom]]></dc:creator>
		<pubDate>Fri, 16 Oct 2026 23:26:51 +0000</pubDate>
				<category><![CDATA[Science News]]></category>
		<category><![CDATA[B-cell targeted therapies in autoimmune diseases]]></category>
		<category><![CDATA[belimumab]]></category>
		<category><![CDATA[belimumab treatment response heterogeneity]]></category>
		<category><![CDATA[biologic therapy]]></category>
		<category><![CDATA[data-driven lupus classification]]></category>
		<category><![CDATA[heterogeneity of lupus clinical presentations]]></category>
		<category><![CDATA[hidden lupus patient subgroups]]></category>
		<category><![CDATA[hydroxychloroquine]]></category>
		<category><![CDATA[Italian Lupus Registry research]]></category>
		<category><![CDATA[LIRE registry]]></category>
		<category><![CDATA[lupus nephritis]]></category>
		<category><![CDATA[Lupus phenotypes identification using machine learning]]></category>
		<category><![CDATA[Machine learning]]></category>
		<category><![CDATA[machine learning for lupus phenotyping]]></category>
		<category><![CDATA[organ damage]]></category>
		<category><![CDATA[organ damage trajectories in lupus]]></category>
		<category><![CDATA[patient phenotypes]]></category>
		<category><![CDATA[personalized medicine in lupus]]></category>
		<category><![CDATA[Precision medicine]]></category>
		<category><![CDATA[rheumatology]]></category>
		<category><![CDATA[systemic lupus erythematosus]]></category>
		<category><![CDATA[systemic lupus erythematosus clinical subtypes]]></category>
		<category><![CDATA[unsupervised clustering]]></category>
		<category><![CDATA[unsupervised machine learning in autoimmune diseases]]></category>
		<guid isPermaLink="false">https://scienmag.com/?p=291162</guid>

					<description><![CDATA[An unsupervised machine-learning analysis of the Italian LIRE registry has identified four clinically distinct phenotypes among systemic lupus erythematosus patients initiating belimumab, with renal and serologically active profiles showing a numerically higher response rate and neuropsychiatric or cardiovascular involvement carrying the heaviest burden of organ damage.]]></description>
										<content:encoded><![CDATA[<p>Systemic lupus erythematosus has always been a disease of disguises. One patient may present with a butterfly rash and aching joints, while another battles kidney inflammation, seizures or destroyed blood cells, yet all can carry the same diagnosis and, increasingly, be prescribed the same biologic drug. A new study from the Italian Lupus Italian REgistry (LIRE) has now used an unsupervised machine-learning algorithm to strip away physician assumptions and let the data speak for itself, revealing that patients starting belimumab fall into four strikingly different clinical phenotypes, each with its own trajectory of response and organ damage.</p>
<p>The research, published in Frontiers in Lupus and conducted with the support of the Italian Society of Rheumatology, addressed a deceptively simple question: when rheumatologists prescribe belimumab, an antibody that blocks the B-cell activating factor BLyS, are they actually treating one population or several hidden ones? International guidelines leave considerable discretion to clinicians, defining refractory lupus loosely as an insufficient response to standard therapy with glucocorticoids and hydroxychloroquine, with or without failure of a conventional immunosuppressant. That flexibility, combined with the notorious heterogeneity of lupus itself, has long suggested that the belimumab-treated population conceals internal structure that average treatment statistics cannot capture.</p>
<p>To find that structure without bias, the team turned to unsupervised learning, a branch of machine learning that discovers patterns in data without any investigator-driven labels or outcome variables. The researchers fed 150 baseline variables, spanning demographics, organ-domain manifestations, serological markers, treatment history, comorbidities and damage items, into a Factor Analysis of Mixed Data, or FAMD, a generalization of classical principal component analysis designed to handle both continuous measurements and categorical features simultaneously. FAMD internally standardizes the variables, one-hot encodes categorical features and divides them by the square root of their probability, producing principal components that explain the maximum variance in the dataset. Five components were retained, together explaining 68.37 percent of the total variance, a number chosen using the scree and elbow criteria applied to the proportion of variance explained.</p>
<p>On top of those components, the team applied Hierarchical Clustering on Principal Components using Ward&#8217;s criterion and Euclidean distance, a method that successively merges the patients whose profiles are most similar while minimizing the within-cluster inertia. Inspection of the dendrogram and of the elbow in the inter-cluster inertia gain curve pointed unambiguously to a four-cluster solution. The analysis was implemented in Python using the Prince, scipy, scikit-learn and numpy libraries, and drew on prospectively collected records from the multicentric LIRE registry. Of 143 patients who had started a biologic agent, 128 belimumab initiators had complete baseline data, and 125 were assigned to the four main clusters; three patients formed small isolated terminal branches on the dendrogram and were excluded from cluster-level analyses.</p>
<p>The four phenotypes were immediately recognizable to any lupus specialist, yet their emergence from raw data was anything but guaranteed. Cluster 1, the largest with 55 patients, exhibited the lowest baseline damage scores and no prominent organ-specific signature. Cluster 2, with 28 patients, was dominated by renal involvement, with 89.3 percent carrying biopsy-proven lupus nephritis, frequent proteinuria and the strongest complement consumption, with 92.9 percent showing low complement levels. Cluster 3, the smallest with 14 patients, displayed severe neuropsychiatric and cardiovascular activity, including psychosis in 35.7 percent, cerebral vasculitis and seizures, together with the highest baseline SLICC Damage Index, enriched neurological and cardiovascular damage, more antiphospholipid antibodies and the lowest hydroxychloroquine use at 78.6 percent versus 95.2 percent in the other clusters. Cluster 4, with 28 patients, gathered patients with predominant hematological abnormalities, notably hemolytic anemia, which was significantly more prevalent in this group.</p>
<p>Crucially, the clusters were comparable in age, sex, ethnicity and even overall disease activity measured by the SLEDAI-2K, meaning the algorithm had separated patients not by how sick they were in aggregate but by the specific pattern of their illness. Articular and mucocutaneous manifestations, the domains where belimumab&#8217;s effectiveness is best established, were distributed evenly across all clusters, which the authors attribute to widely accepted data on the drug&#8217;s performance in those domains. The segregation instead tracked established damage, former treatments such as prior cyclophosphamide exposure, concomitant comorbidities and serological features, revealing that the belimumab population is heterogeneous in ways that go far beyond the overt manifestations that triggered the prescription.</p>
<p>When the researchers followed the patients for 12 months, disease activity fell significantly in the whole cohort and in every cluster, with median SLEDAI-2K dropping from 9 at baseline to 4 by month 12. Clinical response, defined as a clinical SLEDAI-2K of zero at 6 and 12 months, was statistically comparable across clusters, and in logistic regression models cluster membership did not significantly predict the probability of achieving response. Yet a suggestive pattern emerged: Cluster 2, the renal and serologically active phenotype, showed a numerically higher response rate at one year, 70.8 percent versus 52.3 percent in the other clusters, a difference that narrowly missed statistical significance at p = 0.082. The observation aligns with previous real-world evidence supporting belimumab as add-on therapy in renal lupus, and the authors note that patients in this cluster more frequently received mycophenolate mofetil, which may have acted synergistically with the biologic.</p>
<p>The damage trajectories told a more sobering story. Final SLICC Damage Index was highest in Cluster 3 throughout follow-up, consistent with the principle that established damage begets further damage, a burden compounded by higher glucocorticoid dosages and suboptimal hydroxychloroquine intake, both factors previously linked to damage accrual. More unexpectedly, Cluster 1, despite its milder initial phenotype and optimized hydroxychloroquine use, accrued damage faster than the other clusters over the 12 months, with a statistically significant though clinically modest increase in SDI items and no repetitive pattern among them. The authors caution that the median disease duration of around 10 years at belimumab initiation may have prevented early treatment and hampered damage prevention, and they speculate that this cluster may have gathered patients vulnerable to progression for reasons not yet identified, possibly related to interferon activity suggested by a relatively high proportion of anti-ENA positivity.</p>
<p>The study has clear limitations that the authors confront directly. The cohort was relatively small, data came from a real-world registry requiring imputation of residual missing values below 8 percent per variable, and clustering was performed only on patients with sufficiently complete baseline records, which may have introduced selection bias. No independent external cohort was available to validate the four clusters, so external validation will be required to confirm their robustness and generalizability. The authors also acknowledge that Italian reimbursement criteria, which require positive serology or a baseline SLEDAI-2K of at least 10, may have flattened subtle differences in patient profiling, and that differences in the temporal dynamics of response between clusters were not specifically addressed and warrant dedicated investigation.</p>
<p>From a translational perspective, the findings should not be read as definitive therapeutic subgroups, but they generate concrete hypotheses for future research: whether patients with renal and serologically active profiles benefit from earlier or more intensive biologic intervention, and whether molecular phenotyping, such as the enrichment of transitional B cells recently associated with better belimumab response regardless of clinical expression, could sharpen the stratification that clinical variables alone cannot achieve. The authors conclude that diverse immunological pathways can produce similar clinical manifestations, meaning that clinical and laboratory phenotyping cannot fully account for the variability threading through a lupus population. Unsupervised learning, they argue, may complement clinical judgment, leading to a deeper understanding of lupus phenotypes and, ultimately, to individualized drug allocation in a disease that has always resisted one-size-fits-all medicine.</p>
<p><strong>Subject of Research:</strong> Unsupervised machine-learning algorithm identifies clinically distinct phenotypes across patients initiating belimumab in the Lupus Italian REgistry (LIRE)</p>
<p><strong>Article Title:</strong> Unsupervised machine-learning algorithm identifies clinically distinct phenotypes across patients initiating belimumab in the Lupus Italian REgistry (LIRE)</p>
<p><strong>Article References:</strong> Gatto, M., Venerito, V., Rozza, D., Landolfi, G., Scirè, C. A., Carrara, G., Di Nicola, C., Iagnocco, A., Sebastiani, G. D., Conti, F., Doria, A., &amp; in collaboration with the Lupus Italian REgistry (LIRE) (2026). Unsupervised machine-learning algorithm identifies clinically distinct phenotypes across patients initiating belimumab in the Lupus Italian REgistry (LIRE). <em>Frontiers in Lupus, 4</em>, Article 1757086. <a href="https://doi.org/10.3389/flupu.2026.1757086" rel="noopener noreferrer">https://doi.org/10.3389/flupu.2026.1757086</a></p>
<p><strong>Image Credits:</strong> AI Generated</p>
<p><strong>DOI:</strong> <a href="https://doi.org/10.3389/flupu.2026.1757086" rel="noopener noreferrer">10.3389/flupu.2026.1757086</a></p>
<p><strong>Keywords:</strong> belimumab, systemic lupus erythematosus, machine learning, unsupervised clustering, LIRE registry, lupus nephritis, patient phenotypes, hydroxychloroquine, organ damage, precision medicine, rheumatology, biologic therapy</p>
]]></content:encoded>
					
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">291162</post-id>	</item>
	</channel>
</rss>
