...
In other words, it is data that is not tied to the OpenLMIS system (its business logic, calculations, notifications). The timing of when this data is received can be asynchronous (collected at a different time).
We may decide to pick a different name. Examples: user-defined data, custom data, non-logistics data, non-stock data, un-actionable data.
There may also be a Program Data Persona who is the sort of person who defines what fields of information are collected. They are interested in getting this data so it's available for reporting, decision-making and analysis.
...
| # | Question | Outcome | Status |
|---|---|---|---|
| 1 | When stock transactions are captured, such as the SIIL/SELV EPI tabs or the VIMS Stock Status tab, does it generate stock card line items in the software? Or is it just captured as a monthly report that is visible for reporting but not in the system as a stock event/line item? (Josh talked about low-fidelity data that is not appropriate for populating our stock cards.) | Open | |
| 2 | Should we change our terminology to call it something other than "program data"? (See notes above in "What is Program Data?" section) | Open |