Team
One logs. The team confirms.
A logbook is a record of the same operation written by everyone who was there, separately, from memory. Opus lets one person write it once, with photos, and lets the others confirm it from their own phone.
Three people in theatre, one phone out. The registrar logs the case and tags the two colleagues with the role each played.
RegistrarSurgeon
RegistrarFirst assistant
ConsultantSupervisor
What this gives you One case typed, by one person, once.
Scenes advance on their own; choose one to stop.
Why confirmation matters
A training logbook is self-reported, and it decides progression. The UK literature says what that costs:
- 906 UK surgical trainees answered. 68.5% believed overstatement or misrepresentation of case involvement occurs; 20.8% had witnessed trainees logging cases they had not taken part in; 85.2% had few or no eLogbook entries validated. Beamish AJ, Johnston MJ, Harries RL, Mohan H, Fitzgerald JEF, Humm G, Rabie M, Nally DM, Gokani VJ; Council of the Association of Surgeons in Training. Use of the eLogbook in surgical training in the United Kingdom: a nationwide survey and consensus recommendations from the Association of Surgeons in Training. Int J Surg. 2020;84:199–206. doi:10.1016/j.ijsu.2020.02.045
- Of 13,755 operations entered by trainees in one UK region, 12.5% needed correction or exclusion before the data could be analysed. Achuthan R, Grover K, MacFie J. A critical evaluation of the electronic surgical logbook. BMC Med Educ. 2006;6:15. doi:10.1186/1472-6920-6-15
Opus does not police a logbook. It gives each entry a second signature from someone who was in the room: a colleague's confirmation of involvement, and for the fields a board reads, a senior colleague's attestation of the role and the level of supervision, procedure by procedure. The attestation is stored without patient detail, so the owner can read it on any of their devices, and it is written into the RACS MALT report beside the level the trainee claimed.
What it is today, exactly
- Who confirms. Any tagged colleague on Opus can verify or dispute the case. Only a colleague senior to the logger can attest the role and supervision, and a correction is shown beside what was recorded, not treated as a dispute.
- What travels. The case itself is end-to-end encrypted to the tagged colleagues' devices, patient identity included. Verification status and the attested grades are plain, patient-free records. A dispute note is sealed to the owner's devices.
- Whose logbook. The case sits in the logbook of the person who logged it, and their report exports carry who confirmed and attested it. The colleagues hold the shared copy, confirm it, and are assessed on it; their own report exports list the cases they logged themselves.
Where the data sits at each step: where your data lives. The mechanism, file by file: security and privacy.