Ask five people in a medical practice what the par level is for gauze, gloves, or suture kits, and you will often get five different numbers — whatever the last person who restocked the shelf felt was "enough." A real par level formula replaces that guesswork with a number tied to actual usage and actual lead time, and it is the first thing that has to be right before any supply-ordering data standard can do its job. Get the formula wrong and even a perfectly integrated ordering system will just order the wrong amount, faster.
The Par Level Formula, Broken Down
The standard par level formula used across healthcare and hospitality supply management is:
Par Level = (Average Daily Usage × Lead Time in Days) + Safety Stock
Each input matters more than it looks:
- Average Daily Usage — the typical number of units consumed per day, pulled from historical usage rather than a guess. A practice that burns through 40 exam gloves a day needs a very different par than one that uses 400.
- Lead Time in Days — the number of days between placing an order and the shipment landing on the shelf. This is the number practices most often get wrong, because they use the distributor’s quoted lead time instead of the lead time they have actually experienced.
- Safety Stock — the buffer that absorbs a bad week: a delivery that is late, a flu spike that doubles glove usage, a distributor backorder. A more precise version of the formula calculates it as (Maximum Daily Usage × Maximum Lead Time) minus (Average Daily Usage × Average Lead Time), which captures the gap between the worst realistic case and the average case rather than a flat percentage.
Setting Min and Max: The Variables That Actually Move the Number
The formula gives you a starting par, but min and max levels for a given item shift based on a handful of practical factors, not a one-size-fits-all cushion:
| Factor | Effect on Par Level |
|---|---|
| Delivery frequency | More frequent deliveries lower the par needed, since less stock has to cover the gap between orders |
| Lead time reliability | Inconsistent or historically late shipments push safety stock higher |
| Item perishability / expiration | Short-shelf-life items need tighter par levels to avoid write-offs, even if that raises stockout risk |
| Storage space | Caps the practical maximum regardless of what the formula recommends |
| Item cost | High-value items often carry a lower safety-stock cushion, since overstocking ties up more capital per unit |
| Demand variability | Seasonal or unpredictable usage (allergy season, injury clusters) widens the gap between average and maximum daily usage |
None of these show up in the raw formula. They are judgment calls a practice manager makes after running the numbers — which is exactly why par levels need periodic review, not a one-time setup.
Where the Formula Meets the Data: GS1 and EDI Standards
A correct par level is only useful if the reorder it triggers reaches the right distributor system cleanly. That is the connective layer where data standards come in, and it is a separate problem from the math above.
On the ordering side, the healthcare supply chain runs on ANSI-developed EDI X12 transaction sets:
- EDI 850 (Purchase Order) — the practice’s order, sent to the distributor.
- EDI 855 (Purchase Order Acknowledgment) — the distributor’s confirmation, or notice of a change or rejection.
- EDI 856 (Advance Ship Notice) — sent before the shipment arrives, so the practice knows what is coming and can reconcile it against inventory.
- EDI 810 (Invoice) — the electronic bill for what was delivered.
On the identification side, GS1 standards make sure the item ordered is the item that arrives. A GTIN (Global Trade Item Number) uniquely identifies the product, manufacturer, and unit of measure, while a GLN (Global Location Number) identifies the practice or delivery location itself. Both feed into the Global Data Synchronization Network (GDSN), which lets a practice and its distributors share the same product data instead of each side maintaining its own item catalog by hand. The Association for Healthcare Resource & Materials Management (AHRMM) is the industry body that has pushed adoption of these standards specifically for healthcare supply chains, distinct from the broader retail-focused GS1 work most practices are more likely to have heard of.
When a practice’s par-level system references a GTIN instead of a distributor’s internal SKU, and the delivery location is tied to a GLN instead of a free-text address, the reorder can move through EDI 850/855/856/810 without a staff member re-keying anything — which is the whole point of connecting par-level math to a data standard in the first place.
A Practical Review Checklist
- Pull 60–90 days of actual usage per item, not a memory-based estimate.
- Track real lead time per distributor and per item, not the quoted lead time on the contract.
- Recalculate safety stock using the max-usage / max-lead-time version of the formula for anything clinically critical.
- Flag high-cost, low-turnover items for a lower cushion; flag high-variability items (seasonal, trauma-related) for a higher one.
- Confirm which items in the practice’s catalog have a GTIN and GLN mapped correctly — a missing or mismatched identifier is a common reason automated reorders silently fail.
- Revisit par levels quarterly, or after any change in patient volume, service line, or distributor.
Getting the Formula and the Standards Working Together
The par level formula is simple arithmetic; the discipline is in feeding it real usage and real lead-time data instead of assumptions, and then making sure the reorder it triggers can actually reach a distributor’s system through GS1 identifiers and EDI transactions rather than a phone call or a fax. Practices that treat these as one project — not "figure out par levels" and separately "get on EDI someday" — are the ones that stop having a supply closet that is either empty or overflowing. For an Arizona practice weighing whether to build this in-house or bring in a vendor who already speaks GS1 and EDI, that is a conversation worth having with a partner who understands both the inventory math and the interoperability layer underneath it.