Description
Qualify an explicit over-the-counter ingredient label by version.
Pharmacy records distinguish prescribed wording, recorded supply, package counts, consultation timing and product identifiers. A partial-fill balance can reveal a recorded overfill without determining lawful supply, and a lot-code comparison does not retrieve a recall. Preserving a dose string does not interpret or recommend the dose.
Qualify an explicit over-the-counter ingredient label by version.
When to use this tool
Use OTC Label Ingredient Namespace when you already have productId, ingredientWording, labelVersion and need to qualify an explicit over-the-counter ingredient label by version.
How to use the tool and how it works
- Enter productId, ingredientWording, labelVersion. 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 productId, ingredientWording, labelVersion 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 |
|---|---|---|
| productId | Product Id | Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192. |
| ingredientWording | Ingredient Wording | Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192. |
| labelVersion | Label Version | 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": {
"productId": "PR17",
"ingredientWording": "Ingredient A",
"labelVersion": "v2"
},
"output": {
"token": "[\"PR17\",\"Ingredient A\",\"v2\"]"
}
}Limitations and assumptions
- The result records supplied values without assessing safety or interactions. 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 original prescription, dispensing, consultation and product records within the appropriate professional workflow. Use verified clinical and regulatory information for supply or care decisions; local balances and labels do not establish suitability, authenticity or authorization.
References
Similar or alternative tools
- Community Pharmacy Delivery Receipt Code
Preserve explicit pharmacy-delivery receipt wording and source.
- Refill Contact Preference Token
Record an explicit refill contact preference and source.