KHIS and MOH Reporting Software for Kenyan Facilities
Monthly MOH returns and the IDSR weekly report counted from what clinicians already recorded, checked by your records officer, then sent to KHIS.
What’s included
- MOH 705A and 705B outpatient morbidity, counted from coded diagnoses
- MOH 711 from the ANC, immunisation, family planning and growth registers
- MOH 717 service workload and MOH 706 laboratory summary
- IDSR weekly return, with thresholds that alert when a disease crosses its limit
- Submission to KHIS (DHIS2) with a preview and a dry run first
- Mapping of each report line to your KHIS data elements and organisation unit
- ICD-11 diagnoses mapped to MOH lines so the count follows the coding
In most Kenyan facilities the monthly returns are compiled the hard way: a health records officer works through registers and tally sheets, adds them up, and types the totals into KHIS. It takes days, it is error-prone, and the numbers rarely match anything else the facility produces.
AfyaConnect produces the returns from the clinical record instead.
The returns
- MOH 705A and 705B. Outpatient morbidity for under-fives and over-fives, counted from the diagnoses clinicians record. Diagnoses are coded in ICD-11 and mapped to the MOH line, so the count follows the coding and a primary diagnosis cannot be saved without a line to count it on.
- MOH 711. Reproductive and child health, compiled from the ANC, immunisation, family planning, growth and TB screening registers.
- MOH 717. Service workload.
- MOH 706. Laboratory summary.
- IDSR weekly. Counted from coded diagnoses, with facility name and code, and a record of each submission.
Sending to KHIS
The facility connects its KHIS (DHIS2) account once. Credentials are stored encrypted, and the dataset, data elements and organisation unit are fetched from KHIS itself, with the organisation unit found by MFL code. Each report line is mapped to its data element.
Every return can be previewed and dry-run before it is sent. Returns go only after the facility has filed them, so a records officer reviews every number before it leaves the building. Lines the facility does not collect are left blank, never sent as zero.
Surveillance
IDSR thresholds turn the weekly return into an early warning. When coded diagnoses for a notifiable disease cross the facility's threshold, a breach is raised, escalated to the registered surveillance contacts, and kept open until a response is recorded. Our guide to IDSR weekly reporting covers what facilities are expected to report and when.
Why this matters beyond compliance
When the return comes from the record, the data the county sees is the data the facility runs on. Workload numbers that support a staffing request, morbidity trends that justify a drug order, and a surveillance signal that arrives in days rather than at month end all depend on that.
For how the returns fit together, read our guide to KHIS monthly reporting. Reporting is part of the hospital management system; register your facility to see your own returns.
Frequently asked questions
- Does it submit straight to KHIS?
- Yes, once a facility has connected its KHIS account and mapped the report lines to its data elements. Every submission can be previewed and run as a dry run first. A return is sent only after it has been filed by the facility, so a records officer always checks it before it leaves.
- Where do the numbers come from?
- From the clinical record. A diagnosis recorded at consultation is counted on the 705 line it maps to; an immunisation given is counted on the 711. Nobody tallies a register at month end, which is where most reporting errors come from.
- What happens to lines we do not collect?
- They are reported as not collected, never as zero. A zero tells the county that nothing happened; a blank tells it the data is held somewhere else. For example, HIV programme indicators reported through other systems are left blank on MOH 711.
- How does IDSR alerting work?
- Each notifiable disease has a threshold, either a case count or a rise above the baseline. The national defaults are loaded unconfirmed and the facility confirms or adjusts them. When coded diagnoses cross a threshold, a breach is raised and escalated to the surveillance contacts the facility has registered, and it stays open until someone records the response.
Other solutions
- Hospital Management System for Kenyan Hospitals
- Pharmacy Management System for Kenyan Pharmacies
- SHA and NHIF Claims Software for Kenya
- Laboratory Information System for Kenyan Facilities
- Telemedicine Software for Kenyan Clinics and Hospitals
- Electronic Medical Records for Kenyan Facilities
- Rehab Centre and Mental Health Software for Kenyan Facilities
- Maternity and MCH Software for Kenyan Facilities
- Diabetes and Hypertension Clinic Software for Kenya
- Hospital Queue and Patient Flow Management for Kenya