Browse State-of-the-Art › Patient Phenotyping
Patient Phenotyping
7 papers with code · 1 benchmark · 1 dataset archive 2025-07-28
Benchmarks archive 2025-07-28
1 leaderboard table shown for this task, 1 with rows (a “benchmark” on this site is a table with at least one row, as on /sota), ordered by row count. “Best model” is the first row in the archive's own order at snapshot; nothing is re-ranked here and metric direction is not recorded in the archive. PwC's Trend sparklines are not in the archive, so that column is omitted.
| Dataset | Best model (first row in archive order) | Paper | Code | Syntology | Compare |
|---|---|---|---|---|---|
| HiRID (7 rows) | LGBM ( + hand crafted features) | HiRID-ICU-Benchmark -- A Comprehensive Machine Learning Benchmark... | code | Syntology official (archive's flag): 5 ran · 5 ran (of which 0 constructed an object rather than computing a result; 5 with no instrument failure: 0 honoured, 0 violated, 5 with no contract checked; 0 where Syntology's instrument failed) · 3 unverified | Compare |
Syntology column: samples harvested from the paper's repositories and executed on synthesized fixtures; “ran” is not a correctness claim and does not order the table. Each line reads “N ran (of which C constructed an object rather than computing a result; K with no instrument failure: H honoured, V violated, P with no contract checked; I where Syntology's instrument failed) · U unverified”; the instrument figure counts failures of Syntology's instrument, not of the code. When the archive marks a repository official for the row's paper, the line starts with that repository's state (“official” is the archive's flag, not a verdict on who wrote the code; “community repositories only” when every sample that ran came from a community repository, “official: no sample here; runs from other or unrecorded repositories” when some came from a repository the paper names or has in its text, or from none recorded); hover it for the repositories the samples that ran came from. A dash means no Syntology record for that paper, not a recorded non-run. Each “ran” line links to that paper's sample list. Syntology's record for this page last changed ; when this build read Syntology's graph is in the build record. For agents: get_harvested_code_for_paper(arxiv_id) lists each paper's samples; how to connect.
Libraries
Not in the archive: the export carries no per-task library table, so there is nothing to show at snapshot 2025-07-28.
Datasets archive 2025-07-28
1 dataset whose archive record lists this task, ordered by the archive's paper count.
Subtasks archive 2025-07-28
No subtask under this task in the archive's task tree.
Parent tasks archive 2025-07-28
Papers archive 2025-07-28
archive papers tagged: 15 · with a code link: 7 · where Syntology ran a sample: 1 (1 with a run with no instrument failure, 0 where every run was a failure of Syntology's instrument) Syntology
Show: all tagged papersonly where code ran (1 of 15 tagged: 1 with a run with no instrument failure, 0 where every run was a failure of Syntology's instrument)
Page 1 of 1: papers 1 to 15 of 15, in archive order: by repositories listed in the archive (most first), then newest first, not by stars (the archive holds no stars, so PwC's “Social” and “Latest” sorts cannot be reproduced). Papers that list no repository come after every paper that lists one.
Papers without a page here are shown as plain text. A Syntology line reads “N ran (of which C constructed an object rather than computing a result; K with no instrument failure: H honoured, V violated, P with no contract checked; I where Syntology's instrument failed) · U unverified”; the figure “where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. When the archive marks a repository official for the paper, the line starts with that repository's state (the archive's flag, not a verdict on who wrote the code); hover it for the repositories the samples that ran came from.
-
2 Oct 2019 2 repositories listedThis is the first public benchmark on a multi-centre critical care dataset, comparing the performance of clinical gold standard with our predictive model.
-
26 Jun 2025 1 repository listedThe discovery of multiple patient phenotypes for the same medical phenomenon would be useful in such cases.
-
23 Aug 2022 1 repository listedWe describe a method for phenotype recognition that imputes phenotype codes for all UK Biobank participants.
-
28 Nov 2021 1 repository listedMethods: We propose a new unsupervised machine learning technique, denominated as Trace-based clustering, and a 5-step methodology in order to support clinicians when identifying patient phenotypes.
-
16 Nov 2021 1 repository listed Syntology official (archive's flag): 5 ran · 5 ran (of which 0 constructed an object rather than computing a result; 5 with no instrument failure: 0 honoured, 0 violated, 5 with no contract checked; 0 where Syntology's instrument failed) · 3 unverified (of 8 harvested samples) · 6 pointer-only (licence)The recent success of machine learning methods applied to time series collected from Intensive Care Units (ICU) exposes the lack of standardized machine learning benchmarks for developing and comparing such methods.
-
15 Jun 2020 1 repository listedIn this paper, we develop a deep learning approach for clustering time-series data, where each cluster comprises patients who share similar future outcomes of interest (e. g., adverse events, the onset of comorbidities).
-
5 Jul 2019 1 repository listedIn the five chief complaints, we find between 2 and 6 clusters, with the peak mean pairwise ARI between subsequent training iterations to range from 0.
-
Learning to Predict Global Atrial Fibrillation Dynamics from Sparse Measurements13 Feb 2025 0 repositories listedCatheter ablation of Atrial Fibrillation (AF) consists of a one-size-fits-all treatment with limited success in persistent AF.
-
M3H: Multimodal Multitask Machine Learning for Healthcare29 Apr 2024 0 repositories listedDeveloping an integrated many-to-many framework leveraging multimodal data for multiple tasks is crucial to unifying healthcare applications ranging from diagnoses to operations.
-
Collaborative learning of common latent representations in routinely collected multivariate ICU physiological signals27 Feb 2024 0 repositories listedIn Intensive Care Units (ICU), the abundance of multivariate time series presents an opportunity for machine learning (ML) to enhance patient phenotyping.
-
Pain Forecasting using Self-supervised Learning and Patient Phenotyping: An attempt to prevent Opioid Addiction9 Oct 2023 0 repositories listedSickle Cell Disease (SCD) is a chronic genetic disorder characterized by recurrent acute painful episodes.
-
Towards dynamic multi-modal phenotyping using chest radiographs and physiological data4 Nov 2021 0 repositories listedThe healthcare domain is characterized by heterogeneous data modalities, such as imaging and physiological data.
-
A Corpus for Detecting High-Context Medical Conditions in Intensive Care Patient Notes Focusing on Frequently Readmitted Patients6 Mar 2020 0 repositories listedA crucial step within secondary analysis of electronic health records (EHRs) is to identify the patient cohort under investigation.
-
Actor-Critic Approach for Temporal Predictive Clustering25 Sep 2019 0 repositories listedDue to the wider availability of modern electronic health records (EHR), patient care data is often being stored in the form of time-series.
-
Comparing Rule-Based and Deep Learning Models for Patient Phenotyping25 Mar 2017 0 repositories listedObjective: We investigate whether deep learning techniques for natural language processing (NLP) can be used efficiently for patient phenotyping.
Syntology lines on 1 of the papers shown; no Syntology record for the others (a paper without an arXiv id cannot be joined to the graph, and absence from the graph layer is not a recorded non-run). “Ran” means the sample executed on a synthesized fixture, not that the paper's result was reproduced; each line links to that paper's sample list. Syntology's record for this page last changed ; when this build read Syntology's graph is in the build record. For agents: get_harvested_code_for_paper(arxiv_id) lists each paper's samples; how to connect.
Report a problem or propose a change · a person checks every report against the paper or source before anything changes; decisions are listed on /corrections