Entity

Clinical Note

The structured or unstructured documentation of a patient encounter including SOAP notes, H&P, progress notes, and discharge summaries created by clinicians.

Last updated: February 2026Data current as of: February 2026

Why This Object Matters for AI

AI documentation assistants and NLP summarization tools require access to existing notes to maintain continuity and avoid duplication; without it, AI generates notes in isolation.

Clinical Operations & Patient Care Capacity Profile

Typical CMC levels for clinical operations & patient care in Healthcare organizations.

Formality
L3
Capture
L3
Structure
L3
Accessibility
L2
Maintenance
L3
Integration
L2

CMC Dimension Scenarios

What each CMC level looks like specifically for Clinical Note. Baseline level is highlighted.

L0

Clinical notes do not exist in any documented form. Providers remember what happened during encounters and relay information verbally at shift change. When a consulting physician needs to know what the primary team found, they walk over and ask. The patient's clinical story lives entirely in the heads of whoever was present.

None — AI cannot process, summarize, or learn from clinical encounters because no clinical notes exist in any system.

Require providers to create any form of encounter documentation — even handwritten progress notes or dictated summaries filed in the patient chart.

L1

Providers document encounters inconsistently. One physician dictates detailed notes that get transcribed days later, another writes brief handwritten entries, a third types free-text notes in the EHR with no consistent structure. The quality and completeness of clinical notes depends entirely on who wrote them and how much time they had.

AI could attempt to extract clinical information from the notes that do exist, but inconsistent formats and varying completeness make NLP extraction unreliable — critical findings may be buried in dictation or absent entirely.

Standardize clinical note templates in the EHR — implement SOAP note, H&P, and discharge summary templates with required sections that all providers must complete for each encounter type.

L2

Clinical notes follow standard templates in the EHR. Progress notes use SOAP format, admission H&Ps have required sections, and discharge summaries follow a defined structure. All providers document in the same system with the same templates. Note quality is consistent, but the content within sections is still free-text narrative that requires human reading to extract clinical facts.

AI can navigate clinical note sections reliably and extract information from predictable locations (Assessment section for diagnoses, Plan section for orders). NLP can process notes for clinical themes, but precision is limited by free-text ambiguity.

Add structured clinical elements within notes — link diagnoses to ICD-10 codes inline, embed medication orders as structured references rather than narrative text, and require coded problem assessments alongside free-text narrative.

L3Current Baseline

Clinical notes combine structured elements with narrative context. Each note includes coded diagnoses, linked medication references, structured vital sign summaries, and quantified assessment scores alongside the provider's clinical narrative. A query for 'all encounters where sepsis was diagnosed' returns accurate results because diagnoses are coded, not just mentioned in free text.

AI can reliably extract clinical facts from notes using both structured codes and NLP on the narrative sections. Automated coding assistance, clinical summarization, and quality measure abstraction are accurate and actionable.

Implement formal clinical note schemas with entity relationships — link every clinical assertion to its evidence (lab results, imaging findings), map clinical reasoning chains, and encode decision rationale as structured metadata.

L4

Clinical notes are schema-driven documents with formal entity relationships. Every clinical assertion links to supporting evidence — a diagnosis links to the lab results and imaging findings that support it, a treatment decision links to the clinical guideline applied, and the provider's reasoning chain is encoded as structured metadata alongside the narrative. AI can ask 'why was this antibiotic chosen?' and trace the reasoning.

AI can perform deep clinical reasoning from notes — understanding not just what was decided but why. Autonomous quality review, coding validation, and clinical documentation improvement are highly accurate because the reasoning structure is explicit.

Implement real-time clinical note generation where notes are created automatically from clinical workflows — ambient documentation captures the encounter as it happens, with the provider reviewing and attesting rather than authoring.

L5

Clinical notes generate automatically from clinical workflows. Ambient AI captures provider-patient conversations, structures clinical findings from examination data, and assembles comprehensive encounter notes in real-time. The provider reviews and attests to the AI-generated note rather than creating it from scratch. Notes self-update as new information arrives during the encounter — the note is a living document until it is signed.

Can autonomously generate, structure, and maintain clinical documentation from ambient encounter capture. AI produces notes that meet regulatory and billing requirements while preserving clinical nuance and provider reasoning.

Ceiling of the CMC framework for this dimension.

Capabilities That Depend on Clinical Note

Other Objects in Clinical Operations & Patient Care

Related business objects in the same function area.

Patient Record

Entity

The comprehensive longitudinal record of a patient's medical history, diagnoses, treatments, allergies, medications, and care episodes maintained by the healthcare organization.

Medical Image

Entity

The DICOM-formatted radiology images (X-ray, CT, MRI, ultrasound) with associated metadata including patient context, prior imaging, and clinical indication.

Vital Signs Record

Entity

The timestamped measurements of patient physiological parameters including heart rate, blood pressure, respiratory rate, temperature, and oxygen saturation.

Medication Order

Entity

The prescriber's documented instruction for a medication including drug, dose, route, frequency, duration, and clinical indication tied to a specific patient.

Laboratory Result

Entity

The structured output of clinical laboratory tests including values, reference ranges, abnormal flags, and collection timestamps for blood, urine, and other specimens.

Care Plan

Entity

The documented treatment plan for a patient including goals, interventions, responsible providers, and target outcomes for acute or chronic conditions.

Clinical Protocol

Rule

The standardized clinical pathway or evidence-based protocol defining appropriate care steps, decision points, and interventions for specific conditions or procedures.

Surgical Case Record

Entity

The comprehensive record of a surgical procedure including preoperative assessment, operative notes, anesthesia record, complications, and post-operative orders.

Clinical Workflow Template

Entity

The defined sequence of clinical tasks, handoffs, and decision points for specific care settings including ED throughput, OR turnover, and inpatient discharge.

Remote Monitoring Data Stream

Entity

The continuous or periodic data from remote patient monitoring devices including wearables, home sensors, and connected medical devices transmitted to the care team.

What Can Your Organization Deploy?

Enter your context profile or request an assessment to see which capabilities your infrastructure supports.