[docs] Tag docs — concept rewrite and two new flows

[github-actions]

Ezhuthachan

Requested via issue #69 (/document admin/tag). There is no admin docs domain; tags live under platform, where a concept (concepts/platform/tagging.mdx) and a reference (references/platform/tag-config.mdx) already existed.

Changes (both version-3.0 and version-3.1)

Rewritten

• concepts/platform/tagging.mdx — replaced in full to match concept-template.md. Old page used non-template sections (What it represents, How it connects, Tree structure, Lifecycle, Permissions, FHIR reference) and leaked backend permission slugs into a user-facing page. New structure: Definition → Key Attributes (with Resource, Tag tree, Scope, Status sub-sections) → Related. Raw enum values replaced with the labels from public/locale/en.json.

Added

• flows/platform/create-a-tag.mdx
• flows/platform/apply-a-tag-to-a-record.mdx
• flows/platform/_category_.json
• Both flows registered in versioned_sidebars/version-3.0-sidebars.json and version-3.1-sidebars.json (flow sidebar is manual).

Not changed: references/platform/tag-config.mdx — already faithful to the current model and specs.

Traced to

care: care/emr/models/tag_config.py, care/emr/resources/tag/config_spec.py, care/emr/resources/tag/cache_invalidation.py, care/emr/api/viewsets/tag_config.py, care/security/authorization/tag_config.py, care/security/permissions/tag_config.py, care/emr/tagging/base.py.

care_fe: src/pages/Admin/TagConfig/*, src/components/Tags/TagAssignmentSheet.tsx, src/components/Tags/MultiFilterStyleTagSelector.tsx, src/pages/Encounters/tabs/overview/summary-panel-details-tab/encounter-tags.tsx, src/components/Patient/PatientTagsDisplay.tsx, src/components/ui/sidebar/facility/facility-nav.tsx, src/Routers/routes/adminRoutes.tsx, src/types/emr/tagConfig/tagConfig.ts, public/locale/en.json.

Left out (unverified)

• No keyboard shortcut is defined for any tag action in care_fe/src/config/keyboardShortcuts.json, so none is mentioned.
• The system_generated flag shown in the tag details UI is not a field on the TagConfig model, so the concept does not describe it.
• The exact save interaction of the tag picker is component-level; the flow states only the confirmation message that the code emits.

Validation

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

Generated by Ezhuthachan for #69 · opus50 · 253.2 AIC · ⌖ 14.6 AIC · ⊞ 14.4K · ◷
_{Comment /document to run again}

[cloudflare-workers-and-pages]

Deploying coredocs with    Cloudflare Pages

Latest commit:	37a8f6d
Status:	✅  Deploy successful!
Preview URL:	https://49e95cb7.coredocs.pages.dev
Branch Preview URL:	https://docs-tag-docs-13e907e0590e38.coredocs.pages.dev

View logs