Virelion
Tools Talk to us

HeartTwin

Orchestration layer for the cardiac research software stack.

Scientific deep dive. Mechanistic electrophysiology, mechanics, patient-specific calibration, uncertainty, and validation are documented separately. Open scientific detail →
HeartTwin architecture: domain engines into cardiac state engine into digital heart twin
Researchers reviewing digital cardiac models and electrophysiology traces on multiple monitors

What it is

HeartTwin does not re-implement specialist algorithms. It discovers registered services, exchanges typed state objects, and composes research workflows. A native CardiSim digital-twin backend (CDT-compatible) is in place for geometry-aware propagation and pseudo-ECG observation during software integration.

What it is not

Not a clinical twin. Not a diagnostic or treatment tool. Not software as a medical device. Service registration is not scientific validation.

1
Orchestration core
15+
Registered services
CDT
Native twin backend
AGPL
Open source
HeartTwin schematic with anatomy, electrophysiology, mechanics, flow, inference and therapy modules feeding typed state visualizations

Stack around HeartTwin

Measure: ElectroTrace, MyoTrace, OptiCell, CardioScore. Simulate & design: CardiSim, CardiStudio. Challenge: DCCP, CardiVex, CardiAgent. Evaluate: CardiBench, CardiEval. Evidence: CardiAtlas. Glue: CardiBridge, CardiTrace.

Browse tools → GitHub → Dossier →

Status

Active development. Discovery-stage framing is retired for this program. Adapters for many services are still registered without full wiring; the roadmap prioritizes native adapters, multimodal state, and independent evaluation gates.

Open repository → Back to pipeline

New stack layers (Oct 2026)

Tools catalog →