Day Three Positivity Screen

Screen observed day-three positivity against an explicit surveillance cutoff; does not establish resistance.

Description

Day-three positivity summarizes how many assessed participants remain positive at that follow-up.

Day-three positivity summarizes how many assessed participants remain positive at that follow-up. A surveillance trigger can compare this proportion with a caller-selected boundary.

The tool returns dayThreePositivePercent (day three positive percent); exceedsSurveillanceCutoff (exceeds surveillance cutoff). Input measurements and model parameters are supplied by the caller; the tool computes the stated summary rather than acquiring those measurements.

When to use Day Three Positivity Screen

Use Day Three Positivity Screen when you already have dayThreePositive, dayThreeAssessed, maximumPositiveFraction and want dayThreePositivePercent, exceedsSurveillanceCutoff. This is useful for checking a supplied calculation, documenting a measurement convention, or comparing observations prepared on the same basis.

How to use Day Three Positivity Screen and understand its results

Enter dayThreePositive, dayThreeAssessed, maximumPositiveFraction using the field table below. Match the units, ordering and data boundaries described in the calculation.
Run the tool after checking the stated bounds and matching paired observations or categories. A malformed request gives a tool error rather than a usable measurement.
Read dayThreePositivePercent, exceedsSurveillanceCutoff. Use the calculation and interpretation below to distinguish amounts, ratios, signs and decision flags where applicable.
Review the supplied parameters and assumptions before using the result in a report or comparing it with another observation.

Input field	Meaning	Value type and bounds	Requirement
dayThreePositive	Day three positive	integer	Required
dayThreeAssessed	Day three assessed	integer	Required
maximumPositiveFraction	Maximum positive fraction	number	Required

Validate positive counts against a positive assessed count and use a strict greater-than comparison. Equality is not an exceedance.

positivity% = 100 × positives/assessed; exceeds = fraction > threshold

The symbols refer to the supplied quantities or generated values described above; unit conversions and comparison boundaries follow the stated implementation.

json

{
  "input": {
    "dayThreePositive": 8,
    "dayThreeAssessed": 100,
    "maximumPositiveFraction": 0.05
  },
  "output": {
    "dayThreePositivePercent": 8,
    "exceedsSurveillanceCutoff": true
  }
}

Limitations and assumptions

This does not infer the cause of persistent positivity or establish drug resistance. Missing follow-ups and assay limitations are not adjusted.

Numerical inputs must be finite. The tool checks its declared input shape and calculation constraints; those checks do not verify the quality, calibration or representativeness of the supplied observations.

Alternative or Complementary methods

Microfilaremia Prevalence Screen: Screen observed microfilaremia prevalence against a supplied limit; does not certify elimination. K13 Marker Match: Match observed K13 marker annotations against a caller-supplied concern set; no embedded resistance catalog.

Methodological background: Malaria: artemisinin partial resistance.^[1]

References

Malaria: artemisinin partial resistance — World Health Organization

Similar or alternative tools

Microfilaremia Prevalence Screen
Screen observed microfilaremia prevalence against a supplied limit; does not certify elimination.
K13 Marker Match
Match observed K13 marker annotations against a caller-supplied concern set; no embedded resistance catalog.