Diaco Studio — quick start

One page. If you read nothing else, read this.

What it is

Three tools in one application, sharing one patient record:

Socket studio/appTranstibial socket from a residual-limb scan
Insole studio/insole/Parametric insole pair from measurements or a gait scan
Batch buildconsole :5001/import/A folder of STL pairs into OrcaSlicer projects. Ours, not the clinic's

It is a CAD tool. Every design is approved by the practitioner — the application never decides a wall thickness, and never signs off a fit.

Starting it

Double-click run.bat. Two windows open, and so does a browser.

http://127.0.0.1:5100/the clinic — the public page, and the three studios behind a sign-in
http://127.0.0.1:5001/the owner console — accounts, print profiles, batch build, backup

They are separate on purpose. The console can download the whole database and issue licence codes, so it does not share an address with the application your practitioners use. Leave both windows open; closing one stops that half.

The first ten minutes

Giving a demonstration

Sign in and press Demo in the header. It builds a complete sample case from the scan shipped with the application — about five seconds — and puts a bar at the foot of every screen with a twenty-minute script in it: thirteen steps, the line to say for each, a clock, and Notes for what to do and why a clinic cares.

Next moves the demo along and takes the screen with it, across modules if the step lives in another one. End demo removes the sample patient, its case, its socket and its files — exactly what it created, and nothing else.

The sample case is approved but never charged, so a demonstration cannot spend your credit. Anything you build live during the demo is a real design and is charged normally when you approve it.

A socket, start to finish

An insole pair

Enter size, weight, pathology and side, then Generate insole. Adjust any of the 44 parameters live. Optionally upload a gait scan (ZIP or PAYA) first — it is analysed and not stored; only the derived parameters are kept.

Then, in Patient record: choose the patient, Save to patient, Approve pair (charges once), Send to printer.

Where the files go

Finished work lands in the print queue — see it under Batch build → Print queue, which also tells you the folder. Point that folder at your print farm's watch directory in the batch-build settings if you have one.

Backups

The owner panel has Download backup. Take one before any upgrade, and keep it somewhere that is not this computer. It contains patient data — treat it like the paper records.

When something is wrong

Full workflow guide: docs/clinical-workflow.md. Troubleshooting: docs/troubleshooting.md.