Reporting: Implementation Configurations in my reports
Description
QAlity Plus - Test Management
Checklists
Activity
Josh Zamor
At the time of this writing we're simply noting that in the future we'd like to have a solution for managing self-service reporting where there are configurations that implementers might choose in OpenLMIS that make finding the semantics in specific reporting less than straightforward.
Some solutions we've discussed to date:
Flags - a flag is hardcoded into the transaction system (OpenLMIS), and user's may toggle it when they define a piece of configuration in those admin screens. e.g. This stock adjustment reason IS A closed vial wastage. In reporting we'd look for those hard-coded flags. The downside is that I expect these tags to multiply quickly and it takes a SDE to change both systems.
Tags - a tag is a free-form entity that a user of OpenLMIS may use to tag a particular piece of configuration. e.g. I could define a tag ClosedVialWastage and then tag each Stock Adjustment Reason which is that, with that tag. In reporting we'd hard-code or expose those tags, instead of individual reasons. Downside is that it might require an SDE to change the reporting queries to understand new tags - ideally the tags are exposed to the user of superset.
Exposed in superset - this is not an either/or with the first 2, but rather calling out that the most flexible approach is to expose this to the superset user without requiring an SDE - if possible and performant.
Defined by a central authority - this is more specific to answering a question such as: does it make sense to report on Open Vial Wastage for this Orderable? Ideally this comes from the Product Master, where the product master attributes guide us to the right answer. For example the above question should be answerable for safety boxes as opposed to vials of BCG when the product masters definition is that the trade item IS A pharmaceutical.
I do not favor flags at this moment and favor tagging along with exposing / surfacing those tags to the superset user. It provides the highest flexibility without requiring an SDE.
As a user of ad-hoc reports, I want the configurable concepts I use in my country to be available in my reports so that I may appropriately select which of these configurable concepts attribute to the various metrics defined in my reports.
Examples of configuration:
Stock adjustment reasons - which ones are Closed Vial Wastage as opposed to Open Vial Wastage?
Orderables - which ones are actually vaccines in a vial as opposed to vaccines in a pill or drop form? Or not vaccines altogether such as Safety Boxes where Open Vial Wastage clearly makes no sense
AC:
TODO