DHIS2 Z-Score Functions Capped at -3.5 How to Monitor Improvement in Severe Malnutrition Cases?

Implementation - Implémentation
,
2

Hi @hannahchek

Functions are intentionally capped, and you cannot get values below −3.5 from them. This behavior comes from the way DHIS2 implements the WHO growth standard algorithm, not from Android or Tracker limitations.

Recent versions fixed several anthropometry bugs including ANDROAPP-5063, but the −3.5 cap is not a bug. It is part of the function logic shared with the server.

So large DHIS2 nutrition implementations e.g., CMAM trackers typically monitor:

  • Admission criteria
    MUAC
    WFH Z-score < -3
  • Follow-up indicators
    Weight gain (g/kg/day)
    MUAC improvement
    Edema resolution
    % target weight

Not extreme Z-score movement.

Some nutrition programs compute Z-scores using the official WHO software:

  • WHO Anthro
  • ENA for SMART
  • R package zscorer

Then push the full Z-score value into DHIS2 as a data element.

I’m sure you can do it :clap: