Skip to content

Main content

Medicine Source Version Gap Tool

Inspect explicit medicine-reference version metadata without medicine identification or prescribing rules.

Loading tool…

Description

Split a medicine reference at its last version delimiter.

Pharmacy administration distinguishes medicine and document identifiers, service records, stock balances and payment conventions from decisions about care. Literal labels and supplied status flags help reconcile records, while medicine identity, appropriate treatment and actual availability require independent verification.

Split a medicine reference at its last version delimiter.

When to use this tool

Use Medicine Source Version Gap when reconciling the stated pharmacy record, inventory, timing or financial convention.

How to use the tool and how it works

  1. Enter medicineReference, versionDelimiter, expectedVersion. 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 medicineToken, sourceVersion, versionPresent, matchesExpected. Inspect versionPresent, matchesExpected before interpreting the associated values.

Split a medicine reference at its last version delimiter. Require nonempty delimiter; without it retain the reference and empty sourceVersion, otherwise split literally, set versionPresent and compare to expectedVersion.1

Input fieldMeaning and unitsAccepted input
medicineReferenceMedicine ReferenceRequired. Text; maximum UTF-16 length 8192.
versionDelimiterVersion DelimiterRequired. Text; maximum UTF-16 length 8192.
expectedVersionExpected VersionRequired. Text; maximum UTF-16 length 8192.
Output fieldInterpretationReturned shape
medicineTokenMedicine TokenRequired. Text; maximum UTF-16 length 8192.
sourceVersionSource VersionRequired. Text; maximum UTF-16 length 8192.
versionPresentDelimiter occurs, even when one split component is empty.Required. Boolean.
matchesExpectedMatches ExpectedRequired. Boolean.
json
{
  "input": {
    "medicineReference": "med@v2",
    "versionDelimiter": "@",
    "expectedVersion": "v2"
  },
  "output": {
    "medicineToken": "med",
    "sourceVersion": "v2",
    "versionPresent": true,
    "matchesExpected": true
  }
}

Limitations and assumptions

  • Empty version or medicine text can occur when a delimiter is present; no source, medicine or current edition is 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

Inspect verified medicine and service records and the applicable professional procedures; use appropriate clinical systems and qualified professional judgment for care or supply decisions.

References

  1. Calculation and input contract: clinical-pharmacy/medicine-source-version-gap — tool.io

Similar or alternative tools