DATIM issue: OVC SERV Total N (Results vs Targets) calc inconsistent

[shapaklyak]

DATIM: OVC_SERV Total N Targets
Issue: OVC SERV Total Numerator (TOP LEVEL) For FY18 Results and Targets is inconsistent. FY18 Targets it is summing all program status disaggregates (active, grad, exited, transferred), while the FY18 Results sum correctl only the active & graduated disaggregates.
Correction: FY18 Targets should be equal to Active + Grad ONLY
Link: https://www.datim.org/dhis-web-pivot/index.html?id=bQ1me7MAG4o

Status: Spoke w/Jason Pickering at COP week of 3/11; he is fixing this. Kristin R. aware.
Willl follow-up next week.

[shapaklyak]

plus FY19 Targets - same issue

[jb3436]

Update from Katya

Here’s where we landed on the top-level numerator inconsistencies for OVC_SERV’s FY18 and FY19 targets. GitHub ticket here: https://github.com/pepfar-datim/Global/issues/4877.

Per Tim, there are at least two ways to handle this:

1. We could alter the old data, modify it to point at different data elements, update the old data entry forms (a high LOE by itself), and adjusting group-set data elements.
   • Back-of-the-envelope LOE: 3-4 weeks’ worth of development work (testing and approval might take longer)_

2. Couper could create an indicator and a favorite that shows this data in the updated way (i.e., For FY18 and FY19 targets, OVC_SERV’s top-level numerator sums only “active,” “graduated,”).
   • Back-of-the-envelope LOE: about 1 week's worth of development work (testing and approval might take longer)

Next Steps:

1. Couper: Will demonstrate these options (possibly others) for Eda on 5/15
2. Tim : Will further build out the options and associated LOE (as need and as time allows- Couper's demonstrations might suffice and Tim has lots of competing priorities just now)
3. Eda: Will select the option we go with and comment here.
4. Unassigned: Will come up with the canned language or notification associated with the option Eda chooses. Volunteers?
5. Josephine: Will deploy canned language or notification as needed since we’ve had a small number of users report on this issue.