Aquaculture health and treatment records
AquaOS holds aquaculture health and treatment records against the batches they were applied to, and enforces what those records imply. A withdrawal period is not a note someone has to remember; it blocks the sale until it clears.
- Withdrawal blocks every exit to food
- Inherited through splits
- Quarantine has no override
What the health record covers
Treatments against the fish that got them
A treatment records its substance and the units it was applied to, and stamps the batches standing in those units at the time.
The record follows the fish, so it is still answerable after the batch has been split, moved or graded.
Withdrawal periods that are enforced, not noted
A treatment sets a clearance date, and until it passes the platform refuses every exit to food: harvest to an order, sale, transfer, and hand-off.
The refusal happens at the operation, not in a report someone reads afterwards.
Inherited when the fish move
Split a treated batch and the open withdrawal copies onto every child.
This is the case a paper log loses, because the treated cohort stops existing under the name it was treated under and the obligation quietly disappears with it.
An override that leaves a mark
Where a withdrawal is overridden, the override is stamped on the operation itself.
The question of who released fish before clearance has an answer in the record rather than depending on what anyone remembers of the day.
Quarantine with no way around it
A quarantined batch cannot be moved out at all: no transfer, no split, no grading, no hand-off, no harvest to an order.
There is deliberately no override. Mortality, counts, samplings and treatments stay allowed, because a sick cohort still dies, still gets counted and still gets medicated. Releasing it is a logged act of its own.
Vaccinations, diagnoses and mortality by cause
Vaccinations and diagnoses are recorded against batches on the same footing as treatments.
Mortality carries a reason, and the mortality report groups by cause, unit or batch against the stock that was standing when the period opened, so a rate is read against its base rather than as a bare count.
See the reportsWhat changes when the record enforces itself
The worst mistake becomes hard to make
Selling fish inside a withdrawal period is a serious event for a buyer and for a certification. Making it a refused operation rather than a remembered rule is the difference between a control and a hope.
An audit has somewhere to look
What was applied, to which fish, when it cleared, and what happened to those fish afterwards are all in one record, linked by the batch rather than by a date someone has to match up by hand.
Health stops being a separate book
The treatment log, the mortality log and the production record are the same system, so a spike in losses can be read against what was done in the same units in the days before it.
Related capabilities
Harvest and dispatch
Harvest by destination, with the withdrawal and quarantine gates applied per destination.
Production tracking
Batches, placements, splits, transfers, co-mingling and lineage.
Reporting and traceability
Per-pond reports, mortality by cause, movements, farm trend, audit log, exports.
Frequently asked questions
Does AquaOS enforce withdrawal periods or only record them?
It enforces them. While a withdrawal is open, the platform refuses every exit to food for that batch: harvest to an order, sale, transfer and hand-off. Movements that are not a sale, such as an internal move or a cull, remain possible. Any override is stamped on the operation that used it.
What happens to a withdrawal period when a treated batch is split?
Every child batch inherits the open withdrawal from its parents, marked as inherited. This is the case that paper and spreadsheet logs typically lose, because the treated cohort no longer exists under the identity it was treated under.
Can a quarantine be overridden for an urgent sale?
No. Quarantine deliberately has no override path, because the entire point of the state is that nobody moves the fish until someone with write permission on the unit releases them, and that release is itself a logged action. Recording mortality, counts, samplings and treatments stays allowed throughout.
Are vaccinations recorded separately from treatments?
They are recorded as health events, alongside diagnoses, and bound to batches the same way treatments are. They sit in the same history as the production record rather than in a separate health file.
Can mortality be analysed by cause?
Yes. Mortality carries a reason, and the report groups by cause, unit or batch over any period, expressed against the stock standing at the start of that period so the figure is a rate rather than a bare count.
See AquaOS on your operation
Bring a real production scenario. AquaOS is walked through on your operation, not a canned dataset.