[docs] Encounter concept rewrite and encounter flows

[github-actions]

Ezhuthachan

Documents clinical/encounter across all three layers for #46.

What changed

Rewritten — concepts/clinical/encounter.mdx (3.0 and 3.1). The previous page predated the concept template: it used the old What it represents / Lifecycle / Classification / How it connects sections and printed raw codebase literals (in_progress, imp, amb). It now follows the template (Definition, Key Attributes, Status, Permissions, Related), uses the user-facing labels from en.json, and links the FHIR page without narrating the mapping.

Added — three flows, in the order a user meets them:

• flows/clinical/create-an-encounter.mdx
• flows/clinical/assign-a-location-to-an-encounter.mdx
• flows/clinical/close-an-encounter.mdx

Each is listed in the manual Clinical flow sidebar for both versions.

Unchanged — references/clinical/encounter.mdx. It was re-verified field by field against the model, spec and constants in the checkout and is accurate, so it needed no edit.

Traced to

• care/emr/models/encounter.py — fields, caches, save behaviour
• care/emr/resources/encounter/spec.py, constants.py — statuses, classes, priorities, hospitalization
• care/emr/api/viewsets/encounter.py — which action authorizes what, restart action, patient-view fallback
• care/security/authorization/encounter.py, care/security/permissions/encounter.py, care/security/roles/role.py — permission names and expanded roles (CLINICAL_DATA_ACCESS_ROLES → Admin, Doctor, Nurse, Facility Admin)
• care_fe: components/Encounter/CreateEncounterForm.tsx, EncounterActions.tsx, components/Location/LocationSheet.tsx, pages/Encounters/MarkEncounterAsCompletedDialog.tsx, components/Questionnaire/QuestionTypes/EncounterQuestion.tsx, pages/Encounters/tabs/overview/summary-panel-reports-tab.tsx, public/locale/en.json, src/config/keyboardShortcuts.json, care.config.ts

Left out

• Exact restart time limit and the maximum active encounters per patient. Both are deployment settings, so the flows say a limit exists rather than naming a number.
• Care team management. The backend has a dedicated care-team endpoint, but I did not find a matching user flow to document, so it is named as an attribute only.
• The 3.1 flow sidebar keeps its existing Patient sub-category; the new flows were appended, not substituted.

Validation

Corruption scan clean. npm run build succeeds for en and ml.

Generated by Ezhuthachan for #46 · opus50 · 336.4 AIC · ⌖ 10.6 AIC · ⊞ 13.5K · ◷
_{Comment /document to run again}

[cloudflare-workers-and-pages]

Deploying coredocs with    Cloudflare Pages

Latest commit:	31b0ec0
Status:	✅  Deploy successful!
Preview URL:	https://54051dec.coredocs.pages.dev
Branch Preview URL:	https://docs-encounter-concept-flows.coredocs.pages.dev

View logs