Bodhish Thomas

Add security docs

Fix build

Update url

Merge branch 'main' of github.com:ohcnetwork/docs

Move old docs

feat: add Common Lab Codes for India (CLCI · LOINC)

Merge pull request #1 from ohcnetwork/feat/clci-lab-codes feat: add Common Lab Codes for India (CLCI · LOINC)

feat: add Common Lab Codes for India (CLCI · LOINC)

docs: document CLCI labs section and LOINC attribution - README: describe the two-section hub, labs data model, build wiring - NOTICE / DATA_LICENSE.md: add LOINC (c) Regenstrief attribution + non-endorsement - docs/superpowers/specs: CLCI design spec Co-Authored-By: Claude Opus 4.8

feat(labs): add lab browse + detail UI and two-section hub - /labs: instant in-memory search + specimen/scale/discipline facets (mobile-collapsible, aria-pressed, deep-linkable via ?q=/?category=/?specimen=) - /lab: decodes a test's LOINC FSN into six plain-English axes, graceful raw-FSN fallback for unparsed codes, LOINC code / FHIR Coding copy, related-by-specimen - rework home into a two-section "Clinical Codes Browser" hub (Drugs + Labs); nav, footer LOINC attribution, head metadata; tokenize the off-palette substance badge Co-Authored-By: Claude Opus 4.8

feat(labs): add CLCI lab-codes data pipeline and module Add the Common Lab Codes for India (CLCI), a curated subset of LOINC v2.82 (1,473 tests), as a self-contained module keyed on LOINC code: - src/lib/labs: types, curated LOINC glossary, discipline categories, client data layer - scripts/lib/loinc.ts: CSV parse + best-effort/validated FSN decomposition (+ tests) - scripts/build-labs.ts: emits public/data/labs/{tests,manifest}.json - scope the drug build's cleanup so the two builds coexist under public/data - package.json: build:data chains drugs then labs; add test:labs; bump 0.1.0 -> 0.2.0 Co-Authored-By: Claude Opus 4.8

Improve CARE blog content from ACT reports

Fix blog article SEO cards

Merge pull request #152 from ohcnetwork/codex/care-blog-history Fix blog article SEO cards

Fix blog article SEO cards

Fix blog article SEO cards

Add historical CARE blog archive

Merge pull request #151 from ohcnetwork/codex/care-blog-history Add historical CARE blog archive

Add historical CARE blog archive

Add historical CARE blog archive

Merge pull request #26 from ohcnetwork/credit-account-validate

Render patient extensions on patient profile

Register Components for Plugins using Vite

Add support for plug component in notes

docs: refresh CARE plugin/apps docs to match shipped reality

Merge pull request #23 from ohcnetwork/copilot/fix-datetime-to-date-conversion Respect timezone when converting datetimes to dates for Odoo sync

Reorganize doc categories: add Definitions and Access & Governance Rework the concept/reference taxonomy so categories reflect what things are, not just where they sit: - New "Definitions & Terminology": activity/observation/specimen/charge-item definitions, product-knowledge, questionnaire, questionnaire-response- template, and valueset — the reusable structures instance records reference. - New "Access & Governance" (instance-level): organization, facility- organization, user, role, permission, permission-association / access-control. - questionnaire-response moves into Clinical (it is clinical data). - "forms" and "access" dissolve into the above; clinical, medications, scheduling, billing, supply, facility, platform, foundation are retained. Mechanics: normalized sibling links to ..// form, moved files, rewrote link category segments, rebuilt _category_.json (label, position, key, generated-index) for every domain, and set within-category ordering. Updated the landing page (intro + the Concepts/References index blurbs) and the care-doc skills' domain conventions. Mirrored 3.0 ≡ 3.1 (verified identical); full `npm run build` (en + ml) passes clean. Co-Authored-By: Claude Opus 4.8 (1M context)

Rewrite all reference docs to Stripe-grade quality Editorial elevation of all 52 generated reference pages (both versions) via a draft → ruthless-edit pass: orient the reader in the first sentence, confident active voice, section lead-ins that carry signal, Notes columns that state constraints/behaviour rather than restating field names, and removal of the tells that make docs read as machine-written (formulaic openers, hedging, marketing words, empty connectives, repetition). Strictly fact-preserving: verified that no field, type, enum value, permission slug, code block, or link target was dropped — diffed every page's inline-code-token and link sets against a pre-pass baseline (the one flag, payment-reconciliation, was a clearer re-expression of the same Decimal precision + validation, not a loss). The human-authored patient reference is left as-is. Mirrored 3.0 ≡ 3.1; full `npm run build` (en + ml) passes clean. Co-Authored-By: Claude Opus 4.8 (1M context)

Add care-reference-doc and care-concept-doc skills Two reusable Claude Code skills (in .claude/skills/) that codify how this docs site is built, so new Care backend changes — ideally each merged Care PR — can drive doc updates consistently. - care-reference-doc: build/update a reference page ("How is it built?") from the Django model + Pydantic resource specs (the two-layer rule), with the page structure, the PR-update workflow, and conventions. - care-concept-doc: build/update a concept page ("What is…?") to the patient-example quality bar, including the permission-table methodology (trace the viewset's real authorization → handler → permission slug → roles) and the Care design-doc sources. - Shared references/conventions.md: domains & slugs, the link rule (.mdx everywhere except the translated patient/create-patient), MDX safety (no {#anchor} ids; wrap literal braces), 3.0≡3.1 mirroring, and the full `npm run build` (all locales) gate. Co-Authored-By: Claude Opus 4.8 (1M context)

Document Organization & Facility Organization features properly Flesh out organizations to cover what the model actually supports, drawing on the Care design docs: - Organization concept: the permission-grouping purpose; org types and their distinct roles — government hierarchies (govt orgs mirroring State→District→…, viewable by all, superadmin-managed, referenced geographically by facilities/patients), role organizations as user groups (Volunteer/ASHA Worker/MLSP; questionnaire/prescribing assignment), team, product_supplier; roles as permission-sets vs role orgs; the privilege-subset membership rule and the managing-organization management hierarchy for user administration. - Facility Organization concept: the real FacilityOrganizationTypeChoices (root/dept/team/role/other) and how facility orgs scope encounter access. - Organization reference: fix the incorrect claim that FacilityOrganization uses OrganizationTypeChoices (it has its own enum); add the facility-org type values + specs; enrich govt/role semantics and managing_organizations. Mirrored 3.0 ≡ 3.1; full `npm run build` (en + ml) passes clean. Co-Authored-By: Claude Opus 4.8 (1M context)

Correct all concept permission tables against code/care viewset authorization Re-verify every concept's Permissions table by tracing what each resource's viewset actually authorizes — action → authorization handler method → real permission slug → roles — using code/care as the single source of truth (not just dumping the permission enum). - Tables now use the real permission slugs the code checks (e.g. clinical resources gate on can_read_encounter_clinical_data / can_write_encounter_ clinical_data; the encounter resource itself on can_read_encounter / can_write_encounter). - Roles reflect the actual role lists (e.g. CLINICAL_DATA_ACCESS_ROLES). - allergy-intolerance and condition realigned to code/care as well. Mirrored 3.0 ≡ 3.1; full `npm run build` (en + ml) passes clean. Co-Authored-By: Claude Opus 4.8 (1M context)

Rebuild concepts: de-clustered into individual primitives, patient-quality Replace the clustered concept pages (medication/billing/supply/scheduling) with one concept per primitive (42 concepts across 8 domains), each crafted to the gold patient example's standard via a draft → editorial-refine pass: sharp plain-language definitions, a clarifying insight, conceptual lifecycle/relationship sections, accurate status/type values. Also fixes condition.mdx's permission table against the authz-fixed model (adds can_write_patient / can_list_patients, drops the non-existent _clinical_data permissions, keeps the real questionnaire rows). Known follow-up: the remaining concept permission tables still reflect the older permission model (split _clinical_data perms, roles missing Staff, mixed slug/display-name style) and will be re-verified against the authz-fixed Care permissions in a separate pass. Mirrored 3.0 ≡ 3.1; full `npm run build` (en + ml) passes clean. Co-Authored-By: Claude Opus 4.8 (1M context)

Language polish across all concept and reference pages Editorial pass over the 75 AI-generated concept and reference pages (both versions): clearer, tighter, more consistent prose — active voice, less filler, better flow and transitions. Strictly content-preserving: frontmatter, headings, every table cell's data, code blocks, links, and all technical tokens (field names, types, enums, permissions, roles, API paths) are unchanged. Verified by diffing a structural fingerprint (headings + table rows + link targets) of every page before and after; only descriptive prose changed. Human-authored gold pages (intro, patient concept/reference, the create-patient flow) left untouched. Mirrored 3.0 ≡ 3.1; full `npm run build` (en + ml) passes clean. Co-Authored-By: Claude Opus 4.8 (1M context)

Revert "Fix the shape" This reverts commit f3006a243bac58f4cb879f2380bf77f1209f2d91.

Fix the shape

Add concept docs for all Care domains, with real permission model

Merge pull request #2 from ohcnetwork/docs/care-3-concepts Add concept docs for all Care domains, with real permission model

Rewrite concept Permissions tables: Permission | Description | System 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/.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)

Add concept docs for all Care domains, with real permission model

Add concept docs for all Care domains, with real permission model 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)

Fix Malayalam docs fallback links

Add spec-enriched model reference docs for Care 3.0 & 3.1

Merge pull request #1 from ohcnetwork/docs/care-3-model-references Add spec-enriched model reference docs for Care 3.0 & 3.1

Add reference docs for QuestionnaireResponse, FormSubmission & response templates questionnaire.py defines six models; split the three distinct resources that have their own Pydantic specs into dedicated reference docs: - forms/questionnaire-response — QuestionnaireResponse + FormSubmission (submit payload, status enums, structured responses, read/write specs) - forms/questionnaire-response-template — QuestionnaireResponseTemplate (TemplateData shape: pre-filled questionnaire answers, medication requests, activity definitions; create/update/read/retrieve specs) Cross-linked from the questionnaire doc; valueset repositioned to 4. Mirrored to 3.0 & 3.1; `npm run build` passes clean. Co-Authored-By: Claude Opus 4.8 (1M context)

Add spec-enriched model reference docs for Care 3.0 & 3.1

Add spec-enriched model reference docs for Care 3.0 & 3.1 Generate technical reference documentation for all ~50 Care EMR models, organized into 10 domains (foundation, clinical, medications, supply, scheduling, billing, facility, forms, access, platform). Each doc cross-references both layers of the backend: - the Django model (storage) in care/emr/models, and - the Pydantic resource specs in care/emr/resources — enums, the structured shape of JSON fields, Create/Update/List/Retrieve API schemas, validation, and server-maintained behaviour. - References sidebar switched to autogenerated via per-domain _category_.json (positioned, with generated-index landing pages) - version-3.0 and version-3.1 kept byte-identical - Validated with `npm run build` (onBrokenLinks: throw) — passes clean, no broken links or anchors Co-Authored-By: Claude Opus 4.8 (1M context)

Update copyright year in LICENSE file

Update copyright year in LICENSE file (#3685)

Update copyright year in LICENSE file

Initial commit: CDCI Browser — NRCeS India drug codes (SNOMED CT) Frontend-only Next.js static site to search/browse India's Common Drug Codes (NRCeS CDCI SNOMED CT flat files), enrich clinical fields via a GitHub-PR overlay, and copy concepts as CARE ProductKnowledge. SNOMED CT is the canonical identifier. - Build pipeline (scripts/): TSV -> validated -> strength-parsed -> bucketed JSON + FlexSearch records; community enrichment overlay merge; manifest. - App (src/): prefix typeahead, substance/generic/brand detail pages, SNOMED/FHIR/CARE copy, PWA/offline. - Enrichment workflow + CI validation + governance/licensing docs. Co-Authored-By: Claude Opus 4.8 (1M context)

Incorrect datetime to date conversion.

Incorrect datetime to date conversion.

Care 3.0 Update

Care 3 Update

Remove questionnaire tags entirely (align with backend removal)

Remove questionnaire tags entirely (align with backend removal) (#16447) Co-authored-by: Claude Opus 4.8 (1M context)

Remove questionnaire tags entirely (align with backend removal)

feat: make toast notification position configurable via env

feat: make toast notification position configurable via env (#16435)

Versions for Valusets

feat: make toast notification position configurable via env