Skip to content

Main content

Screening Invitation Response Code

Map explicit invitation response codes without determining screening eligibility or interpreting nonresponse.

Loading tool…

Description

Classify a recorded screening-invitation response using two supplied codes.

Public-health data distinguishes assigned case definitions, invitation responses, missing codes, repeat attendances and population denominators. A display-suppression rule changes visible text without necessarily preventing re-identification. Administrative labels and local summaries require verified study, privacy and clinical context before they can support population-health decisions.

Classify a recorded screening-invitation response using two supplied codes.

When to use this tool

Use Screening Invitation Response Code when you already have invitationId, responseCode, acceptedCode, declinedCode and need to classify a recorded screening-invitation response using two supplied codes.

How to use the tool and how it works

  1. Enter invitationId, responseCode, acceptedCode, declinedCode. 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 status. Use the output convention below.

Require invitationId nonempty and acceptedCode!=declinedCode. Return recorded-accepted, recorded-declined or other-or-unrecorded by literal equality.1

Input fieldMeaning and unitsAccepted input
invitationIdInvitation IdRequired. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192.
responseCodeResponse CodeRequired. Text; maximum UTF-16 length 8192.
acceptedCodeMust differ from declinedCode; empty tokens are not independently forbidden by this comparator.Required. Text; maximum UTF-16 length 8192.
declinedCodeDeclined CodeRequired. Text; maximum UTF-16 length 8192.
Output fieldInterpretationReturned shape
statusStatusRequired. Text; maximum UTF-16 length 8192.
json
{
  "input": {
    "invitationId": "I17",
    "responseCode": "Y",
    "acceptedCode": "Y",
    "declinedCode": "N"
  },
  "output": {
    "status": "recorded-accepted"
  }
}

Limitations and assumptions

  • Codes may be empty when otherwise allowed; an invitation response does not establish valid consent, attendance or screening suitability.
  • 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 surveillance definition, survey codebook and population frame for actual counts and classifications. Assess disclosure controls across the full released dataset, including linked totals and repeated queries, rather than relying on one small-cell display rule.

References

  1. Calculation and input contract: public-health/screening-invitation-response-code — tool.io

Similar or alternative tools