What ICAR/ADE is
The International Committee for Animal Recording (ICAR) publishes the Animal Data Exchange (ADE) standard — an open, vendor-neutral JSON format for exchanging animal, movement, and health-event records between recordkeeping systems, breed societies, and regulators internationally. Agribantu builds its export directly against the published ICAR ADE JSON Standard v1.5.
How Agribantu exports it
Export is authority-governed: it runs through the same jurisdiction-scoped access every other authority-facing read in Agribantu uses, so an export can only ever cover the holdings and organisations a given authority officer actually has standing to see. There's no open, self- serve export endpoint — it's a controlled action inside the Authority Command Centre, with every export or validation run written to the audit log.
Agribantu's export follows ICAR's Generic Data Exchange API pattern rather than its location-based pattern — the right fit for an authority user pulling data across many holdings and organisations within a jurisdiction, rather than a single farm exposing one fixed endpoint.
Validate before you export
Before any file is generated, Agribantu produces an export-readiness report: export-ready counts against not-ready counts, missing GLNs, and every species, gender, status, product-family or dose-unit value that can't be confidently mapped to the ICAR vocabulary — shown as a gap to fix, not hidden behind a success message.
A validate-only mode lets an authority officer check readiness without generating or downloading anything, and every run — validate-only or a real export — is kept as a permanent, auditable record: filters used, record counts, the validation summary, and a content hash, so a past export can always be verified against what was actually sent.
What's covered
| ICAR resource | What it covers |
|---|---|
| Animal core | Individual animal identity and core attributes. |
| Movement departure / arrival | Individual movement events, split into departure and arrival records. |
| Treatment events | Treatment, vaccination and FMD vaccination records, combined under ICAR's single treatment-event resource — ADE 1.5 has no separate vaccination resource of its own. |
Export is deliberately scoped to what capture quality currently supports well. Birth and death events, and diagnosis/course-bundle records, are not yet exported — not because they're low priority, but because publishing them today would make the integration look broader than the underlying data actually justifies. They'll be added once the capture-side data quality is there to back them.
Current status
| Capability | Status |
|---|---|
| ADE 1.5 JSON export — animals, movements, treatment/vaccination | Live |
| Export-readiness validation report | Live |
| Validate-only mode | Live |
| Export-run history & audit evidence | Live |
| Live push submission to an external ADE receiver | Not yet built |
| Birth/death & diagnosis-bundle export | Not yet built |
Today, Agribantu produces a downloadable, standards-compliant ADE export an authority can hand to or submit through whatever receiving system is appropriate. Direct, live submission to a specific external ADE-compliant receiver needs a confirmed receiver contract — endpoint, credentials, error handling, retry rules — to build against; that's the next layer once a concrete receiving integration exists, not a gap in the export itself.
The ICAR ADE JSON Standard is published by ICAR under an Apache 2.0 licence. Agribantu's mapping treats it as a domain reference, not a schema to copy internal data models from — Agribantu's own records stay independent of the export format, so a future standard revision never forces a rewrite of how data is actually stored.