This build is wired to the Quadcare project. Paste the anon / publishable key to connect — it's safe in the browser now that row-level security is enforced.
Stored only in this browser (localStorage). Nothing is sent anywhere except your own Supabase project. Clear it any time from the account menu.
Quadcare P2P Workspace
Sign in
Use your Quadcare account. What you see is scoped to your own access grants.
Every submitted request with lines still open. Two separate passes. First decide what you are willing to buy and tell the clinic. Then, once you have been through the supplier’s own system, record what they actually gave you — and that becomes the order.
Running low at the clinics
Marked by someone at the clinic. Each goes on the next morning count; the figure counted shows here. A delivery of it at that clinic takes it off this list, or press Dealt with.
Pass one — what you are willing to buy
Change any quantity you disagree with and say why. Agreeing with the clinic needs no reason. Nothing here reaches a supplier: this is your decision, recorded before you speak to anyone, so the clinic can later tell your decision apart from a supplier being short.
The database refused this:
The refusal happened in the database, not here.
Saved.
Pass two — what the supplier actually gave you
Open the supplier’s own system alongside this. Work down the list: choose the pack, say how many packs you actually ordered, and change the product if they gave you something else. A line disappears once you have dealt with it so you can see what is left. One order per supplier — set the supplier and their order number, place it, then change supplier and do the next.
Check the total against theirs
Two systems holding the same order at different values is the thing this catches. Read the total off the supplier’s own screen and type it in. The figure excluding VAT must match exactly — it is a multiplication and cannot drift. The inclusive figure is allowed a couple of cents, because their VAT may be computed per line and ours on the total.
The database refused this:
The refusal happened in the database, not here.
Order placed.
Close these lines off and tell the clinic
Placing an order tells nobody. This does. Every line is closed off — ordered, part-ordered, or not ordered — and appears in the clinic’s list with your reason. A line you never ordered needs a reason: that is the clinic being told no, and it is the one message they will never come looking for. The system suggests each outcome from what was actually ordered; change any of them if the suggestion is wrong.
The database refused this:
The refusal happened in the database, not here.
The clinic has been told.
System Administration
Open or close the system
Closing the system stops people signing in and shows them your message. It does not stop work already under way — anyone already signed in keeps working until they sign out. Close it, then use the list below to see who is still active and ask them to sign out. You keep access while it is closed, because you hold system administration.
The database refused this:
The refusal happened in the database, not here.
Saved.
Who is working right now
Anyone who has done something in the last twelve hours, most recent first. This shows who has ACTED, not who is sitting on a screen — someone part-way through a form with nothing saved will not appear. Idle minutes count from their last action, so a long idle time does not mean they have gone.
Counting areas
The places a counter physically walks through at a clinic — a dispensary, a fridge, a stockroom. These define what a complete count means there: the counter has to say she has finished every one of them before a count can be submitted, which is what makes an item with nothing recorded mean there are none here rather than nobody looked. Head office only.
Add a place
The short code is permanent. A counter’s past readings record it as plain text, so it can never be changed afterwards — if a place is renamed in real life, switch the old one off and add a new one. The label is what the counter sees and can be changed freely.
Dispensary · Fridge · Stockroom · Consulting rooms · Emergency trolley. Anything already here is left alone.
The database refused this:
The refusal happened in the database, not here.
Counting shapes
How a counter is allowed to count a product — a sealed pack of 500, loose tablets, a prepack of 30 made up on site. A shape defined here shows on that product at every clinic. One defined for a single clinic shows there as well as the company ones, never instead of them. Head office only, and the number matters: a shape saying 30 when it holds 100 makes every reading taken with it wrong, and nothing on the tablet would look odd.
—
How often this is counted
A product can sit in more than one band — a vaccine may be both cold chain and high value — and when it does, the shortest interval wins. These are the starting point, not the final answer: the system shortens the interval on its own where a product moves fast, is valuable, keeps coming up wrong, or has stock going missing, and relaxes it again when that stops. Every product must stay in at least one band — with none, it is never put on any sheet at any clinic and nothing says so.
The database refused this:
Add a shape
The number is permanent — it is copied onto every reading taken with this shape, so changing it later would make new counts disagree with old ones under the same name. If it is wrong, switch the shape off and add another.
Where does it apply?
A shape can be attached to one clinic or to every clinic. Ticking several creates a separate shape for each — same name, same number — so switching it off later means switching off each one. That is the honest trade for the occasional case; if it becomes common, tell me and it is worth building properly.
The database refused this:
The refusal happened in the database, not here.
Products nobody counts
A product only reaches a counter if two things have been set up: a shape so she has something to tap — a box, a bottle, a tin — and a counting class so the system knows how often to ask. Missing either, and the product never appears on any sheet at any clinic. No error is raised and every count still reads complete, so the stock figure drifts unchecked and nothing ever says so.
Reading…
Authorise a full stocktake
A clinic cannot start a full stocktake on its own. You authorise one occasion at a time — the authorisation is used up by the count it creates, so a clinic cannot quietly run one every day. A full count takes a clinic out of ordinary counting and, until it has been reviewed, blocks it from starting anything else.
The database refused this:
The refusal happened in the database, not here.
Authorised.
Authorisations outstanding
Granted and not yet used. Each one allows one stocktake.
Recently used
Authorisations that produced a stocktake — when it was authorised and when it was started.
Settings
Every setting the system reads. Changing one takes effect on the next read — nothing needs restarting. Each change is recorded against your name. New settings cannot be created here: a new setting is a build decision, not an admin one.
Dispensing Analysis
Quantities that did not add up
The person was shown what did not add up with the billing and confirmed it.
Running Low
Mark a product as running low
Find it and tap it. It goes on the next morning count, and the buyer sees it in Review & Order.
Unused Steps
A reminder of what each step did. Nothing here can be switched on or removed — that is done with Chat B.
My Dispensing to Check
Tell us what you gave the patient
To Decide
Decide each one
Correct Stock Value
What is being corrected
This puts right what a product is carried at. It does not order, receive or count anything. A correction lands as one movement in the stock ledger, with your name and your reason on it, and it can never be unsaid — only corrected again.
On the shelf now
—
Carried at
—
Which is a unit at
—
Posted
Raise Purchase Order (without clinic request)
New purchase order — without a clinic request
The app performs no checks of its own. It sends what you enter; the database applies the permission, validates every line, and either mints the order or refuses with its reason shown verbatim below.
Product — or free-text description
Qty
Pack size
Price each excl. VAT
Supplier code
Line note
The database refused this order.
The refusal happened in the database, not here — this screen sent your entries and was given the message above.
Order raised and audited. Your purchase order number is:
Quote this number to the supplier, and choose it on the Receive Delivery screen when the stock arrives.
Check it against the supplier’s screen, now, before you close it.
Type the order subtotal excluding VAT as the supplier’s own system shows it. If the two agree, a keying slip on either side would have shown up here. It is not foolproof — two mistakes that cancel out, or the same wrong quantity keyed in both places, will still agree.
The supplier’s document
Deliveries Without an Order
Goods Receiving Exceptions
What Goods Receiving flagged
Every delivery went into stock when it arrived. These are the ones with something unusual about them. Nothing is waiting for you — look, take it up with the clinic or the supplier if you need to, and mark it seen. An item that is not on our product list is answered: it goes into stock only when you say what it is.
The delivery paper
Receive Against Invoice
Goods Receiving
Record a delivery
Image the paper that came with the delivery, choose the order if there is one, and enter what arrived. It goes into stock. Anything unusual is flagged for the buyer — it does not hold the delivery up.
An order names its own supplier. This is asked only where nothing else can name one — and “not recorded” is a legitimate answer: a blank is honest, a wrong name is not.
Add the scan of the invoices (a PDF from the scanner is best) or a phone photo. The system reads it and fills in the lines below for you to check and tick. It is also kept as proof of delivery and shown underneath while you work.
Choose a purchase order above and its items appear below — just enter what actually arrived. Batch and expiry are optional.
The price field records what the DELIVERY NOTE says, not what was agreed. The order already carries the agreed price and the stock is valued from it, so leave the price blank unless the delivery note actually prints one. A price entered here is treated as evidence of what the supplier charged — a figure nobody read off a document should not be recorded as one.
Item (pack)
Ordered
Received (packs)
Free (packs)
Pack size
Price / pack on the delivery note
Total to stock
Batch / expiry / size
Write what is on the box or the paper. These do not go into stock until the buyer answers; the rest of the delivery does.
What it says
Their code
Received (packs)
Free (packs)
Price / pack
You hold both the receiving and the posting permission here.
Normally one person records the delivery and a second person posts it to stock. Because you are doing both, the database requires a reason, and records it.
Please check before this goes in.
This reason came from the database — the screen sent your entries and was given the message above.
Delivery recorded.
Part-delivered and closed-short orders
Something arrived and something is still owed. Leave them if the rest is coming — or call an order closed if it is not, which needs a reason and takes the outstanding items out of stock-on-order.
Deliveries awaiting posting
Recorded by someone else and not yet posted to stock. Posting is what moves the stock.
Transfers
Request Stock
What your clinic should order
Computed from your stock on hand and your recent usage, against the ordering rule that applies to each product. Quantities are in base units, not packs — the buyer decides which pack sizes fill them. Change any quantity you disagree with and say why; leave the rest alone. Both figures are sent — what was suggested and what you asked for.
The database refused this:
The refusal happened in the database, not here.
Request sent.
Ask for something the rule did not suggest
The list above only covers products this clinic already holds or has used. Anything genuinely new to the clinic will not appear there at all, so search for it here.
Identify Supplier Lines
Unresolved supplier lines
These are lines the database could not match to a pack on its own. The app performs no checks of its own: it sends the pack you choose, and the database applies the permission, refuses a duplicate, and records you as the person who identified it. Once committed, every future line carrying the same wording from this supplier resolves to this pack.
Choose the pack this line means
Search by product name, pack size or code. Read the pack size against the price on the line — a correct product in the wrong pack size is the one error this screen cannot catch for you.
Worth a second look before you commit.
The database refused:
Recorded.
What has been identified so far
Every live alias for this supplier, and the person who decided it. This screen only shows — nothing here can be changed yet. Correcting an alias is a separate act that does not exist as a function, so a wrong one has to be undone by hand against the database.
Count Stock
Which clinic are you counting?
Nothing is started by opening this list. A clinic already counting shows how far it has got.
Start a count
Nothing was started
The refusal happened in the database, not here.
Loading today’s sheet…
Nothing to count
Where are you standing?
Pick the place you are about to count. You will work through every item on the sheet there, then come back and pick the next place.
Print the count sheet
Puts today’s list on paper, with one column for each place this clinic counts. To keep a copy on disk, choose “Save as PDF” in the print box — that is the file to send to the branch. What the system expects to find is never printed.
When you have been everywhere
Abandon this count
Wrong kind of count, or the wrong clinic? Abandoning frees this clinic to start again. Nothing is deleted — the count is kept and marked abandoned, with your reason against it, and the CEM is told.
Not abandoned
The refusal happened in the database, not here.
Counting in
—
—
—
Tap how many you counted on the keypad and press Enter to record it — Enter moves you on to the next pack size, and then to the next item.
No counting shapes are set up for this item yet.
0
recorded for this item, all areas
You have typed and not recorded it yet.
The database refused this
The refusal happened in the database, not here.
That is every item on the sheet.
Items you have not recorded anywhere
You have been to every area. These items still have no reading, so each one needs a reason before the count can be submitted. A silent line is not a zero.
Only the first of these four is a count. The other three are reasons you could not make one. There are none — I looked everywhere is a reading of zero. You went to every area and the shelf is empty. The system will write the stock off, and the item then waits its normal turn before coming round again. Not found, Could not get to it and Skipped record no reading at all. The stock figure is left exactly as it is, and the item is back on tomorrow's sheet — and every sheet after that, until somebody counts it or declares there are none. They do the same thing to the stock; the difference is the reason your reviewer reads, so pick the true one.
Review Count
Counts waiting for review
Every submitted count at a clinic where you may finalise counts. A count stays here until it is approved.
Nothing is waiting for review.
Reviewing
—
Differences that need a reason
Everything else
Finalise
Discard this count
For when the count itself is wrong — the wrong clinic, the wrong kind of count,
or readings that cannot be trusted. The clinic is freed to count again and the readings are gone.
Nothing is deleted and no stock moves: the count is kept and marked discarded with your reason on it,
and the CEM is told.
Approve Invoice Payments
Releasing money to suppliers
Nothing here is paid by the system — approving records that an amount may be paid. You may not approve an invoice you captured, nor one whose differences you ruled on.
Ready to approve
Part approved — a balance is still open
Approve more when a credit or the goods arrive, or close the balance for good.
Invoices Needing Attention
Supplier invoices needing attention
Every supplier invoice that still needs something appears below exactly once, saying what it is waiting for. Open one at a time and deal with it. Nothing here is approved or paid. An invoice you have finished stays on the list until the end of today, so anyone else working the queue can see it was dealt with.
Capture Supplier Invoice
The supplier’s document
Type in what the supplier’s invoice says
This records the document as it is written — it does not interpret it. Once it is in, the system works out which product each line is and compares it against the order and the delivery.
The supplier’s document
Attach the invoice as a PDF or a photograph. It is filed before the invoice is captured, so an invoice is never recorded with its paper missing.
No document chosen yet.
Choose a document first. Reading fills the form in for you — you still check it against the paper beside you.
The lines, as printed
Type what the invoice says. The description and the quantity are the only things required — everything else helps the system work out what the line is.
Description, as printed
What it is search our products
Their code
Qty
Free
Price each excl VAT
Line total excl VAT
Batch / expiry
The totals, as printed at the foot of the invoice
Product Master
Choose a product to see its detail, or use the filters to narrow the list.
Reports
Report extracts
Each workbook is defined in the database as a set of views. Download the data behind a
workbook — one CSV per sheet, plus the registry itself. Hand those to a chat and it
will build the workbook and the commentary.
Nothing is shown on screen here by design: the figures are formatted and interpreted once,
in the workbook, not twice.
Report month
Daily Dispensing Load
Load today’s dispensing
Upload the Healthbridge extract into the system, then run it from here. The file covers the last two weeks, so most of it will already be known — that is normal, not an error. What matters is what is new, and how far back it reaches.
The Healthbridge workbook
Pick the workbook exactly as it came out of Healthbridge. The system converts it, checks it against its own summary page, and refuses to go on if the two disagree. Nothing reaches the system until those numbers match.
Waiting to be loaded
Looking…
Clinics in this file
Every run, most recent first
Looking…
Review New Products
Products that look like the same medicine
The same medicine arrives under several national codes — each manufacturer's version is a separate code, so the system cannot tell they belong together. Grouping them means the system orders, counts usage and reports at the level of the medicine, not the code. Nothing is deleted and nothing moves: each record keeps its own history, and a grouping can be undone.
Products the system created for you
The system builds a product record whenever a clinic dispenses something it has never seen before, so the stock is recorded straight away. Nothing here can be ordered until you approve it. Every field is a proposal — correct anything that is wrong.
Read the flag before you read the numbers.
The busiest item on this list is the one most likely to be a data error, not the one most in demand. A product whose pack size is wrong reports enormous quantities. Fix the pack size first; the volume then means something.