SOAP notes in a real OPD: structure without slowing down
2026-10-05 · MedSlay
Every doctor learned SOAP at some point and most abandoned it in practice. Not because the structure is wrong, but because a forty-patient morning leaves no time for four paragraphs per visit, and a note written at 9 pm from memory is worse than a short one written at the desk. The structure survives if you treat it as four questions rather than four sections.
Subjective: what the patient told you. Objective: what you found. Assessment: what you think it is. Plan: what happens next. A note that answers those four, in that order, in as few words as they need, is a SOAP note.
What the four letters are actually for
The point of the order is that each section constrains the next. The story suggests what to examine; the findings support or contradict the story; the assessment has to fit both; the plan follows from the assessment. A note written in that sequence is hard to get wrong, and one that skips a section is easy to misread later — usually by you, three months on, with the patient back and the file open.
It also matters to everyone else who reads it: the colleague covering your OPD, the specialist you refer to, the insurer asking why an admission was needed and, under the Telemedicine Practice Guidelines and the record rules, the regulator.
Subjective: the patient's words, briefly
The presenting complaint in the patient's own terms, how long, what makes it better or worse, and the relevant history — what they already take, what they are allergic to, what happened last time. Two or three lines.
What to leave out: the whole conversation. The test is whether a line changes what you examine or what you decide. If it does not, it is not Subjective; it is transcript.
Objective: what you found, not what you felt
Vitals, examination findings, and anything you looked at during the visit — a report the patient brought, a dressing you took down. This is the section most often missing from OPD notes, and the one most often needed later. "Chest clear" is worth writing even when unremarkable, because it tells the next reader you listened.
Write findings, not impressions. "Tender right iliac fossa, guarding" is Objective. "Looks like appendicitis" belongs in the next section.
Assessment: name the problem, and the alternatives
A working impression and, where there is real doubt, what else you are considering and what would separate them. One line is often enough: what you are treating, and what you are watching for.
This is the section an AI drafting tool is least able to write for you, and should not try to. Software that listens to the consultation can set out the story and the findings; what they add up to is a clinical judgement, and it is yours. MedSlay's voice module drafts the note from the conversation as advisory text, every field waiting for the doctor to confirm or change. The assessment line is the one to read most carefully before you do.
Plan: the part the patient takes home
Treatment, tests ordered, advice given, and when to come back. This section becomes the document on your letterhead, so write it as instructions: what to take, how, for how long; what to get done and when to bring the result; what would mean coming back sooner.
A follow-up line matters more than it looks. "Review in 5 days, or earlier if fever persists" turns the next visit into a continuation, and it is the line a patient most often cannot remember being told.
Where the time really goes
Ask doctors why they do not write SOAP notes and the answer is time. Watch an OPD and the time is not in the structure; it is in typing and repetition. The same history asked again because it is not in the file. The same instructions written again because there is no template. The note left for later because the next token is at the door.
Voice changes the first. A consultation in Gujarati or Hindi can be transcribed and drafted into clinical English as the visit happens, so the Subjective and Objective sections are mostly written by the time you turn to the screen — see how transcription handles Indian languages. No audio is stored; the written note is the record. Templates handle the second: the instructions you give forty times a week should exist once and be edited, not retyped. The third is a queue problem, not a documentation one.
Writing it during the visit, not after
- Open the note before the patient sits down. The previous visit's Plan is on screen; the first question is whether it happened.
- Capture the history as it is told. Dictated or typed, in the patient's language or yours, while you listen rather than afterwards from memory.
- Examine, then record findings in one pass. Vitals and examination go in as you do them, as findings, not conclusions.
- Write the assessment yourself, in one line. What you are treating, and what you are watching for.
- Write the plan as patient instructions. It becomes the document they take home, so write it once, in the form it will be read.
- Confirm and close before the next token. A note finished at the desk is complete; one finished at night is a reconstruction.
A note that still reads well next visit
The real test of a SOAP note is the day the patient returns and you open the file. If the four questions are answered, the last visit takes ten seconds to re-read and the new one starts where it left off. That is what the structure buys you, and it costs nothing extra once the writing happens during the visit rather than after it.
It is also what keeps you on the right side of the record retention rules: a record worth keeping for years is one that can be read in years. For how the note sits alongside the queue and the patient file, see clinic software.