Algo-Model

MetaboGuard Prevention Model Specification

Clinical purpose

MetaboGuard is a research system for preventive monitoring. It identifies unusual metabolic profiles and produces reusable patient representations for future longitudinal validation.

It is not a diagnostic system. A warning means “this profile differs from the reference and may warrant clinician review,” not “this patient has or will develop cancer/diabetes.”

MetaboGuard self-supervised architecture

Intended users

No autonomous patient-facing alerts are permitted in the current version.

Model layers

Layer 1: self-supervised encoder

Input:

Training:

Output:

Layer 2: anomaly/deviation warning

The warning score combines:

Reference percentiles are empirical percentiles from the training cohort.

Suggested research-only bands:

Percentile Label Interpretation
<90 Within reference range No model warning; not evidence disease is absent
90-95 Mild deviation Consider data quality and routine review
95-99 Elevated deviation Clinician-reviewed follow-up research
≥99 High deviation Strongly unusual profile; still not diagnostic

These bands are not clinically validated thresholds.

Layer 3: post-hoc association heads

Labels are introduced only after encoder training to assess representation content.

Current heads:

No current head is a future-development model because NHANES lacks patient-level longitudinal outcomes.

Layer 4: future longitudinal risk heads

When longitudinal data are available:

  1. choose prediction times before diagnosis;
  2. censor all post-index measurements;
  3. evaluate 1-, 3- and 5-year horizons;
  4. enable a horizon only with at least 50 events and 50 eligible non-events;
  5. validate by site and calendar period;
  6. calibrate probabilities separately for each horizon.

The user-selected “custom horizon based on available data” is implemented as event-count-based horizon eligibility rather than a fixed universal window.

Dataset governance

Prevention feature allowlist

Only measurements plausibly available before diagnosis are allowed.

Denylist

Prohibited:

Dataset capability states

State Allowed outputs
Cross-sectional only representation, deviation score, association checks
Repeated measurements without outcomes trajectory embeddings, no disease risk
Longitudinal with incident outcomes eligible multi-horizon risk heads
Post-diagnosis cancer cohort prognosis/context research only

Cancer scope

The cancer head is pan-cancer by default. Cancer-site-specific heads require enough incident cases at the selected horizon. Sites are not pooled blindly if their biology, screening pathways or treatment histories materially differ.

TCGA can inform cancer heterogeneity and prognosis, but it cannot validate pre-diagnosis metabolic warnings.

Diabetes scope

Type 2

Metabolic early-warning research is feasible with glucose, HbA1c, insulin, adiposity, lipids and longitudinal outcomes.

Type 1

Current output is research-only. Patient-facing Type 1 warnings require:

The current proxy must not be described as Type 1 diagnosis or development risk.

Evaluation

Representation:

Deviation score:

Risk heads:

Current evidence status

The current MetaboGuard-SSL artifact demonstrates technical feasibility:

Cross-sectional association checks must not be interpreted as future development performance.

Future-risk layer (simulation only)

A future-risk layer exists in code and is disabled for real patients. It is documented in docs/FUTURE_RISK_PROTOCOL.md (endpoints, splits, gates), docs/LONGITUDINAL_SCHEMA.md (data contract) and docs/FUTURE_RISK_EVALUATION.md (metrics and controls).

No synthetic metric from this layer is evidence of clinical performance, calibration transfer or early detection.

A future-risk layer exists in code and is disabled for real patients. It is documented in docs/FUTURE_RISK_PROTOCOL.md (endpoints, splits, gates), docs/LONGITUDINAL_SCHEMA.md (data contract) and docs/FUTURE_RISK_EVALUATION.md (metrics and controls).

No synthetic metric from this layer is evidence of clinical performance, calibration transfer or early detection.

A future-risk layer exists in code and is disabled for real patients. It is documented in docs/FUTURE_RISK_PROTOCOL.md (endpoints, splits, gates), docs/LONGITUDINAL_SCHEMA.md (data contract) and docs/FUTURE_RISK_EVALUATION.md (metrics and controls).

No synthetic metric from this layer is evidence of clinical performance, calibration transfer or early detection.

Release policy

An artifact may be shared for representation benchmarking if its model card states that it is non-diagnostic and cross-sectional.

A disease-risk artifact may not be published until: