FAQ
Frequently Asked Questions
What is SpineCRS?
SpineCRS (Spine Complication Risk Score) is a research and educational platform combining a preoperative wound-complication risk-estimation calculator with a standardised classification system for perioperative complications in spine surgery. It is developed at Balgrist University Hospital, University of Zurich.
Is the risk calculator validated?
The calculator is derived from a retrospective cohort of 4,067 consecutive lumbar spine surgeries (2017–2023) at a single academic centre. Seven independent predictors of major wound complications were identified through multivariate logistic regression. External validation is ongoing as the prospective registry accumulates cases.
Can I use the calculator without registering?
Yes. The calculator is freely available for educational use without an account. Registration is required only if you wish to submit cases to the prospective research registry and track outcomes longitudinally.
How are patient data protected?
Patient identifiers (PIDs) are stored in a separate, owner-only table (case_local_refs) with row-level security restricting access to the registering surgeon. The main cases table contains only de-identified clinical data. No demographic or contact information is collected.
Where is the data hosted?
SpineCRS is operated on European infrastructure, with the clinical database and authentication services hosted in a Swiss data centre. The platform is operated in accordance with the revised Swiss Federal Act on Data Protection (revFADP) and the EU General Data Protection Regulation (GDPR). No clinical data leaves this infrastructure except for the limited, surgeon-initiated calls described under the auto-fill questions below.
What security measures protect my data?
All traffic between your browser and the server is encrypted in transit (TLS/HTTPS). The database is encrypted at rest. Access control is enforced server-side via row-level security (RLS): each surgeon can read and write only their own cases and patient identifiers — there is no shared workspace, and surgeons cannot see one another's data. Third-party API keys never reach the browser; they are stored as server-side secrets and only the de-identified payload is forwarded. Authentication uses standard JWT sessions with email verification, and sign-up is gated by institutional email-domain checks where applicable.
How does the automatic Charlson Comorbidity Index (CCI) scoring work?
In Stage 1 of a case you may either fill the Charlson score manually or click Auto-fill. The auto-fill feature accepts a pasted diagnosis list or a photograph of one (for example, a printed problem list) and uses a clinical language model (Anthropic's Claude) to identify which of the 17 Charlson conditions are present. The result is shown as a checklist for you to verify and correct before applying it to the form. Patient age is entered separately and is never inferred by the AI — only you decide which age bracket applies. The final score and the 17 confirmed booleans are saved with the case for auditability.
What happens to the text or photo I send to the auto-fill?
Nothing is stored. Pasted text and uploaded images are forwarded over HTTPS to the language model for a single inference call and are then discarded. The server-side proxy never logs or persists the source material, and no column in the database holds the raw text or image bytes. Only the structured result you confirm — the 17 condition flags, the age points you entered, the chosen method, and a confidence tag — is written to the case record. The verbatim diagnosis list shown to you for verification exists only in the modal and is dropped when you close it.
Can I upload a photo with patient details on it?
No — please don't. Only upload photos that contain the diagnosis list itself and no patient identifiers. Crop, fold, or cover the patient name, date of birth, patient/case number, address, insurance information, and any institutional barcodes or stickers before taking the picture. The auto-fill feature only needs the list of conditions; everything else is unnecessary and should not leave your device. If in doubt, paste the diagnoses as text instead.
Where is the AI processing performed?
The AI inference call goes to Anthropic's API endpoint (api.anthropic.com), which is operated on AWS infrastructure in the United States. This means that any text or photo you submit to the auto-fill feature briefly leaves the EU/Swiss environment for the duration of the call. The request and response are encrypted in transit, Anthropic does not retain API inputs for training, and — as noted above — nothing about the request is stored on SpineCRS servers afterwards. If your institutional data agreement requires that no clinical content leaves European infrastructure, please fill the Charlson score manually rather than using auto-fill.
Why is the blood-loss field empty when I'm logged in?
For prospective cases, the blood-loss field requires the actual measured intraoperative value rather than a population estimate. The automatic per-category estimate (Cat I ≈ 209 mL, Cat II ≈ 403 mL, Cat III ≈ 612 mL) is shown only in the open/educational calculator when no surgeon is signed in.
How do I join the registry?
Use the Create an account link on the sign-in screen. If your institution is already enrolled, sign-up is immediate (subject to email-domain verification). If not, the form lets you submit an enrolment request to the project coordinator.
What is the SpineCRS classification system?
SpineCRS classifies perioperative complications by four axes: surgical complexity (Cat I–III), cause (surgical vs. medical), therapeutic consequence (grades A–E), and neurological deficit. It was developed and validated against cumulative hospital stay in 934 consecutive spine surgery patients (Farshad et al., The Spine Journal, 2020).
Who can I contact?
For clinical enquiries, research collaboration, or technical issues, please contact the author via Balgrist University Hospital, Zurich, or by email at
contact@spinecrs.com. Institutional enrolment requests are routed through the in-app registration flow.
This FAQ will be updated as the platform evolves. Suggestions for additional questions are welcome.