Open Healthcare Network
Open Healthcare Network(OHC) is an open-source platform that helps governments, hospitals, and innovators build connected healthcare systems faster, safer, and at national scale.
Since
6 years
2,295 days
Total Contributors
1,391
All time
Total Activities
917
9%
Last 30 days
Active Contributors
44
Last 30 days
Activity Trend
Daily activity over the last 30 days
917activities in the last 32 days
1,701 total points
Activity Breakdown
Distribution by type (30 days)
PR Reviewed25628%
Commit Created20022%
Commented15817%
PR Opened15016%
PR Merged12514%
Issue Closed172%
Issue Opened91%
Issue Assigned20%
Top Contributors
View allThis week
Recent Achievements
View allLatest badges earned
Our Community
1,391 contributors building together
RIMOVIJAAMNAABBOSOGIYAPRNIARVAVIHAVIJAACPRRARAAAASKHSRADJEMA
1361
Recent Activity
View leaderboardBO
Bodhish ThomasPushed commit to main·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 ../<category>/ 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) <[email protected]>
+2BO
Bodhish ThomasPushed commit to main·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) <[email protected]>
+2BO
Bodhish ThomasPushed commit to main·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) <[email protected]>
+2BO
Bodhish ThomasPushed commit to main·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) <[email protected]>
+2BO
Bodhish ThomasPushed commit to main·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) <[email protected]>
+2BO
Bodhish ThomasPushed commit to main·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) <[email protected]>
+2BO
Bodhish ThomasPushed commit to main·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) <[email protected]>
+2BO
Bodhish ThomasPushed commit to main·Revert "Fix the shape"
This reverts commit f3006a243bac58f4cb879f2380bf77f1209f2d91.
+2BO
Bodhish ThomasPushed commit to main·Merge pull request #2 from ohcnetwork/docs/care-3-concepts
Add concept docs for all Care domains, with real permission model
+2BO
Bodhish ThomasMerged pull request #2·Add concept docs for all Care domains, with real permission model
+5BO
Bodhish ThomasPushed commit to main·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/<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) <[email protected]>
+2Leaderboard
See who's leading this week, month, and year.
People
Browse all contributors and their profiles.
Badges
Explore achievements and milestones earned.