Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.encoreos.io/llms.txt

Use this file to discover all available pages before exploring further.

Progress notes in the Clinical core are accessed via individual note URLs. The path /cl/charts/:chartId/notes (without a note ID) is not a registered route. The active route for viewing a progress note is /cl/charts/:chartId/notes/:noteId.

​
Overview

/cl/charts/:chartId/notes is not a registered route. Navigating to it without a :noteId renders NotFound. The active route /cl/charts/:chartId/notes/:noteId renders ProgressNoteDetailPage, a read-only note view with optional action buttons (Sign, Co-sign, Add Addendum) gated on note status and permissions. The page displays:
  • A linked PM encounter alert (if encounter_id is set), with a link to the patient in Practice Management
  • Session Details card: service date, begin/end time, duration, diagnosis code, service line, place of service, telehealth fields
  • Clinical Documentation card: Presenting Problem, Mental Status Exam Findings, Interventions, Member Response, Plan/Next Session
  • Signatures card (if signed or co-signed): signed-at timestamp, cosigned-at timestamp, credentials badges
Note lifecycle observable in code: draft → completed → signed → cosigned → amended / addendum.

​
Who it’s for

Permission required: cl.progress_note.view (on the /cl/charts/:chartId/notes/:noteId route). Additional permission gates within the page:
  • Sign button: cl.progress_note.sign (shown when status is completed)
  • Co-sign button: cl.progress_note.cosign (shown when status is signed)
  • Add Addendum button: cl.progress_note.create (shown when note is finalized: signed, cosigned, amended, or addendum)

​
Before you start

  • You need cl.progress_note.view permission.
  • You must know the chartId and noteId UUIDs; these are typically reached by navigating from a patient chart’s notes tab.

​
Steps

1

Open a patient chart

Navigate to /cl/charts/:chartId and select the Progress Notes tab to see the list of notes for this chart.
2

Open a specific note

Click a note in the list. The router navigates to /cl/charts/:chartId/notes/:noteId and loads ProgressNoteDetailPage.
3

Review session details

The Session Details card shows service date, time, duration, diagnosis code, place of service, and telehealth information if applicable.
4

Review clinical documentation

The Clinical Documentation card shows Presenting Problem, MSE Findings, Interventions, Member Response, and Plan for Next Session.
5

Sign, co-sign, or add an addendum (if permitted)

If your permissions and the note’s status allow it, use the Sign, Co-sign, or Add Addendum button. Sign and co-sign use ProgressNoteSignDialog; addenda use ProgressNoteAddendumDialog.

​
Key concepts

TermMeaning
Note status lifecycledraft → completed → signed → cosigned; finalized notes may become amended or receive an addendum
encounter_idLink to a pm_encounters record; the page uses useEncounterContext to show the linked encounter type and status
MSEMental Status Exam — findings recorded in mse_findings on the note
signer_credentials / cosigner_credentialsCredential strings displayed as badges on the Signatures card
ProgressNoteAddendumDialogDialog for creating an addendum note linked to a finalized note

Clinical

Clinical core overview.

Governance & parity

This page documents shipped product behavior. It is not medical, legal, or billing advice. Verify against your organization’s policies and applicable regulations before using it for clinical, compliance, or billing decisions. Protected health information (PHI) shown in the product is governed by your tenant’s access controls and is never exposed in this documentation.
  • src/routes/cl.tsx
  • src/cores/cl/pages/ProgressNoteDetailPage.tsx
  • src/cores/cl/hooks/useProgressNoteDetail.ts
  • src/cores/cl/components/ProgressNoteSignDialog.tsx
  • src/cores/cl/components/ProgressNoteAddendumDialog.tsx
  • src/cores/cl/types/progress-notes.ts