Orderables (Products)

Goals/Scope

The goal of this requirements page is to document the feature of Orderables administration screens and the associated user stories. Administration screens for Orderables allows the administrator to view, edit and research Orderables to assist the administrator with data corrections.

• Scope: This feature includes stories on:
  • View list of Orderables
  • Search for specific Orderables
  • Edit Orderables details
  • View and Edit Associated Lots, Trade Items, and/or CommodityTypes
  • Facility Type Approved Products (this is a separate process not completed through Orderables)
  • Configure Product ISA (This was moved out of Admin screens)

Background

• Version 2 has Products but Version 3 has Orderables, Trade Items, and CommodityTypes

Assumptions

• Potentially hundreds of Orderables per Program that can affect performance

User Stories

1. Admin searches for orderable: 
   1. What information does an admin need to make their search more effective? Why are they searching for orderable? Incorrect associations?
      1. How are orderables, commodity types, and trade items structured in the database for this type of view? What changes need to be made so that we can create a view that has all associations?
   2. Do they need to see Orderable Type?
   3. Sort by Program?
2. Admin adds new orderable
   1. Goes through entire process of determining if this is a commodity type or trade item, then is directed to the page to begin entering required fields, then completing the required associations (programs, trade items, lots)
   2. How do we enable lots for an orderable? Via some module when creating a new orderable?
3. Admin edits existing orderable details:
   1. Following editable fields: Active (what happens if they mark an orderable as inactive?), Full Supply, Display Order, Price per pack, Pack rounding threshold, pack size, round to zero, dispensing unit
   2. Should the admin be able to edit all these fields? Are there any restrictions? Are there any impacts to making edits to fields such as pack rounding threshold during the requisition period?
4. Admin edits existing orderable associations:
   1. change associated trade items?
   2. change associated programs?
   3. change associated lots?

Diagrams

Dependencies

Open Questions

Below is a list of questions to be addressed as a result of this requirements document:

Out of Scope

• Migration from Orderables to a Trade Item or Commodity Type when they are defined (suggestion is that the product would be set up as a new Trade Item or Commodity type but this affects historical reporting on the program).