Skip to content

Main content

Prescription Record Status Conflict Tool

Audit literal administrative record statuses without determining prescription validity or dispensing authority.

Loading tool…

Description

Find conflicting status labels for prescription-record IDs.

Pharmacy administration separates inventory, document identity, authorization, service timing and financial records from clinical decisions. Matching labels or a positive local predicate can reconcile supplied metadata without authenticating medicine, establishing lawful supply or determining appropriate care.

Find conflicting status labels for prescription-record IDs.

When to use this tool

Use Prescription Record Status Conflict when checking the stated pharmacy record, inventory, timing, coverage or cost convention.

How to use the tool and how it works

  1. Enter recordIds, statuses. Keep parallel arrays aligned. 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 conflictingIds, duplicateRows. Use the output convention below.

Find conflicting status labels for prescription-record IDs. Require aligned recordIds/statuses; group distinct status labels per ID, return IDs with multiple statuses and count duplicate identical ID/status rows.1

Input fieldMeaning and unitsAccepted input
recordIdsRecord IdsRequired. Array of text; maximum UTF-16 length 8192; maximum items 256.
statusesStatusesRequired. Array of text; maximum UTF-16 length 8192; maximum items 256.
Output fieldInterpretationReturned shape
conflictingIdsConflicting IdsRequired. Array of text; maximum UTF-16 length 8192; maximum items 256.
duplicateRowsDuplicate RowsRequired. Safe integer.
json
{
  "input": {
    "recordIds": [
      "R1",
      "R1",
      "R2"
    ],
    "statuses": [
      "open",
      "closed",
      "open"
    ]
  },
  "output": {
    "conflictingIds": [
      "R1"
    ],
    "duplicateRows": 0
  }
}

Limitations and assumptions

  • Status semantics and actual prescription validity are not verified; conflict is literal label disagreement.
  • 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 verified medicine/service records and applicable professional procedures; consult a qualified pharmacist or other appropriate professional for clinical, legal or safe-supply decisions.

References

  1. Calculation and input contract: community-pharmacy/prescription-record-status-conflict — tool.io

Similar or alternative tools