# KHIS Monthly Reporting for Kenyan Facilities: MOH 705, 711, 717 and 706 > What each monthly MOH return contains, why the numbers so often disagree with the facility's own records, and how to produce them from the clinical record instead of tally sheets. Source: https://www.afyaconnect.africa/resources/khis-moh-705-711-monthly-reporting-guide Last updated: 2026-10-19 Publisher: AfyaConnect HMS (Neurobyte Technologies), Nairobi, Kenya --- *Reporting · 8 min read · Updated 2026-10-19* What each monthly MOH return contains, why the numbers so often disagree with the facility's own records, and how to produce them from the clinical record instead of tally sheets. Every public facility in Kenya, and every private facility that reports into the national system, sends a set of monthly returns to the **Kenya Health Information System (KHIS)**. KHIS is Kenya's instance of DHIS2, the open-source platform many ministries of health use. The returns are how the county and the Ministry know what is happening at your facility: the diseases seen, the services delivered, the workload carried. For most facilities the returns are also a monthly ordeal. This guide explains what each return contains and how to make it a report rather than a project. ## The core monthly returns ### MOH 705A and MOH 705B: outpatient morbidity The 705 returns count outpatient diagnoses by disease. **705A** covers children under five and **705B** covers everyone five and over. Each line is a disease or condition, and the count is new cases seen that month. Accuracy depends entirely on diagnosis. A visit recorded as "fever" with no diagnosis cannot be counted on a disease line, and a diagnosis written in free text has to be interpreted by whoever is tallying. ### MOH 711: reproductive and child health The 711 is the integrated summary for reproductive, maternal and child health: antenatal care, deliveries, postnatal care, family planning, immunisation, growth monitoring and related services. It draws on several registers at once, which is why it is often the hardest return to compile by hand. ### MOH 717: service workload The 717 counts the work the facility did: outpatient attendances, admissions, procedures and services by department. It is the return that supports a case for more staff or a bigger budget. ### MOH 706: laboratory The 706 summarises laboratory tests performed and their results by test type. ## Why the numbers go wrong The returns are usually compiled by a health records officer working from paper registers and tally sheets in the first days of the month. The errors are predictable: - **Double counting** when a patient appears in two registers. - **Missed counts** when a register page is incomplete or a service point kept its own book. - **Interpretation** when a diagnosis has to be guessed from handwriting. - **Zero versus blank.** A zero says nothing happened. A blank says the data is not collected here. Reporting zero for a service the facility simply did not record distorts the county's picture. The deeper problem is that the return and the clinical record are two separate data sets that nobody reconciles. ## Producing the returns from the record The fix is to count the returns from the same data clinicians already record: - **Code the diagnosis at the consultation**, in ICD-11, with each code mapped to its MOH 705 line. The count is then a query, not a tally. - **Record services in registers that the system understands**, so an immunisation given is counted on the 711 automatically. - **Keep the records officer in charge.** The system compiles the return; the officer checks it, files it and submits it. Automation should remove the arithmetic, not the review. - **Submit to KHIS directly**, mapping each line to its KHIS data element and the facility's organisation unit, with a dry run before the real submission. ## Deadlines Returns are due early in the following month. The exact deadline is set by your sub-county health records and information officer, so confirm it locally; late reporting shows up on the county's completeness and timeliness dashboard. ## Weekly surveillance is different The IDSR weekly report runs on a different cycle and has different rules, including the requirement to report zero cases explicitly. See our [guide to IDSR weekly reporting](/resources/idsr-weekly-reporting-kenya-facilities). ## How AfyaConnect handles it AfyaConnect compiles MOH 705A, 705B, 711, 717 and 706 from the clinical record and submits them to KHIS once the facility has connected its account and mapped its data elements. A return goes only after the facility has filed it, and lines the facility does not collect are left blank, never sent as zero. See [KHIS and MOH reporting software](/solutions/khis-dhis2-moh-reporting-software-kenya) for the detail. --- **Author:** The AfyaConnect Clinical & Product Team — Health systems and product engineering, Neurobyte Technologies The team that builds and supports AfyaConnect writes these guides. Everything here is written against software we actually ship and support in live Kenyan facilities — the SHA claims flow, the PPB controlled substances register and the eTIMS invoicing described in these guides are modules we maintain, not features we read about. Where regulation is still moving, we say so rather than guessing. - Supports 40+ healthcare facilities across Kenya and East Africa - Builds and maintains the SHA/NHIF claims, PPB register and KRA eTIMS modules described in these guides - Works to the Kenya Data Protection Act 2019 and Digital Health Act 2023 requirements for patient data Last reviewed: 2026-10-19