Add concept docs for all Care domains, with real permission model#2
Merged
Conversation
Build the Concepts layer ("What is…?") to match the References layer:
23 plain-language concept docs across 8 domains (clinical, medications,
scheduling, billing, supply, facility, forms, access), each distilled
from its technical reference doc.
- Every concept has a Permissions section grounded in the real
care/security/permissions/* enums and roles (care/security/roles).
- A dedicated "Roles & Permissions" concept documents the full RBAC
model: roles, permission contexts, org-tree cascade, memberships.
- Concepts sidebar switched to autogenerated via per-domain
_category_.json (positioned, generated-index landing pages).
- Links follow the repo convention: .mdx for siblings/references,
extensionless for the translated patient/create-patient docs (keeps
the Malayalam locale build green).
- Mirrored to 3.0 & 3.1; full `npm run build` (en + ml) passes clean.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
… Roles The previous tables were cherry-picked 2-column (Permission | Roles) lists. Replace each concept's table with the complete set, sourced from care/security/permissions/<resource>.py: - Every permission in the resource's enum is listed (no cherry-picking). - New Description column: code description where meaningful, otherwise a concise authored explanation of what the permission allows. - System Roles column expands role constants (e.g. CLINICAL_DATA_ACCESS_ROLES) to display names (Doctor, Nurse, Facility Admin, ...). - Multi-resource concepts (billing, supply, organization, questionnaire, specimen, access-control) group rows under per-resource sub-headings. - Surrounding access-model prose preserved. 154 permission rows total. Mirrored to 3.0 & 3.1; full `npm run build` (en + ml) passes clean. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Build the Concepts layer ("What is…?") to match the References layer: 23 plain-language concept docs across 8 domains (clinical, medications, scheduling, billing, supply, facility, forms, access), each distilled from its technical reference doc.
npm run build(en + ml) passes clean.