Skip to content

Main content

Pharmacy Aseptic Record Label Version Pair Tool

Compare supplied label provenance/version fields without process or product release approval.

Loading tool…

Description

Compare recordId with labelParent and recordVersion with labelVersion, then flag a released record when either comparison fails.

Pharmacy traceability and monitoring records contain versions, time gaps, release flags, and ledger entries. Consistent metadata is useful evidence but does not establish product stability, correct preparation, or authorized release.

Compare recordId with labelParent and recordVersion with labelVersion, then flag a released record when either comparison fails.

When to use this tool

Use Pharmacy Aseptic Record Label Version Pair when you need a narrow pharmacy-record consistency check.

How to use the tool and how it works

  1. Enter recordId, labelParent, recordVersion, labelVersion, released. 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 parentMatches, versionMatches, releasedWithMismatch. Inspect parentMatches, versionMatches, releasedWithMismatch before interpreting the associated values.

Require nonnegative integer versions. Compare recordId with labelParent and recordVersion with labelVersion, then flag a released record when either comparison fails.1

Input fieldMeaning and unitsAccepted input
recordIdRecord IdRequired. Text; maximum UTF-16 length 8192.
labelParentLabel ParentRequired. Text; maximum UTF-16 length 8192.
recordVersionRecord VersionRequired. Safe integer; minimum 0.
labelVersionLabel VersionRequired. Safe integer; minimum 0.
releasedReleasedRequired. Boolean.
Output fieldInterpretationReturned shape
parentMatchesParent MatchesRequired. Boolean.
versionMatchesVersion MatchesRequired. Boolean.
releasedWithMismatchReleased With MismatchRequired. Boolean.
json
{
  "input": {
    "recordId": "R1",
    "labelParent": "R1",
    "recordVersion": 2,
    "labelVersion": 1,
    "released": true
  },
  "output": {
    "parentMatches": true,
    "versionMatches": false,
    "releasedWithMismatch": true
  }
}

Limitations and assumptions

  • Literal matches do not prove correct labeling, authorized release, sterile preparation, or valid source records; released is a supplied flag rather than an action performed by the tool.
  • 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.
  • Numeric calculations use binary floating point unless exact decimal-integer arithmetic is explicitly stated. No hidden measurement tolerance or decimal rounding is added; nonfinite or out-of-contract results are rejected. Numeric signed-zero results are exported as zero.

Alternative or Complementary methods

Review the complete quality and traceability record through the responsible pharmacy process before acting on a discrepancy.

References

  1. Calculation and input contract: hospital-pharmacy/pharmacy-aseptic-record-label-version-pair — tool.io

Similar or alternative tools