Information Technology
Common Requirements for Logistics Management Information Systems
This document is intended to bridge the language and discipline of global health with the language and discipline of software and system engineering. The focus of this work was on the creation of a methodology for producing descriptions, models, and figures that accurately represented the views and needs of global health professionals. This document describes this methodology and as such can be used by global health practitioners who are interested in applying it to inform software development related to health systems.
This document also presents a set of descriptions, models, and figures that were produced as a result of the methodology being applied in supply chain and more specifically in logistics management. These artifacts are intended to be useful in discussions between health professionals and suppliers of logistics management information systems. This document does not intend to be a definitive authority on the discipline of logistics management or to provide guidance on how to organize and manage the logistics function within a country. This work was informed by supply chain and logistics management experts. The References and Additional Resources section of this report presents some of the work of these experts in the health system domain of supply chain.
This document is designed to be both a road map and a tool. It serves as a road map for helping ministries of health (MOH) move toward the vision of an effective LMIS as expressed in this document. At the same time, it is a tool for structuring specific implementation projects, informing vendor requests for proposals (RFPs), self assessing existing LMIS capabilities, and providing a methodology that is repeatable in other health system domains. It does not provide the technical specifications for an information system that are often used for designing and writing software applications. MOHs are encouraged to customize or adapt this document to meet local needs. They can modify the business process sections by adding specific or unique requirements and deleting business processes not under their jurisdiction.
No copy data
No other version available