[docs] Clinical Notes concept, flows and reference fix

[github-actions]

Ezhuthachan

Documents Clinical Notes (patient view and encounter view), traced to the Care and care_fe checkouts.

Files

Authored in version-3.0 and mirrored byte-identical to version-3.1.

• Rewritten: concepts/clinical/notes.mdx. The old page predated the concept template: it used ## What it represents, ## Threads and messages, ## Edit history and a ## Permissions table full of permission slugs. It now follows the template (## Definition, ## Key Attributes, ## Related), is strictly user-facing, and uses the labels the user sees (Discussions, Threads, New).
• Added: flows/clinical/start-a-note-discussion.mdx, flows/clinical/add-a-note-message.mdx.
• Changed: references/clinical/notes.mdx — the message_history block used a jsonc fence; changed to text per the reference structure rule. No content change.
• Changed: versioned_sidebars/version-3.0-sidebars.json and versioned_sidebars/version-3.1-sidebars.json — both flows added to the manual Clinical flow list.

The request named a single slug (clinical/clinical notes) with no doc types, so all three layers are covered. Notes is a task with two distinct user actions, so it produced two flows: start a discussion first, then post a message in it.

Traced to

• code/care/care/emr/models/notes.py — NoteThread, NoteMessage, message_history.
• code/care/care/emr/resources/notes/thread_spec.py, notes_spec.py — title limit, encounter validation, server-side edit history.
• code/care/care/emr/api/viewsets/notes.py — authorization per action.
• code/care/care/security/authorization/patient.py, encounter.py → care/security/permissions/patient.py, encounter.py → care/security/roles/role.py for the permission display names in the flows: Can view clinical data about patients, Can Read encounter related clinical data, Can Update a Patient's data, Update Encounter related clinical data. Encounter writes are blocked once the encounter is completed, which is why both flows list an open encounter as a pre-requisite.
• code/care/care_fe/src/components/Notes/NoteManager.tsx, src/pages/Encounters/tabs/notes.tsx, src/components/Patient/PatientDetailsTab/PatientNotes.tsx, src/types/notes/thread.ts — UI steps, discussion templates, duplicate-title error.
• code/care/care_fe/public/locale/en.json — every user-visible label.
• code/care/care_fe/src/config/keyboardShortcuts.json — g n for the encounter Notes tab, shift+enter for submit. No other shortcut applies.

Left out

• Editing a message is described in the concept, but has no flow: NoteManager.tsx renders no edit control, so the UI steps could not be verified. The backend supports it and only the message author may edit.
• The concept no longer names FHIR Communication in prose; it links the FHIR page from the bold first mention instead, per the FHIR rule.
• Message replies and per-role thread names (patient_notes_thread__Doctors) exist only in legacy locale keys, so they are not documented.

Validation

Corruption scan clean. npm run build returns [SUCCESS] for build and build/ml, exit code 0.

Generated by Ezhuthachan for #54 · opus50 · 233.4 AIC · ⌖ 20.5 AIC · ⊞ 13.5K · ◷
_{Comment /document to run again}

[cloudflare-workers-and-pages]

Deploying coredocs with    Cloudflare Pages

Latest commit:	0acabd1
Status:	✅  Deploy successful!
Preview URL:	https://11f35aba.coredocs.pages.dev
Branch Preview URL:	https://docs-clinical-notes-ffd0fe5d.coredocs.pages.dev

View logs

[github-actions]

Generated by Docs Reviewer for #56 · opus50 · 132.4 AIC · ⌖ 15.8 AIC · ⊞ 11K

[github-actions]

Template conformance (checklist item 8): the concept template requires a ## Definition section as the first heading, holding the opening paragraph. This page goes from the H1 straight to prose and then ## Key Attributes, so the required section is missing. Add ## Definition above the opening paragraph (line 7). The same fix is needed in the 3.1 mirror.