Operative Note Automation
Vetro drafts operative notes from what actually happened in the operating room. Stages, timings, and key events are captured as the case unfolds, then assembled into a draft the clinician reviews, edits, and signs. Nothing enters the patient record without clinician approval, and the draft reflects observed events rather than end-of-day recall.
Operative note automation is one workflow on a broader platform. Vetro is a 3D-native, context-aware operating-room intelligence platform, designed as an extra pair of hands for perioperative teams. The same spatial understanding that supports documentation also supports case coordination, instrument context, voice communication, and native integration with the hospital systems teams already use.
Why operative note documentation costs clinician time and revenue
Operative notes are usually written after the case, sometimes at the end of a long day, from memory. Clinicians spend nearly two hours on documentation and administrative work for every hour of direct patient care, and the same event is often recorded in two different systems. The result is late finishes, inconsistent timestamps, and billing built on reconstruction rather than observation.
Documentation quality also has a direct financial effect. The operative note is the evidence base for procedure coding, so detail that was never recorded can leave a case coded below the work performed, and that revenue is usually lost without anyone noticing. In one NHS audit of knee arthroscopy, half of cases carried an incorrect clinical code before a structured operative note was introduced, and 5% did afterwards. Coding that the note cannot support carries the opposite risk: audit exposure. When a payer challenges a claim, the note is the primary evidence available to defend it, so documentation reconstructed from memory is harder to substantiate and appeals take more staff time to resolve.
That cost is spread across several roles. Surgeons complete charting after the list has finished, perioperative leaders plan from timestamps that were entered from memory rather than observed, revenue cycle teams work from notes that may not support the codes submitted, and CMIOs own the documentation quality that results.
How operative note automation works
Operative note automation runs as four steps across the case. Nothing in the sequence asks the clinical team to stop and enter data, and the clinician remains the author of record throughout.
- Capture. Vetro observes the case as it happens and records structured events with timestamps: patient arrival, induction, incision, key milestones, closure.
- Draft. At case close, those events are assembled into a draft operative note, built from what was observed rather than what was remembered.
- Review and sign. The clinician reviews, edits, and signs. The clinician is always the author of record, and every change is auditable.
- File. The signed note flows into the existing EHR workflow, including Epic and Cerner. No duplicate entry.
A draft is only as good as the observation behind it. Overlapping coverage keeps events visible when any single view is blocked, visual context is captured alongside position, and continuity is maintained across the whole case rather than isolated moments. Where an event is uncertain, it is flagged for review rather than recorded as fact.
What changes for surgical and perioperative teams
Operative note automation changes where documentation work happens rather than who is accountable for it. The draft arrives built from observed events, and each role picks up from a more complete starting point.
- Surgeons: The note is waiting as a draft rather than waiting on the surgeon. Review happens in minutes, and charting after the list is shorter.
- Nursing and coordination staff: Intraoperative timestamps are captured as the case runs, so recording them is no longer a mid-case typing task.
- Revenue cycle: Notes grounded in observed events give coders more of the detail they need, which supports accurate coding and gives a clearer evidence trail when a claim is questioned.
- Quality and safety teams: Case timelines are consistent across cases and built from observation rather than reconstruction, which makes them usable for review and audit.
These changes connect. A note that is accurate on the day of surgery supports coding built on the same evidence, and the case timeline behind it feeds the operational picture perioperative leaders already work from. Operative note automation runs as one workflow on the platform rather than another system to maintain alongside it.
How Vetro handles privacy and clinician control
Vetro is designed so that understanding the surgical process never means monitoring the people carrying it out. The principles below describe how privacy, retention, and clinician control work in practice.
- Vetro drafts; clinicians author. No note enters the patient record without clinician review and sign-off, and every draft and edit is auditable.
- Vetro tracks the process, not people. It is designed to understand surgical workflow and operational events. Vetro does not track individual performance metrics of any sort, and no one is scored, ranked, or compared. The same protections apply to everyone in the room regardless of role.
- Identifiable video is never stored. Recognizable detail is removed automatically as the case is observed, and the original footage is deleted immediately, with no way to recover it. What remains cannot be traced back to any individual.
- Short retention by default. A small amount of data, the segments around logged event timestamps, is kept fully anonymized to improve the models. Everything else is deleted on the schedule agreed with the hospital, seven days by default.
- No surgical video to disclose. Because identifiable footage is not retained, there is no surgical video available for disclosure in patient safety investigations or legal proceedings.
- Audio is optional. Where a hospital chooses to enable it, voice capture is triggered by a wake word rather than recorded continuously, and it is not required for Vetro to run.
- Vetro does not make clinical judgments. Drafts cover observed events, stages, and timings. Vetro does not describe clinical technique it cannot observe, and established clinical safety processes remain with the hospital team.
Each of these is confirmed with the hospital during activation rather than assumed. Vetro is designed to give perioperative teams a more complete record of the case without changing who holds clinical responsibility or how the room is run.
Frequently asked questions about operative note automation
Who is the author of record?
The clinician. Vetro produces a draft; the surgeon reviews, edits, and signs. No note enters the patient record without that sign-off.
What if the draft is wrong?
The clinician corrects it before signing, exactly as with any draft. Events carry confidence levels, and uncertain events are flagged for review rather than recorded as fact.
Does Vetro measure individual staff performance?
No. Vetro does not track individual performance metrics of any sort. No one is scored, ranked, or compared, and the same protections apply to everyone in the room regardless of role.
Where does the data live?
On servers inside the hospital. Recognizable detail is removed automatically as the case is observed, and the original footage is deleted immediately rather than being sent anywhere.
How long is data kept?
A small amount of data, the segments around logged event timestamps, is kept fully anonymized to improve the models. Everything else is deleted on the schedule agreed with the hospital, seven days by default.
Does Vetro capture audio in the operating room?
Not by default. Audio capture is optional and is switched on only if a hospital chooses to enable it. Where it is enabled, capture is triggered by a wake word rather than running continuously, and it is not required for Vetro to run.
Does this work across surgical specialties?
Yes. Vetro captures the operational structure of a case, which generalizes across procedure types. The specialties in scope are agreed with the hospital during deployment, and we raise any challenges we anticipate for a specific specialty as part of that process.
Does this replace the EHR?
No. Signed notes flow into your existing EHR workflow, including Epic and Cerner. Vetro adds the documentation layer rather than replacing the system of record.
