Skip to content

Main content

Community Oral Health Screening Consent Tag Tool

Preserve supplied oral-health screening consent metadata without establishing permission or clinical eligibility.

Loading tool…

Description

Preserve supplied oral-health screening consent metadata.

Dental records depend on surface notation, assessed and excluded denominators, missing versus observed zero, reporting quanta and recorded equipment dates. Calendar-day counts can be elapsed or inclusive, and nominal expiry comparisons do not establish sterility. Local surface fractions and source labels are not automatically validated clinical indices.

Preserve supplied oral-health screening consent metadata.

When to use this tool

Use Community Oral Health Screening Consent Tag when you already have screeningId, participantId, suppliedConsentStatus and need to preserve supplied oral-health screening consent metadata.

How to use the tool and how it works

  1. Enter screeningId, participantId, suppliedConsentStatus. 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 token. Use the output convention below.

Enter screeningId, participantId, suppliedConsentStatus 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 fieldMeaning and unitsAccepted input
screeningIdScreening IdRequired. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192.
participantIdParticipant IdRequired. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192.
suppliedConsentStatusSupplied Consent StatusRequired. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192.
Output fieldInterpretationReturned shape
tokenTokenRequired. Text; maximum UTF-16 length 8192.
json
{
  "input": {
    "screeningId": "S17",
    "participantId": "P4",
    "suppliedConsentStatus": "recorded"
  },
  "output": {
    "token": "[\"S17\",\"P4\",\"recorded\"]"
  }
}

Limitations and assumptions

  • The result records supplied values without establishing permission or clinical eligibility. 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

Use original chart, observation and reprocessing records with the complete scoring or controlled workflow. Keep denominator, missingness and date conventions explicit; local arithmetic does not determine oral-health status, appropriate recall intervals or readiness for care.

References

  1. Calculation and input contract: dental-hygiene/community-oral-health-screening-consent-tag — tool.io

Similar or alternative tools