Skip to content

Main content

Community Pharmacy Delivery Round Cost Share Tool

Calculate community pharmacy delivery round cost share from explicit caller-supplied inputs.

Loading tool…

Description

Allocate a delivery round's cost to one weighted stop.

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.

Allocate a delivery round's cost to one weighted stop.

When to use this tool

Use Community Pharmacy Delivery Round Cost Share when checking the stated pharmacy record, inventory, timing, coverage or cost convention.

How to use the tool and how it works

  1. Enter stopWeights, totalRoundCost, stopIndex. 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 weightTotal, allocatedCost. Use the output convention below.

Allocate a delivery round's cost to one weighted stop. Require nonempty nonnegative stopWeights with positive total, valid stopIndex and cost >= 0; allocatedCost = totalRoundCost*selectedWeight/sum(weights).1

Input fieldMeaning and unitsAccepted input
stopWeightsStop WeightsRequired. Array of finite number; maximum items 256.
totalRoundCostTotal Round CostRequired. Finite number; minimum 0.
stopIndexStop IndexRequired. Safe integer; minimum 0.
Output fieldInterpretationReturned shape
weightTotalWeight TotalRequired. Finite number.
allocatedCostAllocated CostRequired. Finite number.
json
{
  "input": {
    "stopWeights": [
      1,
      2,
      3
    ],
    "totalRoundCost": 60,
    "stopIndex": 1
  },
  "output": {
    "weightTotal": 6,
    "allocatedCost": 20
  }
}

Limitations and assumptions

  • Weights are supplied rather than an empirical route-cost model; this does not establish reimbursement, billing rights or actual service costs.
  • 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

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/community-pharmacy-delivery-round-cost-share — tool.io

Similar or alternative tools