SVF SVF Clinical Platform — paid clinical bundle, two capsules free in the browser Open the live demo
All capsules
SHIVA OS/Capsules/Sagittal Load Corridor
Product package Geometry-driven MIT

Sagittal Load Corridor

The mechanical envelope. Given a patient's pelvic incidence, lumbar lordosis, and thoracic kyphosis, the corridor computes the deterministic relationship between any candidate ΔLL correction and the resulting ΔSVA — plus the age-adjusted PI–LL band the patient should land inside, and the SVA target they should land near. Drawn from the patient's geometry, not from a stock atlas. Pairs with SPIN-THA upstream and the Spine Toolkit umbrella.

Inputs
PI · PT · SS · LL · TK · SVA · age · height
Outputs
PI–LL band · SVA target · ΔLL→ΔSVA curve · ΔSLL deltas
Style
SVG overlay generated from inputs · no stock illustration
Companion
DeltaLL / DeltaSVA Product Bundle v2
01 — What the corridor shows

A patient-specific
envelope, not a chart.

Where the patient currently sits in the corridor, where the age-adjusted ideal band sits, and what ΔLL correction would land them on the SVA target — each on the same axes, scaled to the patient's own geometry.

01

Age-adjusted PI–LL band

Lafage-style band scaled to the patient's age. The patient's measured LL is plotted against it — inside, edge, or outside.

02

SVA target zone

The acceptable SVA range for this patient's age and PI, drawn as a band rather than a single line.

03

ΔLL → ΔSVA curve

For each candidate correction in lumbar lordosis (in 1° steps), the predicted resulting SVA is plotted. Surgeons read off the wedge that lands them in the SVA target.

04

ΔSLL (segmental LL)

The same correction is decomposed into segmental LL changes — what each level contributes to the total ΔLL — so the planner sees where the work has to happen.

02 — ΔLL → ΔSVA, computed

Geometry,
not regression.

The relationship is computed from a rigid-body model of the lumbar spine + pelvis + thoracic chain — not from a population regression fit. The Delta Product Bundle contains the closed-form derivation and the unit tests.

// Example output — Sagittal Load Corridor v2 { "patient": { "PI": 54.2, "LL": 38.0, "TK": 42.0, "SVA": 78, "age": 62 }, "band": { "PI_LL_min": 5, "PI_LL_max": 15, "PI_LL_measured": 16.2, "verdict": "just_above" }, "SVA_target": { "min": 20, "max": 45, "measured": 78, "verdict": "out_of_band" }, "deltaLL_to_target": 12, "deltaSLL_breakdown": { "L4_L5": 5, "L3_L4": 4, "L2_L3": 3 } }
Naming note
Not the same as a "Sagittal Atlas".

An atlas is a population reference. A corridor is a per-patient mechanical envelope. Use the corridor when you want geometry-driven targets; use a population atlas (e.g. Roussouly types) when you want phenotype matching. The Spine Toolkit umbrella ships both, with the corridor as the deterministic anchor.

Using this in a clinic?

The MIT code is free. A clinical site license covers deployment support, integration help, hash-verified releases, and indemnification language. See commercial offerings →

Get a quote