Cases are named, not identified.
A case in SurgiReport is “21 Aug · OP #3 · TLIF L4/5”. The date, its position in your operating list, the procedure. The link between that and a patient exists only in your hospital system and in your head.
Built by a consultant spine surgeon practicing in Germany — fellowship-trained in orthopedics and trauma surgery
Stop rewriting last week's op note.
You already have the templates. SurgiReport takes yours, plus the few things that were different today, and writes the finished operative report — your structure, your phrasing, your language. You review it and paste it into your hospital system.
In development · joining now decides what gets built first
Nothing to installNo hospital integrationNo patient data
Worked example
One template. Three lines. A finished report.
A lumbar decompression and fusion. The surgeon's own template on the left, what was different today in the middle. Everything highlighted on the right was changed or added — nothing else moved, and nothing was invented.
Template language
Your templateTLIF L5/S1 — standard
Indication
Degenerative spondylolisthesis L5/S1 with neuroforaminal stenosis and radiculopathy, refractory to conservative treatment for more than six months.
Positioning
Prone on the Wilson frame. All pressure points padded. Single-shot antibiotic prophylaxis given prior to incision.
Approach
Midline incision over L5/S1. Subperiosteal dissection of the paraspinal musculature, exposing the laminae and facet joints bilaterally.
Decompression
Laminectomy L5 with undercutting of the inferior facets. The dura was carefully mobilised medially; no dural injury occurred.
Interbody fusion
Complete discectomy L5/S1. Endplate preparation with curettes and rasps. A 10 mm PEEK cage filled with autologous bone was inserted from the left.
Instrumentation
Pedicle screws L5 and S1 bilaterally under fluoroscopic control. Correct position confirmed in two planes.
Closure
Haemostasis. A drain was inserted. Layered closure of fascia and subcutis, skin closed intracutaneously.
Saved template · used 34 times
What was different today
Level was L4/5, not L5/S1.
Small dural tear in the left lateral recess — oversewn and covered with a patch, no leak at the end.
Cage was 12 mm, inserted from the right.
Dictated in theatre
Your report21 Aug 2026 · OP #3 · TLIF L4/5
Operative report
Indication
Degenerative spondylolisthesis L4/5 with neuroforaminal stenosis and radiculopathy, refractory to conservative treatment for more than six months.
Positioning
Prone on the Wilson frame. All pressure points padded. Single-shot antibiotic prophylaxis given prior to incision.
Approach
Midline incision over L4/5. Subperiosteal dissection of the paraspinal musculature, exposing the laminae and facet joints bilaterally.
Decompression
Laminectomy L4 with undercutting of the inferior facets. The dura was carefully mobilised medially. A small dural tear occurred in the left lateral recess; this was closed with a running suture and covered with a dural patch. No cerebrospinal fluid leak was demonstrable at the end of the procedure.
Interbody fusion
Complete discectomy L4/5. Endplate preparation with curettes and rasps. A 12 mm PEEK cage filled with autologous bone was inserted from the right.
Instrumentation
Pedicle screws L4 and L5 bilaterally under fluoroscopic control. Correct position confirmed in two planes.
Closure
Haemostasis. A drain was inserted. Layered closure of fascia and subcutis, skin closed intracutaneously.
Left for you
You did not mention a postoperative regimen after the dural repair — bed rest, drain management, follow-up. Nothing has been assumed on your behalf.
3 findings applied8 passages rewritten0 facts invented1 point left for you
Why this matters
The template said “no dural injury occurred”. That sentence is gone, because today it would have been false.
Illustrative example. No real patient, no real case.
The problem
The template shuffle
Find a similar case from last month. Copy the report. Hunt through it for the level, the side, the implant size. Change what was different today — and hope you caught every instance of it. Ask a colleague for their version of a procedure you only do twice a year. Hand it to a secretary who wasn't in theatre and doesn't know what you found.
It works. It has always worked. It also costs you fifteen to thirty minutes after every case, and every find-and-replace you miss becomes a documentation error with your signature under it.
You do it after every single case.
Multiplied across a week of operating, it is most of a working afternoon.
It is the same work every time.
Ninety percent of the report is identical to the last one. Only a handful of facts changed.
Nobody trained you for it.
It is the one part of the operation you were left to figure out on your own.
How it works
Three steps, and the third one is just reading.
Add your templates — once.
Paste in the reports you already reuse. SurgiReport reads the steps, their order, and the way you write them, then asks how you would normally refer to that procedure in your own words. That is the entire setup.
Your own reports. Your own wording. Nothing standardised away.
Say what was different.
Type it or dictate it — the level, the side, an unexpected finding, an implant that changed. Two sentences is often enough. Select more than one template when the case combined procedures.
Combined case? Take the decompression from one template and the fusion from another.
Review and paste.
The finished report arrives with every change highlighted, so you check the deltas instead of rereading the whole document. Correct anything you want, copy it into your hospital system, sign it. The content is yours.
Anything you did not mention is flagged, never filled in with a plausible guess.
Privacy by design
Patient identity never enters SurgiReport.
Not because we promise to delete it. Because there is nowhere in the product for it to go. This is the design SurgiReport is being built to; none of it has shipped yet.
PHI Guard checks every input.
Before anything is processed, SurgiReport scans what you paste or dictate for names, dates of birth and case numbers, shows you what it found, and waits for you. We do not claim to catch everything — which is exactly why you see the result and decide, rather than trusting a promise.
Your reports are not training data.
SurgiReport is being built on EU infrastructure, and your templates and reports will never be used to train AI models — not ours, not anyone else's. Where a supplier has to process something outside the EU, it is named in the privacy policy.
This page uses no cookies.
No tracking pixels, no advertising scripts, no consent banner to dismiss. We count anonymous totals — pages viewed, buttons pressed, signups completed — with nothing attached that could identify who did any of it.
What it does
Built for the way surgeons actually document.
Everything here describes the product being built. Nothing has shipped yet — the items marked “planned” come after the others.
Your voice, not a house style
The report comes back in your sentence structure, your terminology, your level of detail. It reads like the ones you have already signed, because it learned from exactly those.
Your template's language
German template in, German report out. French, Spanish, Turkish, Arabic — the report always follows the language of the template, whatever language the interface is in and however you dictate.
Combined procedures, combined templates
Select the decompression from one template and the fusion from another. SurgiReport merges them into a single coherent report in one consistent voice.
Nothing is invented
The design goal every other decision answers to: each sentence traces to your template or to what you said about this case, and anything you left out is flagged rather than quietly filled in. It is also why you review and sign the report, not us.
Delivered where you read it
PlannedHave the finished report sent to the address you actually open at work, so it is waiting for you when you sit down at the hospital PC.
Dictate from your phone
PlannedWalk out of theatre, say what was different, and find the report waiting. Tell us on the waitlist how you would want this to reach you.
The waitlist
Join as a founding member.
SurgiReport is in development. The waitlist is not a mailing list — it decides what gets built first, in what order, and at what price.
Early access
Founding members get in before public launch, while the roadmap is still soft enough to change.
Founding price, locked
The lowest price SurgiReport ever offers, kept for as long as you stay a member.
Actual influence
The optional second part of the form is where you tell us what to build. It is read, not aggregated into a dashboard.
One email to confirm you are real, one to say you are in. Then nothing until there is something worth showing you.
Questions
The things surgeons ask first.
Does my hospital's IT department need to be involved?
No. SurgiReport does not connect to your hospital system, your PACS, or anything else. It runs in a browser, you copy the finished report out, and nothing is installed on hospital hardware. That is a deliberate design decision, not a limitation we intend to remove.
What about patient data?
It does not belong in SurgiReport, and the product is built so that you never need it there. Cases are identified by date, position in your operating list, and procedure. PHI Guard checks every input for names, birthdates and case numbers before processing and asks you to remove what it finds.
Who is responsible for the report?
You are — exactly as you are today when you edit a colleague's template. SurgiReport produces a draft. You review it, correct it, and sign it. It does not practise medicine, and it does not check your documentation for correctness or completeness.
How is this different from dictation software?
Dictation transcribes what you say. SurgiReport writes what you do not say: the ninety percent of the report that is identical every time you perform this operation, in your own wording, with today's differences placed where they belong.
Which languages does it write in?
Whatever language your template is written in. The interface is English at launch, with more interface languages on the roadmap — but the report itself always follows the template, not the interface and not the language you dictated in.
When does it launch, and what will it cost?
Launch follows the waitlist: we are building for the surgeons on it, in the order they tell us to. Pricing will be set from what waitlist members tell us is fair, and founding members keep the lowest price we ever offer.
Your next operative report is already ninety percent written.
It is sitting in a document you wrote months ago. Join the waitlist and we will tell you when SurgiReport can finish it for you.