Keep each animal’s identity, treatments and withdrawal restrictions together. Check the recorded blockers before a sale or movement, and retain who recorded a treatment or released a restriction, with the reason.
Keep the treatment and responsible practitioner with the animal.
Show the reason and end date of active withdrawal restrictions.
Retain referenced registry reconciliation events and release decisions.
A herd-level note is not enough when someone asks about one animal.
A buyer or veterinary reviewer cannot follow the animal’s history.
Link the treatment to the animal and responsible user or external practitioner.
Recorded treatments and the dates they restrict are checked separately.
Treatment dates and entered withdrawal-day counts create meat or milk restrictions with end dates.
One herd entry cannot explain what was recorded for a particular animal.
A herd-care batch creates separate treatment records for its eligible animal profiles.
A reference is copied over and the earlier reconciliation decision disappears.
Record the registry reference, outcome and actor as a new event, preserving earlier entries.
See how a recorded treatment carries through to the next decision in Imara Nexus.
The treatment date and withdrawal-day counts create meat or milk restrictions with end dates. Before a sale, slaughter or movement, the eligibility view shows which actions are blocked, the restriction behind each, and when it ends.
Explore it in your workspaceRecorded in Imara Nexus with a sample animal, an illustrative treatment and illustrative dates. The screens are read only: nothing is recorded, changed or released.
The person reviewing the next action can see the treatment behind the restriction.
Register animal profiles and their tags, herd and site.
An authorised practitioner records individual care or a herd-care batch with the withdrawal-day counts.
Applicable meat and milk restrictions are generated with their end dates.
Review eligibility and blockers. Supported sale, slaughter and movement changes check active restrictions.
Restriction releases retain the actor and reason. Registry reconciliation keeps the returned reference and history.
No. The responsible practitioner supplies treatment details and withdrawal-day counts. The software calculates dates from those records.
No. Milk-collection eligibility is shown for review; there is no milk-collection transaction in the application.
No. An authorised person records explicit, referenced reconciliation events.
Yes. Pumps and tractors use the shared asset and maintenance workflows. This page focuses on livestock records, rather than breeding, feed or farm accounting.
Describe how treatments and registry references are recorded today. Discuss the individual history and restriction checks your team needs.
Prefer to explore first? Start a core-platform trial. Specialist workflows are enabled and configured separately.