SpinePlanner Pro | NeuraCube

Patient information

Age

Sex

BMI (optional)

Prior spine surgery

Primary complaint

Symptom duration

Comorbidities

Imaging

Modality

Side

Levels

DICOM files

Upload .dcm files to open them in the vendored OHIF viewer (DICOM JSON flow). Study/Series UIDs are also read for your records. Optional: external DICOMweb + manual UIDs if you set NEXT_PUBLIC_OHIF_VIEWER_URL to another OHIF host.

Baseline scores

VAS back (4)

VAS leg (6)

OHIF imaging

How viewing works

SpinePlanner ships a vendored OHIF build under /ohif (run npm run vendor:ohif after cloning). Uploaded .dcm files are sent once to this app’s /api/ohif-dicom/session route, which builds a DICOM JSON manifest so OHIF can load slices via dicomweb: URLs—no Orthanc required for that path.

Sessions are in-memory on the Node server (about 1 hour TTL). After a server restart, use Refresh UIDs from .dcm on the case page to re-upload. For a remote OHIF + PACS instead, set NEXT_PUBLIC_OHIF_VIEWER_URL and use Study/Series UIDs only.