SurgeonLog

Who uses it

Built for: General Surgery

Reads

Cases, outcomes, simulator sessions

Writes

Log entries, exports, conversion rates, scope-against-MRI counts, simulator hours

Never

It does not show any surgeon another surgeon’s identifiable figures.

Access

Only people whose role includes it — the clinic owner decides who

Your data

Full PHI. Hosted in Boston, United States. On uninstall: All clinical data stays in the record.

In the product

1. 1Read the line at the top firstThe banner says whether you are looking at your own logbook or, with the supervisor permission, every surgeon’s — read from the permission, not guessed. Writes always go into your own logbook.
2. 2Add the caseAn entry takes the procedure, your role — primary, assistant or supervised — the date, where it was done, and the patient’s age and sex; the patient’s identity is deliberately absent, and a database constraint refuses an entry that names neither one of this hospital’s cases nor the place it was done.
3. 3Record the outcomeAn outcome at thirty days or a year is uneventful, complication, reoperation or death; a complication will not save without its Clavien-Dindo grade, and a grade on anything else is refused.
4. 4Read the numbers with their caveatVolume, complication rate and reoperation rate are computed from these rows, and the server returns the caveat with them — the screen prints it beside the numbers rather than hiding it in a tooltip.
5. 5Log the approach and your practiceOn an entry, log the approach and blood loss; a robotic case adds docking and console minutes, a laparoscopic, robotic or arthroscopic case that converted to open needs its reason, and an arthroscopy adds what the MRI reported, what the scope found and the repair. Approach and practice counts conversions by surgeon and procedure, and adds simulator hours (with any FLS result as reported) beside the OT committee’s own target.