Skip to content

Main content

Paired Binary Discordance Term Tool

Compute an explicitly continuity-corrected paired-discordance contribution without a p-value or significance rule.

Loading tool…

Description

Return a continuity-adjusted discordant-pair statistic.

Biostatistical terms depend on a declared observation unit, exposure denominator, event order and sampling design. A risk-set flag, paired discordance contribution or support-weight ratio can be computed locally without fitting a survival model, establishing a treatment effect or validating an inferential analysis.

Return a continuity-adjusted discordant-pair statistic.

When to use this tool

Use Paired Binary Discordance Term when checking the stated exposure, event, matched-pair or cluster-support convention.

How to use the tool and how it works

  1. Enter firstOnly, secondOnly, continuityCorrection. Use the units and conventions below.
  2. Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
  3. Read difference, correctedAbsoluteDifference, statistic, defined. Inspect defined before interpreting the associated values.

Return a continuity-adjusted discordant-pair statistic. Require nonnegative whole firstOnly/secondOnly and correction >= 0; difference = first-second, correctedAbsoluteDifference = max(0,abs(difference)-correction), statistic = corrected²/(first+second) or zero with defined false.1

Paired binary discordant counts drive the McNemar statistic. This helper applies the stated nonnegative continuity-correction convention without calculating a p-value or selecting an inferential test.2

Input fieldMeaning and unitsAccepted input
firstOnlyFirst OnlyRequired. Safe integer; minimum 0.
secondOnlySecond OnlyRequired. Safe integer; minimum 0.
continuityCorrectionNonnegative caller-supplied correction on the count scale, not restricted to zero or one.Required. Finite number; minimum 0.
Output fieldInterpretationReturned shape
differenceDifferenceRequired. Finite number.
correctedAbsoluteDifferencemax(0,abs(firstOnly-secondOnly)-correction), using the supplied nonnegative continuityCorrection, which may be fractional.Required. Finite number.
statisticStatisticRequired. Finite number.
definedReporting flag under the explicit denominator or information policy above; inspect any zero placeholder or policy-defined value.Required. Boolean.
json
{
  "input": {
    "firstOnly": 8,
    "secondOnly": 2,
    "continuityCorrection": 1
  },
  "output": {
    "difference": 6,
    "correctedAbsoluteDifference": 5,
    "statistic": 2.5,
    "defined": true
  }
}

Limitations and assumptions

  • The correction is supplied; no p-value, exact test, sample adequacy or clinical meaning is determined.
  • Inputs must satisfy both the field types and the cross-field conditions above. Invalid input causes an error; a successful false flag or documented placeholder is a different result.
  • Numeric calculations use binary floating point unless exact decimal-integer arithmetic is explicitly stated. No hidden measurement tolerance or decimal rounding is added; nonfinite or out-of-contract results are rejected. Numeric signed-zero results are exported as zero.

Alternative or Complementary methods

Analyze complete verified data with a method appropriate to the design and censoring assumptions; assess uncertainty and consult qualified statistical and clinical professionals for health conclusions.

References

  1. Calculation and input contract: biostatistics/paired-binary-discordance-term — tool.io

  2. McNemar test — NIST

Similar or alternative tools