...
Requisition Groups and Members
Supply Lines
Geographic Zones and Levels
User
| id | |
| username | |
| password | |
| firstname | |
| lastname | |
| restrictlogin | does this duplicate active? |
| primarynotificationmethod | consider pulling all notification into its own domain |
| officephone | consider pulling all notification into its own domain |
| cellphone | consider pulling all notification into its own domain |
| consider pulling all notification into its own domain | |
| supervisorid | |
| facilityid | |
| verified | |
| active | |
| preferences | user-specific preference settings |
| roleAssignments | consider pulling some of this functionality out into a supervisions domain |
| implementations should handle these via attributes or json extradata field | |
| employeeid | |
| jobtitle | |
| ismobileuser | |
user_password_reset_tokens
Role
Right
"Product" (Requestable)
Dosage Unit
Product Form
Product Category
Product (Commodity)
Kit
Generic Product/Branded Product
Product "Type" (for impact)
Program Product
Program Product ISA
Program Product Price
Facility (Type) Approved Program Product
Inventory Management
Not all of these may be domain models
Stock Card
Stock Card Entry
Stock Movement
Stock Movement Line Item
Lot (and Lot on Hand?)
Stock Event
Stock Event Type
Stock Adjustment Reason
Shipping/Receiving
Its own context or under Fulfillment context? Currently mentioned under fulfillment
Program Data
Open Questions
Can we merge fulfillment_role_assignments into role_assignments?
...