Skip to content

Main content

Notice Language Coverage Share Tool

Compare one public notice package’s supplied language support against its explicit required language list.

Loading tool…

Description

Compare one public notice package’s supplied language support against its explicit required language list.

Public-health summaries depend on who is counted, which observations are verified, and the period and population used as the base. Shares, weighted contributions, and inventory balances describe supplied records; they do not by themselves establish a health outcome or a clinical recommendation.

Compare one public notice package’s supplied language support against its explicit required language list.

When to use this tool

Use it for notice language coverage share when the required inputs and conventions are already available.

How to use the tool and how it works

  1. Enter requiredLanguages, supportedLanguages. Keep parallel arrays aligned and use the stated units and conventions.
  2. Run the calculation. Correct any input error before interpreting a result.
  3. Read requiredCount, supportedRequiredCount, missingLanguages, coverage, defined. Inspect any known, defined, inclusion, or boundary flags before interpreting numeric values.

Deduplicate requiredLanguages, list those absent from supportedLanguages, and return requiredCount, supportedRequiredCount, and coverage when requirements are nonempty.1

Input fieldMeaning and unitsAccepted input
requiredLanguagesRequired LanguagesRequired. Array of Text; maximum UTF-16 length 8192.; maximum items 256.
supportedLanguagesSupported LanguagesRequired. Array of Text; maximum UTF-16 length 8192.; maximum items 256.
Output fieldInterpretationReturned shape
requiredCountRequired CountRequired. Safe integer.
supportedRequiredCountSupported Required CountRequired. Safe integer.
missingLanguagesMissing LanguagesRequired. Array of Text; maximum UTF-16 length 8192.; maximum items 256.
coverageCoverageRequired. Finite number.
definedWhether the associated denominator or quantity is defined; read this before interpreting a zero placeholder.Required. Boolean.
json
{
  "input": {
    "requiredLanguages": [
      "L1",
      "L2",
      "L3",
      "L3"
    ],
    "supportedLanguages": [
      "L1",
      "L3"
    ]
  },
  "output": {
    "requiredCount": 3,
    "supportedRequiredCount": 2,
    "missingLanguages": [
      "L2"
    ],
    "coverage": 0.6666666666666666,
    "defined": true
  }
}

Limitations and assumptions

  • An empty requirement set gives coverage zero with defined false. Language labels are compared exactly; content quality, translation accuracy, literacy, and accessible delivery are not assessed.
  • The field tables describe structural bounds; the mechanics also state cross-field requirements. Malformed input shapes, disallowed keys, and invalid domains cause input errors. Results must remain finite and within the declared output contract. A successful false flag or zero placeholder is distinct from an error.
  • Numeric arithmetic uses binary floating point. Exact comparisons have no hidden tolerance or decimal rounding; negative zero is exported as zero. Decimal-text integer operations retain the exactness specifically stated above.

Alternative or Complementary methods

For notice language coverage share, check the source records and the supplied rule before comparing the result with another method. Use an appropriately validated measurement or analysis method for clinical interpretation.

References

  1. Calculation and input contract: public-health/notice-language-coverage-share — tool.io

Similar or alternative tools