Public proof
Open infrastructure, supported by real institutions and verifiable public-good signals.
Verified DPG
CARE is listed in the Digital Public Goods registry.
MIT licensed
Reusable by governments, hospitals, NGOs, and partners.
FHIR-native
Built around standards, terminology, and open APIs.
Supported by




Foundation layer
The institution around the healthcare OS.
Healthcare systems do not adopt source code alone. They need governance, releases, documentation, security, and an ecosystem that keeps the shared core dependable over years.
Core platform
Stable primitives, APIs, forms, access control, audit trails, reports, and extensibility.
Standards
FHIR-aligned modeling, terminology bindings, ABDM patterns, and implementation guides.
Quality and security
Release discipline, vulnerability handling, testing expectations, and documentation quality.
Ecosystem
Developer community, clinical review, implementation partners, and public-good funding paths.
AI readiness
Assistive, human-reviewed documentation and summarization on structured clinical data.
CARE is the product proof
One open core. Many real workflows.
CARE Core provides the common primitives. CARE Apps extend the platform for national rails, HMIS, TeleICU, palliative care, AI documentation, LMIS, pharmacy, billing, and analytics.
Longitudinal patient records
OP, IP, emergency, observation, home visits
Clinical notes, forms, orders, prescriptions
Labs, pharmacy, inventory, radiology, billing
Tasks, referrals, care plans, dashboards
ABDM, TeleICU, AI documentation, open APIs
Solutions
Deployable workflows on the healthcare OS.
CARE Core is the shared foundation. Solutions package that core into practical workflows for hospitals, critical care, home care, clinics, public health programs, and specialized field operations.
CARE HMIS
Hospital management workflows for registration, encounters, labs, pharmacy, billing, reports, and patient portal.
Explore
TeleICU
Hub-and-spoke critical care workflows with remote rounds, escalation, devices, and video context.
Explore
Palliative Care Grid
Home-based care coordination, longitudinal records, tasks, referrals, follow-up, and field workflows.
Explore
Care Clinics
Primary care and outpatient workflows for scheduling, prescriptions, investigations, and continuity.
Explore
Care Janwar
Animal health workflows built on the same open-core pattern for facilities and field programs.
Explore
Architecture
AI-ready because the data layer is structured first.
CARE is designed around configurable forms, FHIR-aligned resources, terminology bindings, open APIs, audit trails, and role-based access. AI is framed as assistive and human-reviewed because clinical accountability cannot be automated away.
FHIR R5
SNOMED CT
LOINC
UCUM
ICD-10
ABDM
Why this can scale
A nonprofit with product leverage.
The best nonprofit technology organizations compound: each implementation makes the infrastructure better, each partner expands distribution, and each funded release makes future adoption cheaper.
Software leverage
Each reusable module, form, and integration reduces the cost of the next public health deployment.
Open distribution
Governments, hospitals, implementers, clinicians, and developers can adopt without vendor permission.
Data foundation for AI
Assistive AI becomes safer when it sits on structured, interoperable, auditable health data.
Governance moat
The foundation turns open source into infrastructure institutions can trust for long-term operations.
GitHub Story
Open-source collaboration, shown through the work.
The GitHub story is useful proof because it shows OHC as a real contributor network: clinicians, engineers, and institutions building healthcare infrastructure in the open.
Evidence
Field proof, handled with discipline.
OHC has public proof across the DPG registry, open-source repositories, standards architecture, and program deployments. The site keeps metrics dated and program-specific so funders, governments, and media see disciplined claims instead of impact theater.
DPG
Externally listed
MIT
Reusable by default
Open APIs
Built for integration
Community Signals
Recognition from people who understand infrastructure.
See the signals behind the open healthcare infrastructure community.
Blog
Notes for builders of public-good health infrastructure.
May 27, 2026
Why open healthcare infrastructure needs a foundation
Code is necessary, but not sufficient. Health systems need stewardship, release discipline, documentation, security, and an ecosystem that can outlast any one deployment.
Read essay
May 20, 2026
AI-ready, not AI-hyped
Assistive AI in healthcare should sit on structured, interoperable data and human-reviewed workflows. The foundation layer matters before the model layer.
Read essay
May 13, 2026
CARE Core as an operating layer for healthcare workflows
CARE Core provides reusable primitives for patient records, encounters, orders, observations, tasks, care plans, reports, access control, audit trails, and APIs.
Read essay
Who should work with OHC
One foundation, multiple high-leverage paths.
Governments can deploy, funders can support, implementation partners can localize, developers can contribute, and clinicians can shape workflows.
Governments
Own, adapt, and scale health infrastructure locally.
Funders
Back the shared core, not one-off software delivery.
Hospitals
Deploy practical HMIS and EMR workflows without license lock-in.
Implementation partners
Localize CARE and contribute improvements back.
Developers
Build open-source healthcare infrastructure used in the field.
Clinicians
Shape workflows, forms, safety, and AI documentation behavior.
Build the open healthcare commons.
Help OHC Foundation maintain the shared core, governance, security, documentation, and ecosystem that let health systems deploy modern software without vendor lock-in.






