Description
Record an explicitly assigned outbreak case status and definition source.
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.
Record an explicitly assigned outbreak case status and definition source.
When to use this tool
Use Outbreak Case Status Label when you already have caseId, assignedStatus, definitionSource and need to record an explicitly assigned outbreak case status and definition source.
How to use the tool and how it works
- Enter caseId, assignedStatus, definitionSource. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read token. Use the output convention below.
Enter caseId, assignedStatus, definitionSource using the field constraints below. Encode these values, in exactly that order, as a JSON array and return the serialized array as text in token. String values are preserved without trimming or external terminology lookup.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| caseId | Case Id | Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192. |
| assignedStatus | Assigned Status | Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192. |
| definitionSource | Definition Source | Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| token | Token | Required. Text; maximum UTF-16 length 8192. |
{
"input": {
"caseId": "C17",
"assignedStatus": "recorded-confirmed",
"definitionSource": "Definition v2"
},
"output": {
"token": "[\"C17\",\"recorded-confirmed\",\"Definition v2\"]"
}
}Limitations and assumptions
- The result records supplied values without classifying a case. Sources and asserted relationships are not independently authenticated.
- 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
Similar or alternative tools
- Health Survey Nonresponse Code
Distinguish missing and refused survey response codes.
- Screening Invitation Response Code
Classify a recorded screening-invitation response using two supplied codes.