Skip to content

Main content

Case Component Match Count Tool

Count explicit known case-component matches without determining a clinical case definition.

Loading tool…

Description

Count matched entries only where both flags are true, knownCount where known is true, and unknownCount where known is false.

Case-definition records combine criteria, knowledge flags, document versions and date applicability. A component can be unknown rather than false, and literal agreement with supplied rules is separate from independent clinical classification.

Count matched entries only where both flags are true, knownCount where known is true, and unknownCount where known is false.

When to use this tool

Use Case Component Match Count when checking a stated rule, its known components or its supplied version interval.

How to use the tool and how it works

  1. Enter matches, known. Keep parallel arrays aligned. 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 matched, knownCount, unknownCount. Use the output convention below.

Require matches and known arrays of equal length. Count matched entries only where both flags are true, knownCount where known is true, and unknownCount where known is false. Each aligned position represents one supplied component or record.1

Input fieldMeaning and unitsAccepted input
matchesMatchesRequired. Array of boolean; maximum items 256.
knownKnownRequired. Array of boolean; maximum items 256.
Output fieldInterpretationReturned shape
matchedMatchedRequired. Safe integer.
knownCountKnown CountRequired. Safe integer.
unknownCountUnknown CountRequired. Safe integer.
json
{
  "input": {
    "matches": [
      true,
      true,
      false
    ],
    "known": [
      true,
      false,
      true
    ]
  },
  "output": {
    "matched": 1,
    "knownCount": 2,
    "unknownCount": 1
  }
}

Limitations and assumptions

  • Empty arrays return zero counts. A true match flag attached to an unknown component does not count; the tool neither combines criteria into a case definition nor deduplicates records.
  • 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.

Alternative or Complementary methods

Review the authoritative case definition and original records; local boolean or version checks cannot establish the completeness or suitability of the definition.

References

  1. Calculation and input contract: epidemiology/case-component-match-count — tool.io

Similar or alternative tools

  • Cohort Event Exposure Fraction

    Return fraction = events/exposedPersons when exposedPersons is positive, otherwise fraction = 0 and defined = false.

  • Case Definition Component Flag

    In requireAll mode, a known false component resolves the rule as false and all known true components resolve it as true; otherwise it remains unknown.