Home / Demonstrations

CLINICAL SOFTWARE / EVIDENCE ENGINEERING · WORKING SOFTWARE DEMONSTRATION

Evidence you can inspect. Uncertainty you can see.

Connect recorded inputs, explanations and source references while keeping missing, conflicting and unlinked evidence distinct.

78 secondsEnglish narration + subtitlesSynthetic data

WHAT YOU CAN VERIFY

Follow a result back to the evidence behind it.

Traceable evidence

Switch between inputs, explanations and source identifiers for the same prepared case.

Explicit uncertainty

Compare a missing record with a recorded zero. Keep conflicting source records visible for review.

Summary to source

Filter the six-case synthetic cohort and inspect the individual case behind its state.

TRY THE WORKING DEMONSTRATION

Inspect it at your own pace.

Explore a visual path, inspect evidence layers, compare missing and conflicting inputs, then trace a cohort summary to a case.

Start the 5-step English guide ↗

Independent synthetic session. Your changes stay in this browser. Do not enter private information.

TRUSTWORTHY AI / ENGINEERING MECHANISMS

Make the foundation inspectable.

Source references, explicit uncertainty, controlled knowledge changes and human review make it possible to examine what supports an output.

NEURO-SYMBOLIC AI / ARCHITECTURE DIRECTION

Learned interpretation + explicit knowledge.

Our architecture direction combines model interpretation with structured knowledge and explicit reasoning. This demonstration shows selected evidence and deterministic workflow mechanisms. The neural integration layer is not connected.

No certification, end-to-end neural-symbolic performance or production effectiveness is claimed. No clinical rules are executed; this is not for clinical use.

A FOCUSED FIRST ENGAGEMENT

Start with one evidence inspection module.

An engineering engagement defines how reviewers inspect inputs, explanations and source references, with visible uncertainty and testable acceptance criteria.

  • Evidence views and source-reference data contracts
  • Distinct missing, conflicting, stale and unlinked states
  • Synthetic acceptance scenarios and a reviewer handoff
Discuss one workflow →
Read the full English transcript

Trace the evidence behind each step

A result should be inspectable. This engineering demo connects a visual path to recorded inputs, explanations and source references.

Separate inputs, explanations and sources

Select an evidence layer. Inspect the recorded inputs, read the explanation, and follow the source identifiers. Each layer stays connected to the same case.

A missing record is not a negative finding

An absent record must not become a negative finding. Here, a missing note remains distinct from a recorded zero. The explanation preserves what is unknown.

Keep unresolved conflicts visible

Conflicting evidence stays visible for review. Inspect the explanation and both source identifiers, rather than silently collapsing different records into one answer.

Move from a summary back to its evidence

Filter the synthetic cohort, then inspect the case behind its state. The table and chart describe the same prepared records.

Explicit evidence, reviewable software

This supports a trustworthy, knowledge-driven architecture. Neural interpretation is a future integration layer. Start with one evidence inspection module. These are prepared states, not a clinical inference run.