Documentation on Clinical / Clinical Notes

[rithviknishad]

/document clinical/clinical notes

This is about clinical notes (or just Notes) from both patient and encounter view.

[github-actions]

✅ Ezhuthachan completed successfully!

[github-actions]

Ezhuthachan

Documented Clinical Notes and opened a pull request.

Concept — concepts/clinical/notes.mdx was rewritten to the concept template. The old page predated it (What it represents, Threads and messages, Edit history, and a permission table full of slugs). It is now strictly user-facing and covers both entry points you named: the Notes tab of a patient and the Notes tab of an encounter.

Flows — two new pages, because Notes has two distinct user tasks:

• flows/clinical/start-a-note-discussion.mdx
• flows/clinical/add-a-note-message.mdx

Both are listed in the manual Clinical flow sidebar for 3.0 and 3.1.

Reference — references/clinical/notes.mdx was already accurate; only the message_history fence changed from jsonc to text.

All files authored in version-3.0 and mirrored to version-3.1. npm run build is green for en and ml.

One gap: editing a message has no flow. The notes UI renders no edit control, so I could not verify the steps, even though the backend supports it.

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

[github-actions]

Comment Memory

# Clinical Notes (issue #54)

- Backend: `care/emr/models/notes.py` (`NoteThread`, `NoteMessage`), specs in `care/emr/resources/notes/`, viewset `care/emr/api/viewsets/notes.py`.
- Notes has no permission file. Writes use `can_write_patient` (patient-scoped thread) or `can_write_encounter_clinical_data` (encounter-scoped, blocked on completed encounters). Reads use `can_view_clinical_data`, falling back to `can_read_encounter_clinical_data` when the request filters by encounter.
- Display names: "Can Update a Patient's data", "Update Encounter related clinical data", "Can view clinical data about patients", "Can Read encounter related clinical data".
- Frontend: single `src/components/Notes/NoteManager.tsx`, used by the encounter Notes tab and the patient Notes tab (patient tab passes `hideEncounterNotes`). UI words are Discussions / Threads / New, not "notes".
- Thread title templates come from `src/types/notes/thread.ts`. Duplicate titles are rejected client-side.
- Shortcut `g n` goes to the encounter Notes tab; `shift+enter` submits.
- Not documented: editing a message (no edit control in the UI), legacy `patient_notes_thread__*` keys, message replies.
- Delivered: rewritten concept, two flows (`start-a-note-discussion`, `add-a-note-message`), reference fence fix. Branch `docs/clinical-notes`.

Note

This comment is managed by comment memory.

It stores persistent context for this thread in the code block at the top of this comment.
Edit only the text inside the backtick fences; workflow metadata and the footer are regenerated automatically.

Learn more about comment memory

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