Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Ideal Stock Amount is a yearly estimate of the “target” number of doses of a vaccine you should have based off of your population served (i.e. catchment population). This model for estimating the number of vaccine doses you need is irrespective of vial size, packaging, manufacturer, etc so that you focus on a single number of doses that you should have at any given time. For more rural service delivery points, this time is typically the number of doses you should have in a year, divided by 12 months with the idea that your refrigerator can only hold up to about a month's worth of vaccines at a time. The Ideal Stock Amount (ISA) is defined configured by the Facility Operator or Implementor Implementer/Administrator and can be used in reorder calculations for OpenLMIS. 

...

Issue is a type of stock movement that happens when a facility needs to issue stock that isn't requested through the regular requisition workflow.

Anchor
Issue
Issue

Order

An Order is a requisition that has completed the approval process and is ready to be fulfilled.

...

Orderables

...

Local Fulfillment

Local Fulfillment is the process of fulfilling an order locally because the facility has adequate cold-storage capacity. So in this case the order will not need to be fulfilled externally (by a national warehouse).

Anchor
Local Fulfillment
Local Fulfillment

Order

An Order is a requisition that has completed the approval process, converted to an order (manually by a user or automatically by system configuration), and is ready to be fulfilled.

Anchor
Order
Order

Orderables

An Orderable represents any item that may be ordered. For example, an item may be ordered on a Requisition form by a storeroom manager in a medical facility. An Orderable in OpenLMIS 3.0 must be connected to either a TradeItem (a specific item by a manufacturer/brand owner) or to a CommodityType (one category of medicines or commodities). Each of those is described further below.
An Orderable is identified uniquely within an implementation by its Product Code. A Product Code is an implementation specific identifier that assists people filling out paper forms as well as external systems all reference the same commodity that may be ordered. Orderable's may also answer a number of questions that typically arise when one needs to order them:

...

Rights are specific user actions that are enabled through the assignment of a role. There are default rights for each role. Rights are broken into types and the types supported are requisition, fulfillment, supervisory, admin, and reports.
Requisition Rights are associated with Requisition-based programs and allow a user to initiate, update, submit, approve, authorize, delete, and view requisitions. For example, the Requisition-based programs role includes rights for creating, authorizing, and approving requisitions. In some cases, a single user may only be given access to create with a separate user required to authorize and approve. Rights are typically 1:1 where one right as described will equal the capability in the system. For example, the right to view requisitions gives you the ability to view requisitions. Except in some scenarios there are additional rights allowed. For example, the create requisition right allows a user to initiate, update, submit, view, and delete a requisition in OpenLMIS.

  • Fulfillment rights are associated with a Facility where order fulfillment capabilities are allowed. The type of facility allowed to have fulfillment based rights are ones that supply others; such as a warehouse type facility.
  • Supervisory Rights are used in a variety of situations where we'd like to give a user some capabilities within an administrative hierarchy, typically to some aspect of the supply chain focused at Facilities, divided by Program. While Supervisory Rights typically need to be associated to a user by a Supervisory Node and Program, if a user has a Home Facility, then rights of this type can actually be applied directly to that Facility by Program. When these rights are applied directly to a User's Home Facility, then we don't have to reason about any administrative hierarchies. However most of the time we consider supervisory rights, we have to reason about the hierarchy they might apply to given the structure defined by the Supervisory Nodes and Programs they are assigned by. (Since most facilities do not have supervisory rights associated to them a Supervisory Node must always be assigned to a facility.)
  • Admin Rights are not associated to a single Program or Facility, and follow the 1:1 assignment and capability. Admin rights are assigned to enable a user to complete administration type functions such as updating system settings, or editing user details within the system.
  • Report Rights are used to provide users with access to view standard reporting or edit the report templates.

...

Roles

Users' permissions in OpenLMIS are based on assigning them to one or more roles. Roles in turn, are custom-configured by an administrator, and are combinations of one or more rights available in OpenLMIS. Rights relate to individual actions that a user can take, such as view a report, or create a requisition. OpenLMIS classifies rights into five different categories:

...

A detailed explanation of roles are rights and how they are used in the system is located here: Role Based Access Control.

Anchor
Rights
Rights

Roles

Users' permissions in OpenLMIS are based on assigning them to one or more roles. Roles in turn, are custom-configured by an administrator, and are combinations of one or more rights available in OpenLMIS. Rights relate to individual actions that a user can take, such as view a report, or create a requisition. OpenLMIS classifies rights into five different categories: Supervision, Fulfillment, Reports, Administration.

When assigning a role to a user, only the role-based rights are available to allocate to that specific user. A user can have multiple role assignments for a program especially in the case where a user creates and approves requisitions, as well as views reports. A detailed explanation of roles are rights and how they are used in the system is located here: Role Based Access Control.

Anchor
Roles
Roles

Stock Cards

...