Skip to content
#small language model Editorial Open access

Commentary: Autism screening and diagnosis in children with congenital heart disease

Aug 2026 · Frontiers in Pediatrics · 8 references

Abstract

Congenital heart disease (CHD) is the most common structural birth anomaly. As perioperative mortality has fallen, attention has rightly shifted toward the neurodevelopmental cost of surviving early cardiac surgery. Ontiveros Perez and colleagues make a timely contribution to this literature. They prospectively link Modified Checklist for Autism in Toddlers, Revised with Follow-Up (M-CHAT-R/ F) screening at 18-30 months to chart-confirmed autism diagnosis, in a cohort of 94 children who required cardiac surgery before initial hospital discharge (1).It is worth restating, at the outset, why the distinction between these two outcomes matters. Screening with the M-CHAT-R/F is a brief, parent report questionnaire, typically administered in a primary-care or follow-up-clinic setting to a large, largely unselected group of children; a positive result flags an elevated likelihood of autism, not the condition itself. Diagnosis, by contrast, requires a comprehensive, in-person evaluation. This generally involves a developmental paediatrician, psychologist or child psychiatrist, standardised observational instruments such as the Autism Diagnostic Observation Schedule and a detailed developmental history, before autism spectrum disorder can be confirmed clinically. The two therefore differ not only in accuracy but in the time, personnel, and resources each demands, and this gap sits at the centre of several issues raised below.Their headline finding is striking: a screen positive rate of 14.6%, and a diagnosis rate of 11.7%, both more than three fold the current general-population estimate (2). This reinforces a signal that has been accumulating across the congenital cardiology literature for a decade. The design has real strengths, particularly its reliance on a defined referral population and on chart verified outcomes, rather than on screening results alone. Several features of the data, nonetheless, warrant closer scrutiny before the findings are translated into practice recommendations, especially for cardiology programmes that lack the structured High-Risk Infant Follow-Up (HRIF) infrastructure that made this study possible.Of the 94 eligible children, only 48 were screened and only 7 screened positive.The confirmed autism subgroup within the screened cohort comprised just six children. Sensitivity of 66-67% therefore rests on the reclassification of a single case, and its reported confidence interval, 0.33 to 1.00, spans almost the entire plausible range (1). The authors are appropriately candid about this. Still, a bare comparison against general population prevalence (2) risks conveying more precision than the underlying numbers can bear.Table 1 places the study's psychometrics beside published benchmarks. What is notable is not that this CHD sample under-performed the general population norming cohort (3); it did not. Rather, its specificity and negative predictive value were unusually high relative to most high risk validation samples. In those samples, the customary trade-off usually runs the opposite way: sensitivity rises while specificity falls, because co-occurring developmental delay inflates false positives (4,5). A plausible explanation here is verification bias. Referral for full evaluation was left to clinician and family discretion, and 46 of 94 eligible children were never screened at all. Without a fixed, non-discretionary protocol, both the numerator and the denominator of these estimates are shaped by judgements the study cannot audit.A second concern is conceptual, rather than statistical. Children with CHD, independent of any autism diagnosis, commonly display weaknesses in theory of mind, pragmatic language and social cognition. These traits can phenotypically resemble autism without meeting full diagnostic criteria (6). The M-CHAT-R/F was normed on low risk and preterm populations, not on children who have undergone cardiopulmonary bypass, deep hypothermic circulatory arrest or repeated infant general anaesthesia. These exposures plausibly affect the very social communication domains the instrument probes, independent of core autism biology (6,7).Read against this background, the study's association between Risk Stratification for Congenital Heart Surgery-2 (RACHS-2) score and autism diagnosis is biologically plausible, but not unambiguous. Greater surgical complexity predicts both closer follow-up and therefore more opportunities for detection and greater hypoxic ischaemic exposure, a genuine risk factor in its own right. A single centre study of this size cannot separate ascertainment from causation, and few current alternatives can either.The authors attribute the association between public insurance and autism diagnosis to California's disability linked insurance eligibility pathways, rather than to true socioeconomic disadvantage (1). This is a reasonable, locally grounded reading. It is also a reminder that "public insurance" is not a portable proxy for socioeconomic status across health systems. In settings structured differently, including most cardiac referral centres outside the United States, this covariate would carry a different meaning entirely. The conclusion, therefore, should not be imported along with the variable.The HRIF model is valuable, but it is not universally available infrastructure.Cognitive and developmental impairment in CHD spans multiple domains and tends to worsen with age (8). Yet, in many referral centres, particularly in resourceconstrained settings, follow-up after infant cardiac surgery remains predominantly cardiological, with limited routine access to structured developmental surveillance.If autism prevalence in children with severe CHD genuinely runs three fold higher than in the general population, as this and prior work suggest (1,4), the practical bottleneck is not simply the decision to screen. It is the referral capacity that a positive result demands, given a positive predictive value of only 57% in this cohort (1). A screening programme without matching evaluation capacity risks generating parental anxiety, without improving outcomes.Ontiveros Perez et al. add welcome toddler period data to a still thin literature.Their central message, that CHD severity requiring early surgery tracks with meaningfully elevated autism likelihood, is consistent with the field (1,4,6). The specific psychometric estimates, however, rest on a small, clinician selected subgroup, and are better treated as hypothesis generating than confirmatory.Larger, multisite cohorts, using universal, non-discretionary screening and spanning varied insurance and resource settings, are needed before the M-CHAT-R/ F's performance in structural heart disease can be considered established. Until then, the more defensible clinical takeaway is not a specific cutoff, but the underlying principle: children surviving early, complex cardiac surgery warrant systematic developmental surveillance, delivered through pathways equipped to act on what screening finds.

Read PDF

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 Open access Feb 2018

Lean Internal Startups for Software Product Innovation in Large Companies: Enablers and Inhibitors

To compete in this age of disruption, large companies cannot rely on cost efficiency, lead time reduction and quality improvement. They are now looking for ways to innovate like startups. Meanwhile, the awareness and use of the Lean startup approach have grown rapidly amongst the software startup community in recent years. This study investigates how Lean internal startup facilitates software product innovation in large companies and identifies its enablers and inhibitors. A multiple case study approach is followed in the investigation. Two software product innovation projects from two large companies are examined, using a conceptual framework that is based on the method-in-action framework and extended with the previously developed Lean-Internal Corporate Venture model. Seven face-to-face in-depth interviews of the employees with different roles are conducted. Within-case analysis and cross-case comparison are applied to draw the findings from the cases. A generic process flow summarises the common key processes of Lean internal startups. The findings suggest that an internal startup that is initiated management or employees faces different challenges. A list of enablers of applying Lean startup in large companies are identified, including top management support and cross-functional team. Both cases face different inhibitors due to the different process of inception, objective of the team and type of the product. Our contributions are threefold. First, this study is one of the first attempt to investigate the use of Lean startup approach in large companies empirically. Second, the study shows the potential of the method-in-action framework to investigate the Lean startup approach in non-startup context. The third is a general process of Lean internal startup and the evidence of the enablers and inhibitors of implementing it, which are both theory-informed and empirically grounded.

Henry Edison, Nina M. Smørsgård, Xiaofeng Wang et al. · 78 citations · ⚡6
#computer vision Conference Sep 2010

Exploring the Sources of Waste in Kanban Software Development Projects

The application of agile software methods and more recently the integration of Lean practices contribute to the trend of continuous improvement in the software industry. One such area warranting proper empirical evidence is a project’s operational efficiency when using the Kanban method. This short paper takes a new angle and explores waste in the Kanban-driven software development project context. A preliminary research model is presented for helping the consequent replication of the study. The results from the empirical analysis suggest Kanban can be an effective method in visualizing and organizing the current work, but does not prevent waste from creeping in, although the overall project outcome may be successful.

Marko Ikonen, Petri Kettunen, Nilay V. Oza et al. · 67 citations · ⚡9

Related blog posts