ClinicDx is the AI-native clinical OS that lets any health facility run a fully digital practice. No Software Team! No Internet! No Code!
Most digital health pilots never reach sustainable scale. The reason isn't technology, it's assumption. Every existing solution assumes the clinic has a software team, an internet connection, and a budget for implementation. Most don't.
Setting up a digital clinic means weeks of form configuration, terminology mapping, and workflow design that only specialists can do. Most facilities cannot afford that team, so the system never gets built, or never gets used.
When clinicians have to type structured notes, code diagnoses, and fill registers themselves, paper wins. The clinic might have an EMR, but the records that matter still live in a notebook on a shelf.
A single clinical officer is often expected to manage malaria, TB, hypertension, pregnancy, and pediatric emergencies in one morning, with no specialist on call and no protocol library at the bedside.
Even when records are captured, they aren't standardized, queryable, or visible to the district. Facilities cannot report. Ministries cannot see. Outbreaks are spotted late, if at all.
ClinicDx is an offline, AI-native clinical operating system. It configures in plain language, documents visits by voice, surfaces cited clinical guidance before every decision, and generates reports on request, all without an internet connection or an IT team.
ClinicDx is built as four tightly integrated layers. A trusted open-source EMR core, an on-device AI agent that turns plain language into clinical action, a standards layer that codes every record to international medical terminologies, and a clinical safety middleware that keeps every AI output reviewable by a clinician.
ClinicDx is open and inspectable.
The model card and source code are public.
Configure, document, decide, and report through a single offline conversation inside the clinic.
Describe the forms and workflows you need. ClinicDx builds them, codes every field, and publishes into the EMR.
You say“Build an antenatal form with danger-sign checks.”
ClinicDxBuilds it, codes the fields, and waits for your review.
Speak the encounter. ClinicDx writes the structured note and codes diagnoses and medications.
You say“Fever and cough for three days. Temp 38.5.”
ClinicDxDrafts the coded note. Nothing saves until you confirm.
Get a guideline-backed second opinion, then a care summary in the patient’s language—both for your review first.
You say“What’s the differential—and what do I tell the patient?”
ClinicDxCites WHO / MSF guidance, then drafts the discharge summary.
Ask in plain language. ClinicDx queries your coded records and returns the answer—no data team needed.
You say“How many malaria cases this month?”
ClinicDxQueries the records and returns the count.
Built on open clinical standards, grounded in WHO and MSF guidelines, and designed to keep every patient record inside your facility.
Built on FHIR R4 and REST API standards. ClinicDx connects to existing health information infrastructure without proprietary connectors, enabling integration with national EMRs and referral networks.
Differential rankings, drug guidance, and clinical protocols are configurable to local disease burden, formulary, and care level. ClinicDx does not impose a single global model on diverse clinical environments.
The complete codebase is publicly available, auditable, and free to deploy. Ministries of Health and implementing partners retain full ownership with no licensing fees and no vendor dependency.
ClinicDx is built to be used, not just installed. It fits the clinic where it lives, runs on the hardware the clinic already owns, and connects cleanly to the health system around it.
A one-time setup, then a recurring rhythm of care.
A clinical lead describes, in plain language, the consultations, registers, and reports the clinic needs. ClinicDx builds them, codes every field, and publishes them into the EMR. No specialist required.
The clinician sees the patient and speaks the encounter. ClinicDx writes the structured note, surfaces evidence-grounded guidance from WHO and MSF, and waits for confirmation before anything is saved.
ClinicDx generates a care summary in the patient's own language: what they have, what to do, what medicines to take, and when to come back. The clinician reviews and prints it.
Designed for the realities of primary care, not the assumptions of cloud software.
A single small server lives in the clinic. It holds the EMR, the AI agent, and the guideline knowledge base. The internet is not required, before, during, or after deployment.
Clinicians work from whatever they have: a laptop, an Android tablet, or a phone. Every device connects to the local server over the clinic's own network.
ClinicDx is designed for unreliable power and intermittent connectivity. It restarts cleanly after outages, syncs when networks come back, and never loses a patient record.
Clinic data that the district and the ministry can actually use.
Every observation is coded to international medical standards as it is captured. The records are queryable, exportable, and ready for reporting from the very first visit.
Facility managers and district officers ask their questions in plain language. ClinicDx returns the answer from the actual clinical records, not from estimates or paper registers.
FHIR R4 export and DHIS2-compatible reporting bridge the clinic to the national health information system whenever connectivity is available, without changing how the clinic works.
ClinicDx replaces the entire traditional EMR rollout, the implementation team, the cloud dependency, and the months of configuration, with a single conversational system that runs inside your clinic.
No. ClinicDx is designed from the ground up to operate fully offline. All AI inference runs on local hardware at the facility. There is no dependency on external servers, cloud APIs, or internet connectivity of any kind.
ClinicDx runs on commodity hardware: a standard workstation or rugged laptop with a modern CPU. No GPU is required for CDS and scribe functionality. Imaging analysis benefits from a mid-range discrete GPU but can operate in CPU-only mode.
ClinicDx integrates natively with OpenMRS 3.x as a microfrontend ESM module (@clinicdx/esm-clinicdx-app). It also exposes a FHIR R4 REST API, enabling integration with other EMR platforms or standalone deployment without OpenMRS.
The scribe feature supports Swahili, Amharic, French, Hausa, and English out of the box. CDS outputs are available in English and French, with localization roadmap prioritized by deployment region.
Completely. Patient data never leaves the facility. ClinicDx performs all AI computation locally, with no external API calls, no cloud uploads, and no telemetry. Outputs are structured and auditable, meeting WHO and national health data governance standards.
Yes. The CDS knowledge base is curated and aligned to WHO and MSF clinical protocols, including WHO Essential Medicines List, WHO Malaria Guidelines, and IMCI protocols. Every CDS output includes citations so clinicians can verify the evidence basis.
Pilot ClinicDx in your facilities to reduce diagnostic uncertainty, preserve data sovereignty, and return clinician time to patient care.
