AI for hospital supply chain
Hospitals know what they bought. Almost none know what they used.
Pare is a supply ledger for hospitals and surgery centers. It records what comes in and what gets used, reconciles the two, and shows you the gap. It starts at the loading dock, with a phone.
- No patient data
- No contract pricing
- No system integration to start
- Live in weeks, not quarters
Step 1 — the slip
Packing slip · PO 4471-B
Distributor · 3 cartons
- IV start kit, 20g5 CS
- Chloraprep 26mL4 CS
- Gauze 4×4 sterile12 CS
- Suction canister 1200cc6 CS
◉ Captured · 11 seconds · queued offline
Step 2 — matched against the PO
- IV start kit, 20g5 / 5Match
- Chloraprep 26mL4 / 4Match
- Gauze 4×4 sterile9 / 12Short 3
- Suction canister 1200cc6 / 6Match
⚑ Discrepancy logged with photograph · ready for a vendor claim
Illustrative interface. Figures shown are sample data, not a customer result.
The problem
The ledger only has one side
Purchase orders tell you what you ordered. Invoices tell you what you were billed. Nothing tells you what actually arrived, what sat on the shelf until it expired, or what got consumed on which case. So the gap between those numbers gets absorbed quietly, every month.
Nobody counts the pallet
Deliveries get signed for without a count, because the person signing doesn't personally absorb the loss. Short shipments are paid for. Over shipments are never recorded.
Scanning loses to patient care
Barcode par systems assume someone scans each item. When a nurse grabs seven things during an encounter, that doesn't happen, and the inventory record quietly stops being true.
The smallest sites get the least help
Outpatient centers, emergency departments and surgery centers run on paper and spreadsheets, because enterprise supply platforms are priced and staffed for the main hospital.
What Pare is
A balance sheet for supply
One ledger with two sides. Everything in, everything out, reconciled, so you can see where you're leaking instead of finding out at year end.
Inflow · available now
What came in
Photograph the packing slip at the dock. Pare reads the line items, matches them against the purchase order, and flags every short ship, over ship and wrong-site delivery, with the photograph attached as evidence.
Outflow
RoadmapWhat got used
Consumption read from the documentation clinicians already write, rather than a scan nobody has time for. This requires a data agreement and an EHR interface. It is the second half of the ledger, not a second product.
Two things Pare will not hold
Enforced in the schema, not in a policy document
The fastest security review is the one where the answer is “that data doesn't exist in our system.” Both of these are structural, and we'll show you the schema.
No patient data
There is no field anywhere in the receiving product for a patient, an encounter, a medical record number, or a date of service. It cannot hold protected health information by accident. No BAA required to begin.
No contract pricing
Packing slips carry quantities. Invoices carry prices, and your distributor and GPO pricing is contractually confidential. Pare records units, and leaves the cost column for you to fill in.
Encrypted
TLS in transit, AES-256 at rest, US regions only.
Tenant-isolated
Row-level security at the database, not the application.
Audit-logged
Append-only. Every image view and export is recorded and exportable.
Human-confirmed
Nothing posts without a person. Every flag is overridable.
Who it's for
The sites nobody built software for
Enterprise supply platforms are sold to health systems and deployed at the flagship hospital. The outpatient healthplex, the freestanding emergency department and the surgery center inherit whatever came down from central IT, usually a barcode system nobody has time to use.
Outpatient healthplexes
High SKU variety, unpredictable add-on volume, one supply manager for the whole building.
Emergency departments
Round-the-clock demand that breaks every par level, and no time to scan anything.
Ambulatory surgery centers
Multi-specialty SKU breadth and consignment implant trays that arrive and leave without ever touching a par level.
How it works
One phone, one pallet, no IT project
Median capture under 45 seconds, because a system that's slower than skipping the count will be skipped. The app times itself and reports the number back to you every week.
- 01
Capture
Photograph the packing slip on arrival. Works offline; the loading dock usually has no signal.
- 02
Match
Line items are read and reconciled against the purchase order. Correct pallets need zero taps.
- 03
Flag
Short, over, damaged, wrong item, wrong site. Each with the photograph attached as evidence.
- 04
Reconcile
A monthly one-page report: ordered, received, variance. The document you hand to sourcing.
See it run
One delivery, end to end
Watch the whole loop: capture at the dock, lines matched against the PO, one short flagged with evidence, and the ledger updating itself. A human confirms every line — Pare drafts.
- Capture
- Match
- Flag
- Ledger
Apex Healthplex · Dock 2
Works offline · syncs when signal returns
The dock worker's phone
On hand
Open discrepancies · 0IV start kit, 20g
38CS
Chloraprep 26mL
12CS
Gauze 4×4 sterile
21CS
Suction canister 1200cc
18CS
Ledger · movements today
- Saline 0.9% 1L+6 CSReceipt confirmed
The director's screen — inventory and ledger, updated without a keyboard
A pallet lands. The dock worker opens Pare on the phone.
Illustrative animation. Interface simplified; figures are sample data, not a customer result.
Why now
Everything else needs a project. This needs a pallet.
Enterprise supply platforms
- Months of implementation before value
- Integration-first: IT queue, interfaces, security review
- Six-figure floors that outpatient sites never clear
- Sold to the system, deployed at the flagship hospital
Pare
- Value on the first delivery
- No integration, no PHI, no business-associate agreement to start
- Priced for a single site to approve locally
- Built for the site, and it scales across the network from there
Roadmap
One ledger, built in order
Each phase earns the next. We ship the half that needs nobody's permission first.
Available now
Receiving and the live inventory ledger
Photograph, match, flag, reconcile. No integration, no patient data, no pricing. Live in weeks.
Next
Expiration capture and first-expired-first-out
Photograph lot and expiry on high-value items so the shelf tells you what to use before it turns into a write-off.
Requires a data agreement
Consumption and charge reconciliation
Read what was used from the documentation clinicians already write, and surface billable items the record supports but that were never posted. Every charge traces to a specific line of documentation, and a human confirms before anything posts.
Later
Forecasting, replenishment and vendor claims
Seasonality-aware demand planning from your own history, draft purchase orders for review, and discrepancy claims filed the same day instead of never.
From the field
Built from watching the work, not from a whiteboard
We spent a day shadowing the end-to-end supply workflow at an outpatient and emergency healthplex, from the purchase request, through the sourcing committee and the distributor, to the pallet arriving in the basement and the supplies leaving the closet.
The person counting the pallet doesn't personally feel the loss. The system does. So the count gets skipped, and the discrepancy gets paid for.
That's a workflow-economics problem, not a technology one, which is why the whole product is designed around a single constraint: capturing the delivery has to be faster than not capturing it.
Start here
See what your dock is signing for
A free 30-day receiving audit. Your supply manager photographs and hand-counts every pallet for a month. We turn it into one page: ordered, received, variance, unclaimed. No software to install, no contract, no data leaving your building.