Update an EN2.1 sections-based Note.
Request body for updating a sections-based note.
When content_map is sent on a base note update, snapshot_id is required (from create or GET /notes/{id}/edit) for collaborative conflict detection.
Field order: content-update fields (content_map, snapshot_id) first, then mutable fields in the same order as ElationNoteCreate (provider through metadata; create-only layout_name, practice, patient omitted), then confidential.
The ID of the bill associated with the note.
Practice-created identifier for note category (Visit Note Type).
Typed map from section type to its content. All sections are optional.
Keys match section type wire values (NodeType): lowercase single words (e.g. narrative, vitals) or camelCase for multi-word nodes (e.g. followUp).
The ID of the assigned provider.
Successful Response
Full representation of a sections-based note returned by the API.
content holds the sections-based structure: layout (structural description) and content_map (typed section content). This replaces the DocumentNode tree used by the legacy Note model.
layout_name is inherited from ElationNoteCreate. It is not populated on reads — the canonical layout is embedded in content.layout.
The sections-based note content: layout description + typed section content.
Name of the pre-defined layout, e.g. 'simple_note'.
The ID of the patient for whom the note was created.
Authoring practice ID.