LMIS vs HMIS in Nepal: What Each System Measures and Why They Must Connect
A clear comparison of logistics and health management information systems, their core data, decision cycles and safe integration in Nepal.
Editorial context
Developed from uploaded LMIS teaching notes and two historical diagrams. Their former reporting lines and fixed quarterly schedules are preserved as archival examples, not current operating instructions; Nepal’s digital and federal arrangements continue to evolve.
Key points
- HMIS describes health services and population-health results; LMIS describes health commodities and their movement.
- LMIS decisions are often operational and time-sensitive because a stock-out can interrupt care immediately.
- The systems should connect through governed identifiers and definitions, not duplicate every record.
- Daily source records may feed reporting at different intervals; current schedules must be confirmed officially.
- Good dashboards pair data with responsibility, feedback and documented action.
The simplest distinction
A health management information system records information about services, conditions, coverage and outcomes. A logistics management information system records information about products: what was received, issued, used, lost, adjusted, ordered and remains available.
The boundary is practical rather than absolute. Both support management, and both may share facility, programme and time-period identifiers. Their different purposes determine which data are collected and how quickly managers need to act.
- HMIS question: What services were delivered, to whom and with what result?
- LMIS question: Are the products required for those services available, safe and in the right place?
- Combined question: Did commodity availability help or constrain service delivery?
Core LMIS data and decisions
For each product and location, an LMIS commonly needs beginning balance, receipts, issues or consumption, losses and adjustments, and usable stock on hand. Orders in transit, lead time, expiry and days out of stock may also be needed.
These data support stock-status assessment, resupply, redistribution, forecasting, quantification, procurement and expiry control. Managers should act at the level closest to the problem while escalating risks that cannot be solved locally.
How the decision rhythm differs
Both systems may record events daily and compile reports periodically. However, logistics data often require immediate review: a low balance, cold-chain excursion, recall or delayed shipment cannot safely wait for a quarterly analysis.
HMIS trends may be reviewed monthly, quarterly or annually depending on the indicator and decision. Fixed schedules shown in older diagrams should not be assumed to apply today; users must follow the current programme and platform requirements.
Connect systems without creating confusion
HMIS and LMIS are more useful together when common facility codes, product and service definitions, reporting periods and governance rules are aligned. Integration can show whether service changes reflect demand, reporting behaviour or commodity availability.
Connection does not mean combining all personal and supply data in one unrestricted file. Use the minimum necessary information, role-based access, audit trails and documented data stewardship. Aggregate commodity analysis usually does not require patient identifiers.
- Use one authoritative facility identifier across systems.
- Maintain controlled product and indicator catalogues.
- Define ownership for correction and approval.
- Reconcile unusual service and consumption patterns.
- Protect confidentiality and limit access by role.
Reading Nepal’s historical LMIS diagrams
The uploaded reporting chart shows health posts and other service points sending forms through district and regional structures to a central logistics unit, with feedback moving back through the system. It is useful for understanding that reporting must be two-way, but the organizational labels predate federal restructuring.
The accompanying 2007/08 report documents earlier procurement, training, store construction and web-LMIS initiatives. Its targets, budgets, coverage percentages and named offices are historical evidence only and should not be quoted as current performance.
A practical review checklist
When reviewing an HMIS or LMIS report, first identify the decision it should support. Check completeness, timeliness, internal consistency and unusual changes, then compare related measures and document action.
- Is the facility, product or indicator code correct?
- Do opening balance, receipts, issues and closing balance reconcile?
- Could a service increase explain higher commodity use?
- Could a stock-out explain an apparent service decline?
- Who will act, by when, and how will feedback return?
Sources and further reading
Use the linked institutions for current definitions, regulations, programmes and statistics.
- Nepal Integrated Health Management Information System
Official portal for current HMIS resources and reporting context.
- Nepal Digital Health Platform
National direction for interoperability among digital health systems.
- Department of Health Services Nepal
Official source for current programme, logistics and annual-report materials.
- USAID Global Health Supply Chain: Nepal
Supply-chain strengthening and eLMIS programme context.
- UNICEF: Nepal Health Information System case study
Review of Nepal’s health-information ecosystem, governance and data use.
- WHO: SCORE for Health Data Technical Package
Framework for improving health data systems and use.
Related learning note
Health Systems & DataHealth Management Information System in Nepal: Data to DecisionsA practical guide to HMIS in Nepal: data collection, quality, reporting, interpretation and responsible use for planning and improving health services.Educational notice: This article summarizes historical and public-health material. It does not replace current national protocols, clinical judgement or care from a qualified professional.