A SOAP note organizes consultation information so that the next authorized professional can understand what the patient reported, what was observed, what the clinical assessment was, and what plan was agreed upon.<\/p>\n\n\n\n
SOAP means Subjective, Objective, Assessment, and Plan<\/strong>. The structure does not replace clinical judgment nor does it turn a consultation into a rigid form. Its function is to provide order to the record so that relevant information is not scattered among quick notes, memory, and loose messages.<\/p>\n\n\n\n This guide explains what each section corresponds to, how to avoid common errors, and what the professional must review before approving or signing a note. The example is fictional, abbreviated, and demonstrative: it does not reproduce an internal Itaca template nor should it be used as clinical guidance for a real case.<\/p>\n\n\n\n A SOAP note is a way to structure clinical documentation of an encounter. It helps separate four things that shouldn't be mixed:<\/p>\n\n\n\n This separation makes the note easier to review and to pick up on a future visit. It also helps when multiple professionals are involved, a shift change occurs, or the patient returns for a follow-up after some time.<\/p>\n\n\n\n There is no single correct SOAP note for every specialty or context. What is documented depends on the care provided, the information available, and the professional's judgment. The structure is a guide for organizing the record, not a substitute for clinical reasoning.<\/p>\n\n\n\n The subjective section gathers what the client, their caregiver, or whoever accompanies them to the consultation communicates. It may include the reason for the visit, the reported progression, relevant history, mentioned treatments, and aspects that the professional considers necessary to understand the encounter.<\/p>\n\n\n\n The goal is not to transcribe the entire conversation. It is to preserve the information that provides clinical context for the assessment and plan.<\/p>\n\n\n\n Helpful questions before closing this section:<\/p>\n\n\n\n The objective section contains findings that the professional observes, measures, or consults from available sources during care. Depending on the context, it may include examination, vital signs, results, reviewed documents, or other verifiable data.<\/p>\n\n\n\n This section should not fill in data that was not available. If a measurement, result, or document is missing, it is more helpful to leave it pending for review than to turn a guess into a recorded fact.<\/p>\n\n\n\n Helpful questions before closing this section:<\/p>\n\n\n\n The assessment connects the context and findings with the clinician's clinical judgment. Here, the impression, issues considered, diagnosis when appropriate, and the reasoning guiding the next step are documented.<\/p>\n\n\n\n This is the section that most clearly requires professional judgment. A tool can organize information to facilitate a draft, but it should not present an inference as a confirmed diagnosis, nor should it make decisions for the professional.<\/p>\n\n\n\n Helpful questions before closing this section:<\/p>\n\n\n\n The plan records what follows the consultation: instructions, studies, treatment, education, referrals, upcoming appointments, and pending items. It should allow the patient and team to know what was agreed upon without having to reconstruct the conversation.<\/p>\n\n\n\n Helpful questions before closing this section:<\/p>\n\n\n\n The following example uses fictional and simplified information. It serves to illustrate the difference between sections, not to publish the exact format of a clinic or to replace professional assessment.<\/p>\n\n\n\n An adult patient presents with respiratory discomfort of a few days' duration. They report cough and congestion and mention they have not started any new medications. The healthcare professional performs the relevant examination and defines a follow-up plan.<\/p>\n\n\n\n Subjective.<\/strong> Reason for consultation, reported progression, relevant symptoms, history, and treatments mentioned during the encounter.<\/p>\n\n\n\n Objective.<\/strong> Findings from examination, vital signs, or other data measured or reviewed during the visit.<\/p>\n\n\n\n Evaluation.<\/strong> Clinical assessment by the professional at the corresponding certainty level and points requiring further observation.<\/p>\n\n\n\n Plan.<\/strong> Instructions, agreed-upon studies or measures, warning signs explained when appropriate, and follow-up criteria.<\/p>\n\n\n\n The value of the example isn't in copying phrases. It's in seeing that each piece of data has its place: what it refers to, what is observed, what the professional evaluates, and what remains to be done.<\/p>\n\n\n\n When findings and assessment are mixed, it becomes difficult for the next person to distinguish what was observed from what was interpreted. Keeping the sections separate makes the record clearer and more reviewable.<\/p>\n\n\n\n A note doesn't improve just because all the spaces are filled. If a date, dosage, result, or relevant piece of information is missing, the draft should leave it visible for the professional to confirm before approving.<\/p>\n\n\n\n An extensive transcript is not always a good clinical note. Documentation should retain what is relevant for care, continuity, and professional review, not repeat every phrase of the conversation.<\/p>\n\n\n\n The plan loses its usefulness when it's unclear what action follows, what's pending, or what needs to be reviewed later. A clear note helps ensure continuity doesn't depend on individual memory.<\/p>\n\n\n\n An AI-generated or AI-assisted note should be treated as a draft until the clinician confirms it accurately reflects the patient encounter. Before approving or signing, omissions should be corrected, information not pertaining to the encounter should be removed, and the assessment, plan, and follow-up should be validated.<\/p>\n\n\n\n The utility of AI is not to decide on the evaluation or sign off for the professional. It can help convert available context into an organized draft for review, for example from an in-person consultation, a video call, a clinical document, or quick notes.<\/p>\n\n\n\n In Itaca, documentation is prepared as a reviewable clinical draft while the professional is seeing the patient. The professional retains editing, approval, and signing of the final note. The flow can be organized with clinical note templates<\/a> and Clinical note rules<\/a> to maintain a consistent structure without exposing the product's internal logic.<\/p>\n\n\n\n To know the complete flow, visit clinical notes with AI<\/a>. To understand the difference between draft, final note, and later corrections, consult Signature, review, and traceability of clinical notes<\/a>.<\/p>\n\n\n\n These three elements complement each other, but they don't do the same thing:<\/p>\n\n\n\n A clinic doesn't need to expose its formats or draft prompts to get started. It can upload an example of the form it already uses; Itaca converts it into a reusable template for future care. The final note still requires professional review.<\/p>\n\n\n\n Before closing a note, the professional can check:<\/p>\n\n\n\n The structure of a note is only part of the job. In a clinic, who accesses the information, how it is protected, and how continuity is maintained between professionals, locations, and shifts also matters.<\/p>\n\n\n\n Itaca encrypts data in transit and at rest. Clinical data belongs to the user and their organization; it is not used to train models, nor is it sold or provided to third parties for commercial purposes. Administrators have visibility into usage, access, and team activity. Learn more about the approach on the page security and privacy of clinical documentation<\/a>.<\/p>\n\n\n\n For teams that need documentation to keep pace with care and follow-up, Clinic software<\/a> Itaca connects shared clinical context with roles, processes, and operational continuity by enabling a unified view of patient information accessible to all relevant stakeholders. This shared context ensures that everyone involved in patient care understands the current situation, treatment plans, and any ongoing issues. It streamlines workflows by clearly defining roles and responsibilities and standardizing processes, reducing ambiguity and potential errors. By maintaining this consistent and accurate information flow, Itaca supports operational continuity, allowing for smoother transitions of care, efficient resource allocation, and improved patient outcomes without interruption or duplication of effort.<\/p>\n\n\n\n SOAP stands for Subjective, Objective, Assessment, and Plan. It is a structure for organizing clinical information from an encounter and facilitating its later review.<\/p>\n\n\n\n No. The structure can be adapted to the type of care, specialty, and consultation context. The important thing is to retain relevant information, distinguish data types, and maintain professional judgment in the evaluation.<\/p>\n\n\n\n No. AI can help prepare a draft, but the responsible professional must review, correct, approve, and sign the final note when applicable.<\/p>\n\n\n\n No. The public examples are illustrative. The templates, rules, and internal logic of the product are not published.<\/p>\n\n\n\n Yes. A clinic can upload an example of the format they already use and convert it into a reusable template for future care, without having to draft prompts or publish their internal logic.<\/p>\n\n\n\n A useful SOAP note makes clear what happened in care and what comes next. Itaca helps prepare structured clinical drafts while you care for patients; you retain final review, approval, and signature.<\/p>\n\n\n\nWhat is a SOAP note and what is it used for<\/h2>\n\n\n\n
\n
The four sections of a SOAP note<\/h2>\n\n\n\n
Subjective<\/h3>\n\n\n\n
\n
Goal<\/h3>\n\n\n\n
\n
Evaluation<\/h3>\n\n\n\n
\n
Plan<\/h3>\n\n\n\n
\n
Illustrative example of a abbreviated SOAP note<\/h2>\n\n\n\n
Reason for a fictional consultation<\/h3>\n\n\n\n
How could the information be organized?<\/h3>\n\n\n\n
Common errors when writing SOAP notes<\/h2>\n\n\n\n
Mix findings with conclusions<\/h3>\n\n\n\n
Convert incomplete information into a fact<\/h3>\n\n\n\n
Copy everything without prioritizing context<\/h3>\n\n\n\n
To leave a plan difficult to follow<\/h3>\n\n\n\n
Sign without a final review<\/h3>\n\n\n\n
How does an AI tool help with SOAP notes<\/h2>\n\n\n\n
SOAP Note, Templates, and Rules: What Changes Each One<\/h2>\n\n\n\n
\n
Checklist before approving or signing a SOAP note<\/h2>\n\n\n\n
\n
SOAP Documentation Security and Continuity<\/h2>\n\n\n\n
Frequently Asked Questions about SOAP Notes<\/h2>\n\n\n\n
SOAP stands for Subjective, Objective, Assessment, and Plan.<\/h3>\n\n\n\n
Does a SOAP note always have to include the same questions or fields?<\/h3>\n\n\n\n
Can an AI tool automatically sign a SOAP note?<\/h3>\n\n\n\n
Does Itaca publish the exact structure of its SOAP notes?<\/h3>\n\n\n\n
Can a clinic use its own format in addition to SOAP?<\/h3>\n\n\n\n
Document with structure, review with clinical judgment<\/h2>\n\n\n\n