Diving into Data Science: A Clinical Laboratory Update
Notice bibliographique
Résumé
“Data is like garbage. You’d better know what you are going to do with it before you collect it.” — Mark Twain Mark Twain’s words are perhaps controversial; it is undeniable, however, that data, and what one does with it, has fundamentally changed science and medicine. Clinical laboratories are no exception, and in fact have had a leading role in developing health data sources as well as health data science and analytics. At many laboratories and hospitals, laboratory information systems (LIS) predated robust electronic health record (EHR) systems by years or even decades, establishing them as the first “data warehouses” and bringing with them robust computational methods for quality control, reference range estimation, and clinical decision support. Moreover, the analytical roots of clinical chemistry and laboratory medicine predate even the earliest LIS, emphasizing the analytical mindset deeply rooted in laboratories and clinical pathology. Nonetheless, laboratory data science today is at an inflection point. The size and depth of data available to laboratories, as well as the addition of new data-intensive testing modalities such as genome sequencing or mass spectrometry, is pushing the limits of data storage and the analytic capabilities of laboratories. In parallel, the breakneck advancement of artificial intelligence and machine learning (AI/ML) technologies is creating new opportunities for laboratory data analysis. Finally, as laboratories seek to incorporate laboratory testing and interpretation as an integral element of diagnostic odysseys, integration within the broader healthcare data science field and operationalization of new analytic approaches presents interoperability and regulatory challenges. In this special issue, several articles focus on data pipelines, laboratory-based ML, and quality assurance, including an article by Ammer and colleagues highlighting the use of a R-based package, and a review by Spies and colleagues surveying data-driven anomaly detection methods. The infrastructure needed for data science in the laboratory is addressed in several articles and reviews by Cotten, Forsman, Krumm, McClintock, and Mooney. Future challenges for the field are also highlighted, including opinions and reflections on data science education (Kadauke), reproducibility (Mathias and Master), and interoperability (Chang), and a review of fair and equitable AI/ML practices (Zaydman). Taken as a whole, this special issue highlights many remarkable recent advances of laboratory data science; however, it would be remiss of the editors to not recognize 4 challenges the field faces: The operationalization of data pipelines and algorithms in clinical environments still faces substantial barriers, including: access to, and standardization of, data sources, the ability to leverage necessary technologies (e.g., cloud environments, workflow orchestration, open-source software), improved connectivity within informatics systems, and training of people with the right skills to develop, evaluate, and maintain these applications in production within healthcare/lab IT infrastructure. Second, the field must continue to emphasize the importance of “reproducibility” of data analyses. Such efforts will reduce errors, improve the success and safety of data analyses when operationalized, and support increased regulation of software and algorithms when needed. The field must place continued emphasis on data diversity, equity, and inclusiveness. Increasingly, it is recognized that population-specific data (e.g., reference intervals) improve patient care; conversely, we must be mindful of the (mis-)use of AI/ML methods that do not account for population-specific differences, or worse, actively misrepresent racial, ethnic, or gender-based features. Finally, the field must prioritize education and training of data science and related skills, across all positions and roles within our laboratories. We believe that the methods and tooling for data science, data reproducibility principles, and the fundamentals of AI/ML methods should be taught alongside other “core” skills for laboratory medicine trainees, medical technologists, and other members of the laboratory. We hope you enjoy this special issue of JALM. Author Contributions:All authors confirmed they have contributed to the intellectual content of this paper and have met the following 4 requirements: (a) significant contributions to the conception and design, acquisition of data, or analysis and interpretation of data; (b) drafting or revising the article for intellectual content; (c) final approval of the published article; and (d) agreement to be accountable for all aspects of the article thus ensuring that questions related to the accuracy or integrity of any part of the article are appropriately investigated and resolved. Authors’ Disclosures or Potential Conflicts of Interest:Upon manuscript submission, all authors completed the author disclosure form. Disclosures and/or potential conflicts of interest:Employment or Leadership: N. Krumm, L.A.L. Bazydlo, D.R. Bunch, S. Haymond, and D.T. Holmes, guest editors, The Journal of Applied Laboratory Medicine, AACC. D.T. Holmes, AACC and MSACL; S. Haymond, AACC. Consultant or Advisory Role: None declared. Stock Ownership: None declared. Honoraria: D.R. Bunch, AACC and MSACL; D.T. Holmes, AACC and MSACL; S. Haymond, AACC and Korean Society Laboratory Medicine. Research Funding: D.T. Holmes, SCIEX—loaned instrumentation. Expert Testimony: None declared. Patents: None declared. Other Remuneration: D.T. Holmes, support for attending meetings and/or travel from AACC and MSACL; S. Haymond, support for attending meetings and/or travel from AACC, Korean Society Laboratory Medicine, and MSACL.
Récupéré en direct depuis OpenAlex et désinversé. Les résumés ne sont pas conservés dans cette base de données : les index inversés représentent 8,6 Go des 9,3 Go de texte de la base, et le serveur dispose de 13 Go libres.
Comment cette classification a été obtenuedéplier
Prédiction distillée sur la base complète
Imitation des enseignantsNi prévalence calibrée, ni vérité terrain. Validation humaine à venir. Apprise à partir de 10 348 étiquettes directes de Codex et de 10 348 étiquettes directes de Gemma. Le mode candidate est l'union des têtes enseignantes seuillées; le consensus est leur intersection. Ces sorties portent le statut machine_predicted_unvalidated et ne sont ni des étiquettes humaines ni des étiquettes directes de modèles de pointe.
Scores Codex et Gemma par catégorie
| Catégorie | Codex | Gemma |
|---|---|---|
| Métarecherche | 0,050 | 0,011 |
| Méta-épidémiologie (sens strict) | 0,000 | 0,000 |
| Méta-épidémiologie (sens large) | 0,001 | 0,000 |
| Bibliométrie | 0,000 | 0,004 |
| Études des sciences et des technologies | 0,000 | 0,002 |
| Communication savante | 0,000 | 0,001 |
| Science ouverte | 0,002 | 0,001 |
| Intégrité de la recherche | 0,000 | 0,002 |
| Charge utile insuffisante (le modèle a refusé de juger) | 0,000 | 0,000 |
Scores machine (provisoires)
Les deux têtes enseignantes du modèle étudiant, lues sur ce travail. Un score ordonne la base pour la relecture; il n'affirme jamais une catégorie, et le statut de validation accompagne chaque rangée tel quel.
Scores de référence d'un modèle non mature (critères de maturité non atteints, 7 itérations). Un score ordonne; il n'affirme jamais une catégorie.
score_only:v0-immature-baseline · tel quel depuis la passe de notation : score_only signifie que le nombre peut ordonner les travaux, et qu'aucune étiquette de catégorie n'en découleClassification
machine, non validéePrédiction automatique; les deux têtes enseignantes s’accordent sur ce qui est montré ici.
Le détail, modèle par modèle et score par score, se trouve en fin de page sous « Comment cette classification a été obtenue ».