2020-02-06 Requirements Review
- Ben Leibert
Date
Feb 6, 2020
Participants / Stakeholders
@Felimone Amone Junior
@Matthew Kumbuyo (Deactivated)
@Chongsun Ahn (Unlicensed)
@Ben Leibert
@Vidya Sampath
@Swetha Srinath (Unlicensed)
@Julia Guerette
Notes
So as to avoid confusion, the data-source for any given indicator should be consistent wherever possible. It’s nevertheless alright to have health facilities pull from requisitions while having warehouses pull from stock-management. We should have distinct reports for each of them, however, so as to minimize confusion.
For country-level stock reports it may be necessary to combine data sources (requisitions and stock-management.) In that case, we should use descriptive labels to clearly describe the report’s content.
It’s technically feasible to combine data sources within a single Superset report. This might be done by embedding logic in stored procedures referenced by Superset or by combining data as necessary as part of the ETL process. Both approaches add significant complexity, however, and thus increase developmental and maintenance costs. Wherever possible, we should try to avoid such an approach. We should instead try to design multiple reports, each of which has a dedicated data source.
It may help to distinguish between reports intended for official use and those more suitable for ad-hoc data exploration. Official reports are typically intended for a printed page, timestamped, and implemented in Japser. Our Superset reports, by contrast, are better used for ad-hoc data exploration.
Because facilities submit requisitions no more than once per month, a district-level user trying to redistribute stock amongst them will likely need to call each facility to confirm their current stock levels. For this use case, our reports won’t likely save much time.
It’s not yet clear whether we’ll continue to use Tableau with SELV.