Sep 2026· Frontiers in Digital Health· 0 citations· 19 references
Machine Learning in Healthcare
Abstract
Post-market surveillance for adverse events of special interest is often constrained by key diagnostic elements being captured primarily in unstructured clinical notes and reports. This feasibility study evaluated large language model (LLM) and clinical quality language (CQL) methodologies to perform phenotype feature extraction and outcome determination on Fast Healthcare Interoperability Resources (FHIR) data.
Two health systems identified patients with an mRNA COVID-19 vaccination and an inpatient myocarditis diagnosis within 42 days. Patient FHIR data was retrieved via a Health Information Exchange and converted into narrative text (“textified”). Llama3.3 70B Instruct answered yes/no Brighton Collaborative–based myocarditis feature questions; answers were written back as FHIR Observation resources to enhance each patient bundle. Three methods were compared: simple CQL (structured data only), LLM (textified FHIR data), and enhanced CQL (CQL on enhanced bundles). Three clinicians provided gold-standard determinations. An optimization set (
n
= 10) supported pipeline refinement; performance was evaluated in a test set (
n
= 25).
In the test set, simple CQL performed poorly for identifying cardiac and non-specific symptoms [Matthews Correlation Coefficient (MCC): 0.08; F1: 0.02] but excellently for cardiac biomarkers (MCC:0.83; F1: 0.88). The LLM achieved excellent performance identifying symptoms and imaging features (e.g., echocardiogram abnormalities MCC: 0.86) but weaker performance for biomarkers (MCC: 0.54). Enhanced CQL had excellent feature identification performance across most domains. Both LLM and enhanced CQL correctly determined the myocarditis outcome for 23 of 25 patients.
In this small feasibility study, structured and unstructured FHIR data provided the computable phenotypes using an LLM with sufficient clinical information for myocarditis feature identification and outcome determination.
The results are packaged in the Greenfield Startup Model (GSM), which explains the priority of startups to release the product as quickly as possible, and the need to shorten time-to-market, by speeding up the development through low-precision engineering activities.
Carmine Giardino, Nicolò Paternoster, M. Unterkalmsteiner et al.· IEEE Transactions on Softwar...· 178 citations· ⚡14
Software startup companies develop innovative, software-intensive products within limited timeframes and with few resources, searching for sustainable and scalable business models.
M. Unterkalmsteiner, P. Abrahamsson, Xiaofeng Wang et al.· e-Informatica Software Engin...· 157 citations· ⚡17
This study conducts a case survey study based on the secondary data of the major pivots happened in 49 software startups, and demonstrates that customer need pivot is the most common among all pivot types.
Sohaib Shahid Bajwa, Xiaofeng Wang, Anh Nguyen-Duc et al.· Empirical Software Engineeri...· 127 citations· ⚡15
The comparison of adopter and non-adopter sample reveals three potential adoption inhibitor, security, data privacy, and portability, which underlines the importance of the technical and security perspectives for research investigating the adoption of technology.
Nattakarn Phaphoom, Xiaofeng Wang, S. Samuel et al.· Journal of Systems and Softw...· 111 citations· ⚡8
This study investigates how Lean internal startup facilitates software product innovation in large companies and identifies its enablers and inhibitors, and shows the potential of the method-in-action framework to investigate the Lean startup approach in non-startup context.
Henry Edison, Nina M. Smørsgård, Xiaofeng Wang et al.· Journal of Systems and Softw...· 78 citations· ⚡6
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.· EUROMICRO Conference on Soft...· 67 citations· ⚡9
Related blog posts
MIT News · Artificial Intelligence· news.mit.eduSep 14, 2026
The “HardFlow” algorithm could help generative AI models produce high-quality outputs that obey strict requirements when “pretty close” doesn’t cut it.
AI may appear weightless, but every model depends on physical infrastructure. To understand responsible AI, we need to look beyond algorithms and consider the entire lifecycle of the hardware behind them. The post Responsible AI Must Consider Its Afterlife appeared first on GPT-Lab.