One animal record that follows the animal between institutions, for life.
One animal record — studbook lineage, veterinary history, diet — that follows the animal between institutions, for life. A breeding-loan transfer moves a permission, not a fragmented export, so the receiving facility gains access and the animal's history stays continuous. It is zoo and aquarium operations built around the animal, not the building.
What's included
Canonical animal record — studbook lineage, vet history, diet plans live on the animal and follow it on every transfer (held ≠ owned for breeding loans)
Inter-institution transfers move a permission, never a copy — the receiving zoo gains access, the history stays continuous
Husbandry: daily keeper rounds, behavioral observations, enrichment schedule — phone-first keeper board at /keeper
Veterinary records: exams, treatments, quarantine, prescriptions, necropsy
Collection / studbook with taxonomy, identifiers (microchip/transponder/band), parentage, ZIMS Global Accession #
ZIMS-companion posture: Species360 stays the studbook of record; Turtini owns visitor ops, husbandry, diet, staff — or flip isSystemOfRecord for unaccredited facilities
Cross-context: the institution runs at /zoo; a keeper carries their professional record at /me/keeper
About this module
Zoos & Aquariums lives at /zoo and applies the same idea to living collections: the animal owns its record. Studbook lineage, veterinary history, and diet plans live on the animal and follow it on every transfer — because in accredited breeding programs an animal is held, not owned, and its record has to stay whole as it moves between institutions. Transfer an animal on a breeding loan and the receiving zoo gains a permission to the continuous record, never a copy that immediately starts drifting from the original.
The daily work of keeping animals runs from where the keepers actually are. Husbandry — keeper rounds, behavioral observations, enrichment schedules — lives on a phone-first keeper board at /keeper, alongside veterinary records (exams, treatments, quarantine, prescriptions, necropsy) and the studbook itself (taxonomy, microchip / transponder / band identifiers, parentage, ZIMS Global Accession #).
It sits beside the system you already trust. Species360's ZIMS can remain your studbook of record while Turtini owns visitor operations, husbandry, diet, and staff — or, for an unaccredited facility, flip it to system-of-record and run everything here. And like Sports and Museums, it is cross-context: the institution runs at /zoo while a keeper carries their own professional record at /me/keeper, so an animal-care career follows the person across every facility they work at.
What you can do with it
Keep one animal record — studbook lineage, vet history, diet — that follows the animal on every transfer
Move a breeding-loan animal as a permission grant, with its history staying continuous
Run keeper rounds, behavioral observations, and enrichment from a phone-first keeper board
Track veterinary care — exams, treatments, quarantine, prescriptions, necropsy — on the animal
Complement Species360 ZIMS, or become system-of-record for an unaccredited facility
Get this module
Free for all Turtini organizations.
Who it's for
- Zoos, aquariums, safari parks, aviaries, and wildlife sanctuaries in accredited programs
- Animal rescues and private collections that need a continuous, portable animal record
- Keepers and vets who want their professional record to follow them between institutions
Details
- Category
- Operations
- Pricing
- Free
- Built by
- Badge
- New