The same topological identity engine that powers robotics and market regime detection —
applied to clinical data. CT, ECG, vitals. Modality-agnostic. Auditable.
Decision-support, not diagnosis.
CLINICAL PIPELINE
The Perception Path
From raw sensor data to decision-support signal in a single deterministic pass. Every number traces to a real test result.
01 — Ingest
Sensor → Validate
CT voxel grid, ECG waveform, or vitals stream ingested via ClinicalDataView. Buffer consistency enforced.
"The clinical engine does not diagnose — it detects structural anomalies in sensor data and converts them into auditable decision-support signals for human clinicians."
THE CLINICAL ENGINE THESIS
PROOF ARTIFACTS
Test Suite Results
Every claim on this page is backed by reproducible test output. Run it yourself.
C++ Test Suite — 10/10 ✅
CT voxel → pointcloud24,076 pts
Modality acceptanceCT=OK, ECG=OK
Full compute14 H₀ features
Regime classificationCritical · 0.59
ECG topology12 beats · 833ms
Fingerprint determinismsim = 1.000
Vitals trajectoryDeteriorating ✓
Cross-modalityCT↔MRI = 1.000
Council consensusIntervene · 100%
Acuity scoringLevel1-Immediate
Python Proof Suite — 6/6 ✅
CT voxel segmentation24,076 tissue pts
ECG topology detection11 beats · 833ms
Vitals regime trajectorydet > stable ✓
Fingerprint deterministic0xE8DE22FC…
Latency gate (imaging)0.4ms < 100ms
Multi-sensor fusionCT+ECG+Vitals ✓
Domains Proven: [ Robotics, Healthcare ]
LIVE OUTPUT
What the Engine Actually Prints
Raw output from a CT scan pipeline run. Every number is deterministic — run it yourself and get the same result.
python proof-artifacts/benchmarks/run_clinical_proof.py — same output every run
STATE OF THE ART
SOTA Comparison: Clinical Decision-Support
How Apex17 Clinical compares to existing approaches for real-time sensor-driven clinical intelligence.
Capability
Rule-Based
Deep Learning
Apex17 Clinical
Latency
Real-time Simple threshold checks
50–500ms GPU inference per scan
4.1ms Full pipeline, CPU-only
Modalities
1 per system Separate alert rules
1–3 per model Retrain per modality
10 modalities Same engine, zero retraining
Auditability
High Simple but structurally blind
Low Black box, hard to govern
Full chain fingerprint → votes → reasoning
Structural Awareness
None Threshold only
Learned features Data-dependent
H₀ Topology Mathematical structure
DATA FLOW
A Different Kind of Clinical Pipeline
Most clinical alerting is threshold-based. Most AI is black-box. This engine sits in between — structural, deterministic, interpretable.
RULE-BASED ALERTING
Threshold → Alert
Sensor→Threshold Check→Alert / Silence
Simple and auditable, but structurally blind. Misses multi-variable patterns, trajectory context, and structural anomalies. High false-alarm rate.
DEEP LEARNING
Sensor → Neural → Prediction
Sensor→CNN / Transformer→Classification
Can find subtle patterns, but less interpretable. Hard to audit. Harder to govern. FDA pathway requires extensive validation infrastructure.
EHR ANALYTICS
Records → Model → Risk Score
EHR Data→Feature Eng.→ML Model→Score
Good for population health, but batch-oriented. Not real-time. Not sensor-native. Doesn't see topology.
APEX17 CLINICAL
Sense → Topology → Council → Signal
Sensor→Validate→H₀ Topology→Clinical Council→Acuity Signal
Real-time structural analysis with full audit trail: fingerprint, council votes, reasoning strings, regime classification. Every output is a decision-support signal, not a diagnosis.
DIFFERENTIATORS
Five Architecture-Level Differences
These are not incremental feature additions. They are structural design choices that change what the system can prove.
01
Modality-Agnostic Topology
The same H₀ persistence engine processes CT point clouds, ECG time series, and vitals trajectories. No modality-specific neural networks required.
This means new sensor types require only a data adapter, not a new model architecture. The validated cross-modality similarity is 1.000 (CT↔MRI).
02
Deterministic Fingerprinting
PathologyFingerprint produces a 64-bit hash from topology features. Same input → same hash, always. Similarity uses std::popcount for portable Hamming distance.
Fingerprint similarity = 1.000 for identical inputs across runs. This enables O(1) recall: "have I seen this structural pattern before?"
03
Modality-Gated Council
Agents only vote when relevant to the input modality. CT input activates ImagingAgent; VitalsAgent and LabsAgent abstain. No "phantom votes" from irrelevant specialists.
Consensus confidence measures agreement among relevant agents, not total agent count. This prevents a 3-agent system from appearing to have 3× confidence on a single-modality input.
04
Auditable Decision Chain
Every decision carries: fingerprint hash → council votes → reasoning strings → regime classification → acuity level. All timestamped, all deterministic.
This is important for regulatory audit trails. The system can prove exactly why it produced a specific signal for a specific input.
05
Decision-Support, Not Diagnosis
The engine explicitly frames outputs as signals for clinician review. "Specialist review recommended" — never "patient has condition X." This is a design choice, not a limitation.
Clinical overreach is an architectural violation. The council uses softened language: "elevated structural anomaly" instead of "biopsy recommended."
HONEST ASSESSMENT
What This Proves. What Production Needs.
This scaffold demonstrates the architecture works. Production healthcare requires significantly more.
What This Scaffold Proves
Modality-agnostic topology works on clinical data
Same math as robotics and markets — one engine
Deterministic fingerprinting enables recall at O(1)
Support-weighted council prevents urgency escalation bias