CDSS subgroup project

Thank you everyone for the contributions.

I am currently working on mapping the SANS-related variables identified from the relevant literature shared by everyone to available datasets. I am also going through different datasets to understand what variables and data types are available and what kinds of AI/ML models we could potentially build using them, particularly in the context of the SANS-CDSS.

This will help us connect the literature-derived variables with actual data sources and inform the development of the minimum clinical dataset and subsequent synthetic longitudinal astronaut profiles.

If anyone would like to contribute to this work, please feel free to reach out and contribute to the dataset and variable-mapping process.

Link: CDSS Data Sources - Google Docs

Best,
Ritika

3 Likes

CDSS Group Meeting Summary — 25 September 2026

Thank you everyone for another thoughtful discussion. This meeting helped us narrow the direction of the CDSS subgroup and connect several pieces of work that have been developing in parallel over the past few months.

Main direction: SANS as the first CDSS use case

We agreed that Spaceflight-Associated Neuro-ocular Syndrome (SANS) should remain the first focused clinical use case for the CDSS.

One important point raised by Ritika was that we already have a considerable amount of work spread across different places: literature reviews, datasets, prototypes, UI/UX ideas, engineering work, governance discussions, and earlier meeting outputs. Before adding more layers, it would be useful to bring these together into one reference document so everyone can see clearly what has already been done, what is still missing, and where each person can contribute.

Dr. Chintan Dave also emphasized something fundamental: before choosing a model, dataset, or technical architecture, we need to define the exact clinical and research question.

This led to an important distinction in the discussion. An AI model may predict or classify a condition, but a CDSS should do more than diagnosis. It should bring together clinical evidence, guidelines, sequential information, uncertainty, and practical next steps to help a medical officer decide what to do.

For SANS, this could mean supporting questions such as whether a finding is concerning, whether it is progressing, what additional test is needed, how urgently action is required, and when expert or Crew Medical Officer involvement is necessary.

The system should also be designed around the actual constraints of spaceflight: limited computing resources, intermittent connectivity, delayed access to specialists, and the need for at least partially autonomous clinical decision-making.

We also discussed reviewing existing Earth-based CDSS platforms and open-source clinical systems rather than rebuilding every component from the beginning.

SANS biomarkers and clinical interpretation

Farnaz presented the outline of her review on AI-based detection of ocular biomechanical alterations in SANS.

The discussion covered several potential imaging and physiological biomarkers, including OCT-derived measures such as optic disc edema and retinal nerve fiber layer changes, fundus and retinal vascular imaging, OCT angiography, orbital ultrasound, and MRI.

A useful clarification from Dr. Chintan was the need to keep three concepts separate:

Symptoms are what the astronaut reports.
Signs are objective findings identified through examination or imaging.
Digital biomarkers are measurable quantitative features that can potentially be used for detection, monitoring, or prediction.

This distinction is particularly important in SANS because objective ocular changes may appear before an astronaut reports noticeable symptoms.

The group also discussed reversibility. Some effects related to fluid redistribution may improve after return to Earth, while structural abnormalities such as choroidal folds may persist for longer periods. The review should therefore look not only at detection, but also at which findings are reversible, which may persist, and what their possible long-term significance is.

Patient-reported symptoms should still be included in the CDSS, but they need to be interpreted alongside objective measurements and individual variability. The group also discussed the possibility that symptoms may sometimes be underreported because astronauts could be concerned about the implications for future flight eligibility.

Tabular foundation models and digital-twin work

Jian introduced tabular foundation models, particularly TabPFN 3.5, and discussed how they might contribute to several parts of the project.

Potential uses include classification, prediction, missing-data imputation, causal analysis, and synthetic-data generation. One attractive feature is that these models may allow several different analytical tasks to be approached within a common framework rather than developing an entirely separate pipeline for every task.

The proposed first experiment is intentionally simple: test TabPFN on an OSDR tabular dataset, such as OSD-255, and understand its practical strengths and limitations before considering more complex clinical applications.

There was also discussion about how these models might eventually contribute to a digital-twin framework, particularly if local or edge inference becomes feasible with relatively small datasets and limited computing resources.

Atul raised an important limitation: a model trained largely on Earth-based data may not adequately represent biological responses under microgravity, radiation, and other space-specific conditions.

Jian therefore proposed exploring a complementary approach in which foundation models are combined with methods such as conditional variational autoencoders (cVAE) and explicit spaceflight-related conditioning variables. This could provide a way to incorporate space-specific context rather than assuming that terrestrial relationships transfer directly to space.

Where we are heading

The discussion is gradually bringing several parts of the subgroup into one common framework:

Clinical question → SANS variables and biomarkers → astronaut longitudinal data → synthetic/real data integration → AI and probabilistic models → CDSS logic → clinically meaningful recommendations

The important point is that we are not trying to build an AI model simply because a model is available. The goal remains to develop a system that can eventually support real clinical reasoning under the unusual constraints of spaceflight.

Next steps

Ritika will prepare a forum update asking the group for input on the research question, project direction, and development tasks, and will also coordinate with Alireza on application development and the addition of Adolfo Viguera to the engineering team.

The subgroup will begin consolidating the existing literature, datasets, prototypes, UI/UX work, and governance material into a common reference resource. We will also review existing terrestrial CDSS systems and open-source clinical guidelines to identify components that may be reusable.

Farnaz will continue refining the SANS biomarker review, particularly the distinction between signs, symptoms, and digital biomarkers, as well as the evidence regarding reversibility and longer-term structural effects.

Jian will share the digital-twin presentation, datasets, notebooks, and relevant Google Drive/GitHub resources, and will organize a practical coding session for TabPFN 3.5. Group members can then test it on a simple OSDR tabular dataset and bring their findings to the next meeting.

Max and the existing VAE contributors will continue developing the conditional VAE and related digital-twin work.

4 Likes

This I interesting, I would love to get involved

3 Likes

Quick progress update on the explainability piece I mentioned. I’ve finished the first pass comparing how rule-based, Bayesian, LLM/RAG and hybrid approaches show the evidence behind a recommendation (table below). Next I’ll turn it into a short subsection and map each approach to the SANS decision questions from the 25 Sept summary (is it concerning, is it progressing, what test next, how urgent, when to involve the CMO), so it can go into the consolidated reference doc and link with Ayse’s governance section. Happy to take feedback on the table first.

Approach How it shows its evidence Main weakness Suggested fit for SANS CDSS
Rule-based Names the exact rule that fired Rigid, can’t express uncertainty Clear thresholds and escalation rules
Bayesian Shows how probabilities shift as findings are entered Hard for non-experts to read Uncertainty and progression over time
LLM/RAG Cites retrieved sources plus generated text Can hallucinate, weak source traceability Interface only, risky as the decision maker
Hybrid Rules and retrieved evidence both visible, or the LLM only presents a validated model’s output More complex to build and validate Best fit for offline, mission-critical use

The last column is my suggested fit, so expect the group to push back on it.

3 Likes

Following the meeting summary, my explainability work (rule-based/Bayesian/LLM-RAG/hybrid evidence-reporting, shared earlier) maps directly onto the “AI and probabilistic models → CDSS logic” step in the framework Ritika outlined. Since the group’s now consolidating everything into one reference resource, happy to write this up as a subsection there rather than leave it as a standalone post, specifically covering how each approach type would report its evidence for a SANS recommendation (concerning/not, progressing/stable, next-step needed), tying into both Ayse’s AI Governance proposal and Dr. Dave’s point about defining the clinical question before the architecture.

Also interested in contributing to Ritika’s dataset/variable-mapping work if useful, my background’s in dataset engineering and leakage/validation QA, which could help on the “connect literature-derived variables to actual data sources” side specifically.

3 Likes

Here is a link to a paper discussing the species/unobserved conditions translation/prediction methods I proposed in the call today: scGen predicts single-cell perturbation responses | Nature Methods

3 Likes

My name is Sherlyn, and I recently joined the AI/ML AWG. I’m currently a second-year college student from California with a strong interest in data science and AI.

I’m really interested in your subgroup and would love to learn more about the project! I’m still new to a lot, but I’m happy to contribute wherever I can.

I was wondering when your meetings are held and if it would be possible for me to attend an upcoming meeting to learn more about the project?

Thank you!

2 Likes

Proposal for the SANS decision support design: an evidence trace attached to every recommendation.

For each decision question from the 25 Sept summary (concerning? progressing? next test? how urgent? escalate to the CMO?), the answer carries a trace with:

  1. Question and answer: which question, and the recommendation.
  2. Inputs: each variable with value, unit, date and data source, so Ritika’s variable mapping plugs in directly.
  3. Logic: the rule IDs that fired, or the model name and version with the top feature attributions.
  4. Evidence: citations with the exact passage used for any literature backed statement.
  5. Uncertainty and missing data: the confidence, and which inputs were missing.
  6. Escalation: the threshold that triggered it and who reviews it.

Design rule: the LLM only writes the narrative from this trace and never makes the decision. This is the hybrid pattern from my comparison.

Three checks we could use: (a) citation faithfulness, meaning the cited passage supports the claim; (b) trace coverage, meaning every statement maps to an input or a source; (c) abstention when key inputs are missing.

If the group wants, I can turn this into a one page template mapped to the five questions.

3 Likes

Hi everyone, I’m Abe, a second-year medical student at the University of Louisville with a background in biomedical engineering and physiology. I’ve been following this thread and I’m really interested in contributing, especially around the SANS use case. I’d love to join the TabPFN session on OSD-255 (is there a date set yet?) to start building hands-on ML experience, and I’d also be glad to help with the clinical framing side, like the concerning-versus-progressing distinction and CMO escalation logic Dr. Dave raised.

Thanks!

4 Likes

Hi @amnidhiry @Sherlyn.zxq

Please send me or @Ritika_Saha your email so we can put you in email list , also please check meeting summaries for last updates .

1 Like

Hi @lauren.sanders,

I’m Naima, a recently graduated AI Engineer (Python, LLM/RAG, agentic systems), and I recently joined the AI/ML AWG. I read the CDSS subgroup description and I’m interested in contributing.

Is there still room to join? I would be glad to start with something small and well defined, for example around the LunarAgent codebase or the synthetic data with built-in anomalies. Please tell me where help is most needed.

Thank you,
Naima