At 6:45 p.m., the operating list is finished but the documentation is not. One note needs the exact procedure and findings. Two families need a plain follow-up plan. Tomorrow’s clinic already has 14 patients. This is where AI can help a surgeon now: drafting and organising words, under review, outside the operative decision.
The working boundary
- Use AI first where the output is a visible draft tied to an authorised source.
- Keep consent, diagnosis, operative choices, orders, and final signatures human-owned.
- Never replace the surgical team’s safety pause with a software completion mark.
- Test Indian language input, English note output, privacy, corrections, and downtime together.
A green, amber, red map for a surgical unit
| Zone | Example | Minimum control | Verdict |
|---|---|---|---|
| Green | Draft a clinic, ward-round, or follow-up note from a conversation | Surgeon checks every fact before signing | Pilotable |
| Green | Turn the surgeon’s dictated facts into a structured draft | Preserve source, author, time, and corrections | Pilotable |
| Amber | Summarise an authorised longitudinal record for review | Link every conclusion back to the source record | Test narrowly |
| Amber | Prepare a postoperative instruction draft | Treating team approves every patient-specific instruction | Test narrowly |
| Red | Infer an operative finding that was not stated | No safe documentation shortcut | Do not deploy |
| Red | Recommend an incision, device, diagnosis, or treatment from the live case | Requires a different validated clinical product and governance case | Outside scribe scope |
| Red | Mark a safety checklist complete because a field is populated | Team confirmation has not occurred | Do not deploy |
The colour belongs to the task, not the brand. A product can be green for clinic-note drafting and red for intraoperative decisions on the same day.
Before theatre: draft the record, not the consent decision
A preoperative consultation contains history, the surgeon’s assessment, discussion of options, and a plan. An ambient scribe can draft the words spoken during that consultation. It cannot decide whether consent is valid, whether the proposed procedure fits the patient, or whether an unstated risk was discussed.
Use a short review card:
- correct patient and encounter;
- history and examination facts actually stated;
- procedure and laterality stated by the surgeon;
- discussion captured without invented assurances;
- medicines and allergies checked against the authorised record;
- questions or uncertainty left visible;
- clinician edits and signature recorded.
The MoHFW EHR Standards for India, 2016 describe an EHR as a collection of records generated through clinical encounters and explain why longitudinal, clinically relevant records matter. They are a standards reference, not proof that any AI draft is complete.
For the narrower specialty-scribe decision, compare the India cardiology clinic workflow and the medico-legal documentation guide. The surgical boundary is stricter when the missing fact concerns an operation.
Inside theatre: the team pause stays a team pause
The WHO Surgical Safety Checklist resources organise checks around three critical points: before anaesthesia, before incision, and before the patient leaves the operating room. WHO’s implementation material centres verbal participation and local adaptation.
Software can show a checklist, record a time, or route an unresolved item under a hospital’s approved process. It should not infer that a pause happened because boxes became checked. Nor should an AI scribe decide that the site, procedure, count, specimen label, antibiotic plan, or recovery concern is correct.
If the team finds a discrepancy, the useful system keeps it open and names an owner. A green dashboard that hides an unresolved mismatch is worse than paper.
After theatre: dictate exact facts, then inspect the draft
An operation-note draft should begin with facts supplied by the surgeon and theatre record. Build the review around what could cause harm if copied incorrectly:
- procedure and laterality;
- operative findings;
- specimens and labels;
- implants, devices, drains, or counts when applicable;
- blood loss and complications as documented by the responsible team;
- postoperative plan and destination;
- author, reviewer, time, and later correction.
Do not let the model fill silence from a template. “No complication stated” is not the same as “no complication occurred.” The reviewer must resolve the difference.
The same rule applies to discharge material. A draft can organise the treating team’s approved instructions. It cannot invent a medicine, follow-up interval, warning sign, or fitness decision.
Privacy starts before the first real recording
The DPDP Act, 2023 supplies the statutory framework for processing digital personal data in India. Its application to a hospital workflow, notices, consent, lawful uses, processors, retention, and patient rights needs organisation-specific legal review.
For a pilot, name the data path on one page:
- which encounter is captured;
- which device and account receive it;
- whether audio is stored;
- which note and transcript artifacts remain;
- who can view, edit, export, and delete them;
- how a patient request or incident is routed;
- what happens when connectivity fails.
Start with synthetic cases. Move to real patient information only after the hospital’s privacy, security, clinical, and contracting owners approve the exact workflow.
The India pilot: five cases, one correction drill
Use five synthetic cases rather than a polished vendor script:
- a Hindi-English clinic discussion that must yield an English clinical draft;
- a laterality correction caught before signature;
- a ward round with two speakers and an interrupted plan;
- a postoperative draft with one deliberately unstated field;
- a connectivity loss followed by recovery and audit review.
Score factual omissions, unsupported additions, correction trace, reviewer effort, access, and export. Do not publish an accuracy percentage from five cases. The pilot is a failure search, not a marketing study.
WHO’s AI-for-health guidance puts human autonomy, safety, transparency, accountability, inclusion, and sustainability at the centre of deployment. For a surgical unit, that means the surgeon and hospital remain responsible for deciding when a draft can enter the record.
We think the best early result is boring: fewer unfinished notes, no broader clinical claim, and a correction trail the quality team can follow.
Patient Square’s stated scope
Patient Square is an AI clinical platform. Practice Copilot brings the whole practice under one AI copilot: an ambient AI Medical Scribe that hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft minutes after the visit, plus a bundled AI EHR, scheduling, and messaging as you move up the plan. Hospitals get Hospital Copilot.
For India, Patient Square’s stated scribe scope includes multilingual and code-mixed speech with the note produced in clinical English. Live consultation audio is processed in memory and discarded when the note is drafted; uploaded recordings use a separate retention mode with explicit consent. ICD-10 output remains suggestions, prescriptions remain drafts, and ABDM integration remains on the roadmap. Patient Square does not claim image interpretation, surgical planning, robotic control, intraoperative recommendations, or autonomous signing.
If the green-zone documentation work is your bottleneck, review the current Hospital Copilot scope. Confirm the current India plan and product scope and security posture before expanding the pilot.