WO2008018037A2 - Management of livestock - Google Patents

Abstract

The invention relates to a method of keeping record of livestock. The method includes recording a unique identity which has been allocated to each of a multiplicity of animals belonging to a number of different parties. Each unique identity is associated with both a unique machine readable identity and a unique human readable identity given to an animal. The method also includes receiving data about each animal, and storing the data about each animal as a separate dataset in a central database, the recorded unique identity of each animal being linked to the dataset relating to the animal. The method further includes in response to receipt of a data request from a requestor in respect of a particular animal identified in the data request, making at least some of the data in the dataset relating to said animal available. The invention extends to a system for keeping record of livestock.

Description

MANAGEMENT OF LIVESTOCK

THIS INVENTION relates to management of livestock. It more particularly relates to a method of keeping record of livestock, and to a system for keeping record of livestock.

In accordance with one aspect of the invention there is provided a method of keeping record of livestock, the method including: recording a unique identity which has been allocated to each of a multiplicity of animals belonging to a number of different parties, each unique identity being associated with a unique machine readable identity and a unique human readable identity given to an animal; receiving data about each animal in respect of which a unique identity has been recorded; storing the data about each animal as a separate dataset in a central database, and linking the recorded unique identity of each animal to the dataset relating to the animal; and in response to receipt of a data request from a requestor in respect of a particular animal identified in the data request by means of its unique identity, making at least some of the data in the dataset relating to said animal available.

The method may thus also include receiving a said data request.

The method may include generating each said unique identity.

The method may include linking the unique machine readable identity and the unique human readable identity, so that an animal can be identified by using only one of the machine readable identity and the unique human readable identity given to the animal. Thus, access can be obtained to a dataset of a particular animal by using either one of the unique machine readable identity and the unique human readable identity.

The method may include periodically receiving updated data about an animal, and updating the dataset in respect of the animal in accordance with said updated data. The method may also include receiving additional data about an animal and adding said additional data to the dataset in respect of the animal.

The data in each dataset may include data about one or more selected from the group consisting of: date of birth of the animal; gender of the animal; breed of the animal; breeding history of the animal; demographical information about to the animal; genetic information about to the animal; medical history of the animal; treatment history of the animal; information about ownership of the animal; geographical location of the animal; status of the animal, e.g. whether the animal is dead or alive; and nutritional information relating to the animal.

Each dataset when populated will thus contain data from cradle to grave of an animal. Naturally, the above list is not exhaustive.

The data about an animal may be received from a party associated with ownership of the animal. For purposes of this specification a party associated with ownership of an animal is to be understood as including the owner of the animal, an employee of such owner, an agent of such owner responsible for the animal, or any other party designated by such owner to furnish and receive data about the animal. Data about an animal that will typically be received from a party associated with ownership of the animal will include data about the ownership of the animal, the date of birth of the animal, the gender of the animal, the breed of the animal, the breeding history of the animal, the demographical information about to the animal, if available to said party, genetic information about to the animal, medical history of the animal, treatment history of the animal, the geographical location of the animal, status of the animal, and the nutritional information relating to the animal. With status of the animal is meant whether the animal is in transfer, i.e. from one location to another, whether it is still alive or dead, whether it has been reported as lost or stolen, and the like.

Instead, the data about an animal may be received from an independent party, e.g. a veterinarian or a veterinary laboratory. Typically, when the independent party is a veterinarian or a veterinary laboratory, data received from said party will be in the form of medical data, e.g. results of a blood or other test conducted on an animal. Thus, data on whether or not an animal is infected with a particular disease or suffers from a particular condition can be contained in the dataset of the animal.

The data about an animal may electronically be received from a location remote from the central database. Typically, the data will be received via a distributed network, e.g. the Internet. For example, the data will be received via an Internet portal. In one embodiment, the party from whom the data is received will log onto an Internet website and will submit the data via the website.

The abovementioned data request may be received from a party associated with ownership of an animal. Instead, the data request may be received from an independent party. For example, a data request may be received from a law enforcement authority to ascertain ownership of an animal, in case the animal appears to be lost or it is suspected that the animal has been stolen.

The data request may be received from a location remote from the central database. In one embodiment, if desired, a data request may be received telephonically, in which case the human readable identity given to the animal will be used to identify the animal. In another embodiment, the data request may electronically be received. The data request may be received via the aforementioned Internet portal. In this case, as will be appreciated either one of the machine readable and the human readable identity may be used to identify the animal. Data in the dataset may be made available to the party from whom the data request is received. For example, if data is requested by a law enforcement authority, the data can be made available to the law enforcement authority. Instead, data in the dataset may be made available to a party other than the party from whom the data request is received. For example, a party associated with ownership of an animal may request that data about the animal be made available to an independent party, e.g. a party interested in taking over ownership of the animal.

The data may be made available to a said party by electronically sending it to the party, e.g. by e-mail or short message service (sms), or the like. Instead, the data may be made available to a said party by allowing the party electronically to view the data. For example, the party may be allowed to view the data via the aforementioned

Internet portal.

When said party to whom the data is made available is a party associated with ownership of an animal, the data may be made available by causing the data automatically, in response to receipt of a data request from said party associated with ownership, electronically to be downloaded from the central database to an electronic database operated by said party associated with ownership and to overwrite existing data contained on said database operated by the party associated with ownership. For example, if blood test results in respect of an animal is received from a veterinary laboratory and said blood test results are included in the dataset of the animal, the blood test results will automatically be downloaded onto said database operated by the party associated with ownership of the animal, and overwrite previous blood test results contained on said party's database. The same applies to the results of any other tests conducted on an animal.

The method may include receiving from a party associated with ownership of an animal a transfer request to issue a transfer reference in respect of at least one animal of said party to be transferred, and in response to receipt of said transfer request, issuing to the party a unique transfer reference which can be linked to said at least one animal, and storing the transfer reference on the central database. In one embodiment, the method may include receiving from the party to whom a unique transfer reference is issued one of the unique machine readable identity and the unique human readable identity of at least one animal to be transferred, and linking the dataset of each said animal to the unique transfer reference. In another embodiment, the method may include simultaneously with receiving a transfer request, also receiving one of the unique machine readable identity and the unique human readable identity of at least one animal to be transferred, and linking the dataset of each such animal to the unique transfer reference prior to issuance of the transfer reference. Thus, by using the transfer reference, a list of the unique identity of each animal linked to the reference and, accordingly, access to the data contained in the dataset of each such animal can be obtained.

The transfer reference may electronically be issued, e.g. via e-mail or sms, or it may be made available via the aforementioned Internet portal.

The method may include receiving from a party to whom the unique transfer reference was issued a request to make the transfer reference available to a designated party and, in response to receiving said request, making the transfer reference available to the designated party. Typically such a designated party will be a party who is to receive the transferred animal(s), e.g. a party taking over ownership of the animal(s). In this case, the transfer reference may be made available to the designated party by electronically sending it to the designated party.

The method may include receiving from the designated party to whom the unique transfer reference was made available, a data request, including said transfer reference, for making available the data contained in the dataset of each animal whose dataset is linked to the transfer reference and, in response to receipt of a said data request, making data in said datasets available to the party from whom the data request was received. Thus, by making use of a said transfer reference, data about each transferred animal can electronically be made available to a said designated party, e.g. the new owner of each transferred animal. Said making available of data may be by permitting said data electronically to be downloaded from the central database to a remote electronic database operated by said party from whom the data request was received. Thus, a new owner of each transferred animal can, typically via the aforementioned website, electronically download all the data in the dataset of each transferred animal to his own electronic database. Naturally, if desired, the method may include, prior to making said data available to the designated party, updating the data in accordance with transfer particulars, e.g. if ownership passes, this may be updated as such in each dataset in question, if location of each animal changes, this may be updated accordingly, and the like.

The method may further include linking, on the central database, the datasets of all animals belonging to a particular party. The method may yet further include, upon receipt of a data request including a transfer reference, causing the link on the central database between the dataset of each animal linked to the transfer reference and the party owning said animal to be terminated, and a new link to be established between the dataset of each said animal and a party from whom the data request including the transfer request is received.

The method may also include prior to recording of the unique identity of each animal, allocating said unique identity to each animal.

The method may include simultaneously with receiving data about an animal and receiving a data request in respect of an animal also receiving one of the unique machine readable identity and the unique human readable identity of the animal, to permit identification of each animal in question. Thus, a party providing data about an animal or requesting data about an animal will have to specify each animal in question. Typically, the machine readable identity of an animal in question will electronically be read, or the human readable identity of the animal will be captured.

The method may further include verifying the identity of a party prior to receiving data about an animal from the party or prior to making data about an animal available to the party. To facilitate said verification, the method may include assigning a user identity to each party from whom data will be received or to whom data will be made available. Thus, the user identity of each party will be used to effect said verification of the identity of the party. The method may include requiring a party to register by furnishing predetermined information, prior to assigning a user identity to a party, and upon receipt of said information assigning a user identity to a party. Thus, a portfolio may be created on the central database in respect of each party owning or associated with ownership of an animal in respect of which data will be contained ion the central database. By virtue of the abovementioned link which is established between the dataset of each animal belonging to a particular party and said party, the portfolio of each party owning or associated with ownership will, in effect, also contain the datasets of each animal associated with such party. Thus, when transfer of ownership of an animal takes place, and the aforedeschbed transfer reference is used, the central database will be updated such that the dataset of each animal in respect of which ownership is being transferred will be linked to or included in the portfolio of the party taking ownership of the animal or the party associated with said ownership.

As foreshadowed above, the method may also include providing a data interface, e.g. the aforementioned Internet portal, via which the data about each animal is received, and via which data about each animal can be made available.

The unique machine readable identity given to each animal may be in the form of a two-dimensional matrix code.

Accordingly, the invention also provides an identification tag for securing to an animal, the identification tag being provided with a machine readable two- dimensional matrix code.

The identification tag may as foreshadowed above, in addition to the machine readable two-dimensional matrix code, also be provided with a human readable identification code, e.g. a numeric or alphanumeric code. Advantageously, the identification tag will be provided with both the machine readable two-dimensional matrix code and the human readable identification code.

The identification tag may further, if desired, be provided with a human readable management code, the human readable management code being in the form of a numeric or alphanumeric code.

The identification tag may include a body, the machine readable two- dimensional matrix code and the human readable identification code and, when applicable, the management code being provided on the body. The body may include a tag portion on which the machine readable two-dimensional matrix code and, when applicable, the human readable identification code and, when applicable, the management code are provided, and a securing portion fast with the tag portion and by means of which securing portion the tag is in use secured to an animal.

In some embodiments, the identification tag may also include an electronic identification device fast with the body for permitting remote identification of an animal to which the identification tag is secured in use. The electronic identification device, in one embodiment, may be in the form of an Electronic Individual Identification (EID) tag identifiable by a remote reader. In another embodiment, the electronic identification device may be in the form of a Radio Frequency Identification (RFID) tag identifiable by a remote reader.

The two-dimensional matrix code provided on the body of the identification tag may be in the form of a data matrix. If desired, the two-dimensional matrix code may, instead, be in the form of any other matrix code, e.g. an Aztec code, or a QR code.

The body of the device may be constructed from scuff- and tear resistant weatherproof material, i.e. a material that has high resistance against damage by the elements. In a particular embodiment, the body of the identification tag may be in the form of an ear tag for securing to one ear of an animal. In this case, the tag portion of the body may be of synthetic plastics construction, the securing portion, typically, being at least partially constructed of metal. Alternatively, the securing portion may be entirely of synthetic plastics construction.

The invention also provides a collection of identification tags, the collection comprising a multiplicity of identification tags as hereinbefore described, each identification tag including a machine readable two-dimensional matrix code, with the two-dimensional matrix code of each tag being unique, so that each tag has a unique identity provided by its unique matrix.

Each tag in the collection is thus, by virtue of its unique identity, distinguishable from each other tag in the collection. Accordingly, each animal to which an identification tag is secured will be distinguishable from every other animal to which an identification tag is secured. Each tag in the collection may also include the aforedeschbed human readable identification code, the human readable identification code of each tag being unique. The human readable identification code of each identification tag thus also provides the tag with a unique identity. Each animal to which an identification tag is secured can then, either by making use of the unique identity provided by the two- dimensional data matrix or by making use of the unique identity provided by the human readable identity code, be distinguished from each other animal to which such an identity tag is secured.

When each identification tag includes the aforedescribed electronic identification device, the electronic identification device of each tag will also have a unique identity code associated therewith, such that the electronic identification device also provides the identification tag with a unique identity.

In accordance with another aspect of the invention there is provided a system for keeping record of livestock, the system including: a data server for connection to a distributed network, the data server being configured to store a dataset in respect of each of a multiplicity of animals belonging to a number of different parties in respect of which record is to be kept, each dataset comprising a unique identity of the animal, which unique identity is associated with a unique machine readable identity and a unique human readable allocated to the animal, the data server further being configured when connected to a said distributed network: to receive, via the distributed network, data about animals in respect of which datasets are stored, and to include said received data in the dataset relating to the animal; and to receive a data request in respect of an animal in respect of which a dataset is stored from a location remote from the data server, in which request at least some of the data contained in the dataset relating to the animal is requested and, in response to receipt of the data request, to retrieve the requested data from the database and to make it available.

The access means may be operatively connected to the data server for accessing each dataset. The server may be configured to generate each said unique identity.

The data server may be configured to host a database containing each dataset. Thus, a database containing each dataset may be hosted on the data server.

The access means may be in the form of a network interface providing for said connection of the data server to a distributed network. The distributed network may be a virtual private network which may use one of the Internet, a wireless application protocol network, or a cellular telephone communications network. Instead, the distributed network may be a public network.

The access means may include a user interface to the data server. The user interface may be in the form of any one of an Internet portal, a wireless application protocol portal and a cellular telephone interface. In one embodiment, a website may be provided via which website data is received and made available.

The unique machine readable identity and the unique human readable identity allocated to each animal may be linked, so that an animal can be identified by using only one of the machine readable identity and the unique human readable identity given to the animal.

The data server may be configured periodically to receive updated data about an animal and to update the dataset in respect of the animal accordingly.

The data server may be configured to receive additional data about an animal and to add said additional data to the dataset in respect of the animal.

Each dataset may provide for storage of data about one or more aspects of an animal selected from the group consisting of: date of birth of the animal; gender of the animal; breed of the animal; breeding history of the animal; demographical information about to the animal; genetic information about to the animal; medical history of the animal; treatment history of the animal; information about ownership of the animal; geographical location of the animal; status of the animal; and nutritional information relating to the animal.

The above list is not exhaustive. A dataset may thus include data, from cradle to grave, of an animal.

The data server may be configured to receive data from a party associated with ownership of the animal. The data server may be configured also to receive data from an independent party, e.g. a veterinary laboratory conducting tests on animals.

The data server may be configured to receive a data request from a party associated with ownership of an animal. In addition, the data server may be configured to receive a data request from an independent party, e.g. a law enforcement authority such as the police who wish to enquire about ownership of an animal. A said data request will typically electronically be received, e.g. via the Internet portal.

The data server may be configured to make requested data available to the party from whom the data request is received. In addition, the data server may be configured to make requested data available to a party other than the party from whom the data request is received. The data server may be configured to make the requested data available to a said party by electronically sending it to the party. The data server may be configured also to make the requested data available to a said party by allowing the party via the user interface to view the data.

When said party to whom the data is made available is a party associated with ownership of an animal, the date server may be configured such that the data is made available by causing the data automatically, in response to receipt of a data request from said party associated with ownership, electronically to be downloaded via the distributed network to an electronic database operated by said party and to overwrite existing data contained on said database operated by the party associated with ownership.

The data server may be configured to receive from a party associated with ownership of an animal a transfer request to issue a transfer reference in respect of at least one animal of said party to be transferred, and in response to receipt of said transfer request, to issue to the party a unique transfer reference which can be linked to said at least one animal, and to store the transfer reference on the central database.

The data server may be configured to receive from the party to whom a unique transfer reference is issued one of the unique machine readable identity and the unique human readable identity of at least one animal to be transferred, and linking the dataset of each said animal to the unique transfer reference. In another embodiment, the data server may be configured, simultaneously with receiving a transfer request, also to receive one of the unique machine readable identity and the unique human readable identity of at least one animal to be transferred, and linking the dataset of each such animal to the unique transfer reference prior to issuance of the transfer reference.

The data server may be configured electronically to issue the transfer reference.

The data server may be configured to receive from a party to whom the unique transfer reference was issued a request to make the transfer reference available to a designated party and, in response to receiving said request, making the transfer reference available to the designated party.

The data server may be configured to make the transfer reference available to the designated party by electronically sending it to the designated party.

The data server may be configured to receive from the designated party to whom the unique transfer code was made available, a data request, including said transfer reference, for making available the data contained in the dataset of each animal whose dataset is linked to the transfer reference and, in response to receipt of a said data request, making data in said datasets available to the party from whom the data request was received.

The data server may be configured to make the data available by permitting said data electronically to be downloaded via the distributed network to a remote electronic database operated by said party from whom the data request was received.

The data server may be configured to link the datasets of all animals belonging to a particular party.

The data server may be configured, upon receipt of a data request including a transfer reference, to terminate the link between the dataset of each animal linked to the transfer reference and the party owning said animal, and to cause a new link to be established between the dataset of each said animal and a party from whom the data request including the transfer request is received.

The data server may be configured simultaneously with receiving data about an animal and receiving a data request in respect of an animal also to receive one of the unique machine readable identity and the unique human readable identity of the animal, to permit identification of each animal in question.

The data server may be configured to verify the identity of a party prior to receiving data about an animal from the party or prior to making data about an animal available to the party.

The data server may be configured to assign a user identity to each party from whom data will be received or to whom data will be made available, the user identity of each party being used to effect said verification of the identity of the party.

Thus, by means of said user identity, the dataset of each animal belonging to a particular party can, as mentioned above, be linked to the party.

The data server may be configured to require a party to register by furnishing predetermined information, prior to assigning a user identity to a party, and upon receipt of said information assigning a user identity to a party. The unique machine readable identity given to each animal may be in the form of a two-dimensional matrix code.

The invention is now described, by way of non-limiting example, with reference to the accompanying diagrammatic drawings.

In the drawings:

Figure 1 shows, schematically, a front elevation of one embodiment of an identification tag used in keeping record of livestock according to the invention; Figure 2 shows a block diagram of components forming part of a distributed network used in implementation of the invention, the distributed network including a system in accordance with the invention;

Figure 3 shows a block diagram of steps executed in forming a database used in implementation of the invention; Figure 4 shows a block diagram of steps executed in making available of data forming part of the database used in implementation of the invention; and

Figure 5 shows a block diagram of steps executed in order to update the database in accordance with transfer of ownership of livestock.

With reference to Figure 1 of the drawings, an identification tag for use in keeping record of livestock, and management of livestock, according to the invention is generally designated by reference numeral 10. The identification tag 10 is for securing to an animal of which record is to be kept. The invention is expected to be particularly advantageously applicable in the context of livestock such as cattle, goats, sheep, pigs, ostriches, and the like.

The identification tag 10, in this example, is in the form of an ear tag, which includes a body 12 which is constructed of scuff- and tear resistant synthetic plastics material. The body 12 includes a flattened tag portion 14, and a securing portion 16 (shown in concept only) secured to the tag portion 14. In use, the tag 10 is, by means of its securing portion 16, secured to an animal. In this embodiment, although not shown as such, the securing portion 16 includes a spigot-like formation which is received, in the case of cattle, goats, pigs and sheep, through a piercing in an ear of an animal, and a socket-defining retainer secured to a free end of the spigot-formation, such that, in use, the ear of an animal is held captive between the tag portion 14 and the socket-defining retainer.

The tag portion 14 is, as mentioned above, flattened, and has a major face 18 which, in use, faces generally forwardly. A machine readable two-dimensional matrix code, in the form of a data matrix 20, is provided on the major face 18 of the tag portion 14. The data matrix 20 is applied to the face 18 of the tag portion 14 by means of laser technology, so that it is wear-resistant and does not easily fade. Further, a human readable identification code 22, which in this embodiment is a numerical code, is also provided on the major face 18 of the tag portion 14. The tag portion 14, on its major face 18, is yet further provided with a numerical human readable management code 24. As will become more apparent hereunder, the identities 20, 22 and, when applicable, the identity of the device 26, are used to record and manage animals on a global scale, i.e. animals belonging to a multiplicity of parties, so that each said identity is unique. The management code 24, on the other hand, is used to manage animals on a local scale, e.g. all animals belonging to a particular owner or to a particular stud. Thus, the codes 24 of tags 10 need only be unique on a local basis. In this embodiment, an electronic identification device 26 (shown in broken lines) is embedded in the body 12. In other embodiments (not shown), the tag 10 does not include an electronic identification device 26. The electronic identification device 26, in one embodiment, is in the form of an electronic individual identification (EID) tag, and in another embodiment is in the form of a radio frequency identification (RFID) tag. The purpose of the codes 20, 22, 24, and the device 26 will be described in detail hereunder.

By virtue of the relative robustness, i.e. being readable even if damaged to a certain extent, of a data matrix, in comparison to, for example, a linear barcode, the data matrix 20 of the tag 10 is well suited for this particular application.

In use, a collection or multiplicity of tags 10 are employed, each tag 10, as hereunder described in further detail, serving to distinguish one animal to which a tag 10 is secured from every other animal to which a tag 10 is secured. To this end, the machine readable data matrix 20 of each tag 10 is unique, so that the data matrix 20 of each tag 10 differs from the data matrix 20 of every other tag 10. Thus, by machine reading the data matrix 20, an animal to which the tag 10 is secured can be distinguished from every other animal to which a tag 10 is secured. Likewise, the human readable identity code 22 of each tag 10 is unique, so that the identity code 22 of each tag 10 differs from the identity code 22 of every other tag 10. Thus, each animal wearing a tag 10 can be distinguished, by means of the code 22, form every other animal wearing a tag 10. Similarly, the electronic identification device 26 of each tag 10 is unique, thereby permitting, by means of a reader, i.e. also machine reading, identification of each tag 10 and, accordingly, an animal to which the tag 10 is secured. Machine reading of the code 20 and the identity of the electronic identification device 26 is done in conventional fashion and, accordingly, is not further described.

By virtue of the uniqueness of the data matrix 20, the identity code 22 and, when applicable, the electronic identification device 26 of each tag 10, each tag 10 has a unique identity. Thus, an animal wearing a tag 10 can be identified by using only one of the data matrix 20, the identification code 22 and, when applicable, the electronic identification device 26 of the tag 10 worn thereby.

As will be appreciated, an identification tag use in implementing the invention may take on any suitable shape and size other than that herein described and illustrated.

Figure 2 shows a block diagram representing components forming part of a distributed network used in implementation of the invention, the distributed network being generally designated by reference numeral 30.

The distributed network 30 includes a system in accordance with the invention for keeping record of livestock, the system comprising a data server 32 which, inter alia, includes an access means 34 in the form of a data interface. A central database 36 is hosted on the data server 32, the database 36 comprising, in respect of each animal of which record is to be kept, a separate dataset 38, in which dataset 38, as will be described hereunder, data about the animal form cradle to grave is contained in use. Only a limited number of datasets 38 are shown in Figure 2. Each dataset 38 is accessed via the access means 34. Functioning of the data server 32 in execution of a method in accordance with the invention is described hereunder with particular reference to Figures 3 - 5 of the drawings.

The server 32 is configured to generate the unique identity, i.e. the codes 20, 22 which is assigned or given to each tag 10, and to store said unique identity on the database 36. Naturally, the codes relating to each tag 10 are linked on the database

36. The unique identities will be recorded on the database 38 prior to manufacturing of the tags 10.

In use, as will be described in more detail hereunder, data is received and made available by the data server 32 via a user interface which, in this embodiment is an Internet portal, including an Internet website. Communications with the server 32 thus takes place via the Internet 40 in this embodiment. In other embodiments the user interface can be a wireless application protocol portal or a cellular telephone interface. In use, data is received from and made available to a multiplicity of parties associated with ownership of animals in respect of which record is to be kept, and also from and to independent parties described hereunder.

In Figure 2, a first party associated with ownership of animals in respect of which record is to be kept, and who wishes to make use of a facility provided by the invention, is notionally represented by block 42, the party 42 having a computer, notionally represented by block 44, on which suitable software for record keeping and livestock management purposes is installed. Another such party is notionally represented by block 46, the party 46 also having a computer 48 on which said software is installed. Naturally, in practice there will be a multiplicity of such parties, but for ease of reference only two, namely the parties 42, 46 are shown, and the invention will further be described with reference to these two parties 42, 46. As will become more apparent hereunder, each party 42, 46 has, in practice for record keeping and livestock management purposes, an electronic database hosted on their computer 44, 48, which database comprises data relating to animals belonging to the party 42, 46. Each said database is thus a local database which contains only data relating to or owned by a said party 42, 46. The management code 24 associated with each animal wearing a tag 10 can be used in relation to a said local database, to keep record of and to manage livestock on a local basis. Both the parties 42, 46 in use communicate with the server 32 via their computers 44, 48 and through the Internet 40. Communications with the server 32 can also take place via any other wireless communications device, e.g. a cellular telephone, a palmtop, or the like. An independent party 50, in this case a veterinary laboratory 50, also communicates with the data server 32 via the Internet 40. The laboratory 50 has a computer 52 on which suitable software to effect said communication is installed. Naturally, as notionally represented by the arrows in Figure 2, in order to permit said communication, a communications link need to be established, via the Internet 40, between the server 32 and a computer 44, 48, 52 in question. The same applies where communications with the server 32 is effected by means of any other communications device, e.g. a cellular telephone.

A further independent party, i.e. a party who is not associated with ownership of an animal in respect of which record is to be kept, is notionally represented by block

53 in Figure 2. The independent party can be any party who periodically needs to have access to, data stored on the central database 36. In this example, the party 53 is a law enforcement authority, e.g. the police.

Figure 3 of the drawings shows a block diagram representing steps taken in executing a method of keeping record of livestock in accordance with the invention, using the system in accordance with the invention. In order to execute the method in accordance with the invention, a multiplicity of identification tags 10 are manufactured and their respective machine readable identification codes 20, their human readable identification codes 22 and, when applicable, the identity of their electronic identification devices 26 are, as mentioned above, recorded and stored on the central database 36. Further, a party 42, 46 wishing to make use of the record keeping, and livestock management, facility provided by the invention, needs to register by providing certain pre-specified particulars about themselves. Once registered, said particulars of each party 42, 46 will be stored on the database 36. Typically, when registering, a user will be issued with a username and password which can be used to access the server 32. Also, said username and password can be used to ascertain and verify the identity of each party from whom data or a request (described hereunder) is received. Whenever identification tags 10 are issued to a registered party 42, 46, the identification tags 10, by means of their recorded and stored identities, are allocated on the database 38 to the party 42, 46. In order to effect said allocation of an identification tag 10 on the database 36 to a party 42, 46, the party 42, 46 needs to inform the server 32 that they are in possession and will be using the tag 10. Before said allocation takes place on the server 32, the identity of each tag 10 will be validated by the server 32, i.e. the server 32 will ascertain whether or not the machine or human readable code 20, 22 of a tag 10 received from the party 42, 46 has been allocated to before or not. If it has not yet been allocated, it will be allocated to the party 42, 46. If, however, the identity of the a tag in question had previously been allocated, the party 42, 46 trying to have the tag 10 in question validated, as well as the party in respect of which the identity of the tag in question had previously been validated, will be notified, e.g. by sms, e-mail, fax, telephone call, or the like. Validation can be effected by using only one of the codes 20, 22. If validation is done by using the code 22, and it appears that the identity in question had previously been allocated, a party trying to validate a tag can be required to furnish the code 20, i.e. to read the code 20. The system in accordance with the invention is thus configured to combat fraud.

The parties 42, 46 then secure the identification tags 10 to their animals and, by means of the software installed on their computers 44, 48, capture data relating to each animal wearing a tag 10. Typically, the data which is to be captured includes the date of birth of the animal, the gender of the animal, the weight of the animal when last weighed, the breed of the animal, the breeding history of the animal, demographical information about the animal, genetic information about the animal, the status of the animal, e.g. whether the animal is dead or alive, is lost or stolen, is in transit or not, and the like, the medical history of the animal, e.g. diseases with which the animal has been affected, the treatment history of the animal, e.g. the date of treatment, the medication, the batch number and expiry date of the medication, and the like, information about ownership of the animal, geographical location of the animal, nutritional information relating to the animal, and any other important information. Naturally, if a tag 10 is secured to a new born animal, the data about the animal will, as will become more apparent hereunder, be supplied as and when events occur in the life of the animal.

Block 58 in Figure 3 notionally represents receipt of data by the server 34, which data has been captured by the parties 42, 46. In order to capture said data, a party 42, 46 will identify each animal by means of one of the unique machine readable identity (obtained by reading the identity by means of a machine) and the unique human readable identity, and capture said data against a local record kept on the relevant computer 44, 48 in respect of the animal. The data is received by the server via the Internet 40. In one embodiment, the software installed on the computers 44, 48 accesses a website provided on the Internet 40, so that the data is received via the website. In another embodiment, the data is received from the computers 44, 48 via an Internet portal other than the website. Upon receipt of the data by the server 32, the server is configured to store the received data relating to each animal in a dataset 38 relating to the animal. Naturally, each animal in respect of which data is received will be identified in the received data. Likewise, the unique identity of each animal in respect of which a dataset 38 is contained on the database 32 is linked to the particular dataset 38. Thus, all data captured by a party 42, 46 is ultimately stored on a central database 32, from where it is, as described in further detail hereunder, accessible when required, and from where it can be made available. Further, the dataset 38 of each animal belonging to each party 42, 46 will be linked to the party on the database 36.

Once a dataset 38 in respect of an animal is contained on the database 36, the dataset 38 can be supplemented with additional or updated data, e.g. as and when events occur in the life of an animal in question. The method may thus, as notionally represented by block 62 in Figure 3, include receiving additional data from a party 42, 46, or from an independent party 50. Typically, additional information received, via the Internet 40, from the independent party 50 which, as mentioned above, in this example, is in the form of a veterinary laboratory, will include results of blood or other laboratory tests conducted on the animal. The additional data received from the party 50 can thus include the results of such a test, the date on which the test was conducted, and further details such as details about the laboratory or a veterinarian involved in the test and, in the case of a blood test, the time and/or place where blood was drawn from the animal. Upon receipt of said additional data, the data is stored, as notionally represented by block 64, in the dataset 38 relating to the animal in question.

The server 32 is further configured to receive updated data about an animal in respect of which a dataset 38 is contained on the database 36, as and when the status of an animal changes. Receipt of said updated data is notionally represented by block 66 in Figure 3, and receipt thereof takes place in exactly the same fashion as hereinbefore described. Said updated data will typically be received when the animal is moved from one geographical location to another, when the animal is treated, and the like. Upon receipt of the updated data by the server 32, the updated data is stored in the dataset 38 relating to each animal in question, said storage being notionally represented by block 68 in Figure 3.

The invention as described thus far thus provides for keeping a detailed record, i.e. from cradle to grave, of an animal on a central database. The data kept on the central database can be updated and accessed as and when required.

Referring now to Figure 4, a block diagram is shown which represents steps taken in making data contained on the central database 36 available. In order to obtain data contained in a particular dataset 38 of an animal, a party, which can be a party 42, 46 associated with ownership of an animal, or can be an independent party such as the party 53, sends an electronic data request to the server 32, requesting said data. The server 32 thus receives a said data request, said receipt being notionally represented by block 70 in Figure 4, in which data about a particular animal or animals is requested. Upon receipt of such a data request, the access means 34 accesses each relevant dataset 38, said accessing being notionally represented by block 72, and makes the requested data available to either the party from whom the data request was received or to another party designated in the received data request. Making available of the requested data is notionally represented by block 74 and can either be by allowing a party to view the requested data via the aforementioned website, or can be by electronically sending the requested data to a said party, e.g. via e-mail, short message service (sms), or the like. Allowing a party to view the requested data is notionally represented by block 76, and electronic sending of requested data to a said party is notionally represented by block 78. In one embodiment, where the party to whom the requested data is to be made available is the party associated with ownership of each animal in respect of which the data request is sent, the data may be made available to said party by allowing the data to be downloaded to the party's local database.

Where a party, for example the party 46, wishes to access data about an animal owned by a different party, for example the party 42, typically when the party 46 wishes to take ownership of a particular animal or animals from the party 42, a data request will be transmitted by the party 42, and in which data request it will be specified that data about each said animal is to be made available to the party 46. As indicated by blocks 76, 78 said data can thus either be viewed by the website by the party 46, or said data can be sent to the party 46 electronically, for example, by e-mail. Naturally, the party 42 may also print out data about each animal in question and hand or send it to the party 46.

In another embodiment, a data request can be received from the independent party 53. For example, in the case of theft of livestock, a law enforcement authority, such as the police, can, if an animal wearing a tag 10 is found, send a data request in respect of the animal to the server 32. Naturally, as is the case with a party associated with ownership of an animal, the animal in question will be identified either by means of its machine readable code 20, its human readable code 22 or, when applicable, by means of the identity of the electronic identification device 26 of the tag 10 worn by the animal. When data is made available to the law enforcement authority, they will then be able to ascertain who the lawful owner of the animal in question is and, whether or not the animal has been lost or stolen. When data is requested by a said party 53, the party 42, 46 who owns an animal in respect of which said data is requested will be notified, e.g. by e-mail, sms, or the like. In said notification to the owner, the identity of the requester of data will be included, so that the owner of the animal in question will know who is requesting data about the animal.

As is the case with the aforedescribed inclusion of test results on the database 36, a quarantine or other notice regarding the status of an animal can be included in the dataset 38 of the animal on the database 38. For example, when an animal is infected with a disease, and needs to be kept in quarantine, a veterinarian or other authority can, in similar fashion as hereinbefore described with reference to the laboratory 50, have a quarantine status in respect of the animal recorded on the central database 36. Whenever an independent party 53, e.g. the police in a road block situation, requests data about such an animal, it will thus be made available to them that the animal needs to be in quarantine rather than being transported, so that appropriate action can be taken by the police. A similar status can be recorded in a case where an animal needs to be killed due to infection, and if the animal is not duly killed and said death duly recorded on the database 36 by the owner, authorities can be notified, so that the matter can be investigated. The invention further facilitates, for record keeping and tracking purposes, transfer of ownership of animals in respect of which record is kept, said facilitation of transfer of ownership being described hereunder with reference to Figure 5 of the drawings.

When ownership of an animal or animals in respect of which datasets 38 are contained on the database 36 is to be transferred, the owner, for example the party 42, sends via the Internet 40 a transfer request to the server 32. The transfer request will, in the case where a party to whom ownership is to be transferred is registered, include details of said party to whom ownership is to be transferred. Receipt of the transfer request by the server 32 is notionally represented by block 80 in Figure 5. Upon receipt of the transfer request, the server 32 is configured to issue a transfer reference, such issuing being represented by block 82, to the party 42, i.e. the party from whom the transfer request is received. The issued transfer reference is stored on the database 36. In one embodiment, after issuance of the transfer request to the party 42, the party 42 needs to provide the identity of each of their animals in respect of which ownership is to be transferred. This is also done via the Internet 40. Thus, in this embodiment, the identity of each animal which is to be associated with the transfer reference is received by the data server 32, such receipt being represented by block 84. Upon receipt of the identity of each animal in question, the server 32 is configured to link the dataset 38 of each such animal to the issued and stored transfer reference. In another embodiment, the unique identity of each animal in respect of which ownership is to be transferred is included, by the party 42, in the transfer request, so that such identity is received simultaneously with the transfer request. In this embodiment, the aforementioned linking of the identity of each animal in question to the transfer reference is done by the server 32 prior to issuance of the transfer reference to the party 42. Irrespective of which of the aforementioned procedures is followed, the linking of the unique identity of each animal in question with the transfer reference is represented by block 86.

When each animal whose dataset 38 is linked to the transfer reference, i.e. each animal in respect of which ownership is to be transferred, is dispatched to a party to whom ownership is to be transferred, for example the party 46, the transfer reference can be made available to the party 46. Said making available of the transfer reference is represented by block 88 in Figure 5. Making available of the transfer reference to the party 46 can either be via the server 32, or can be effected directly between two involved parties, i.e. the parties 42, 46. A transfer reference is, in the case where it is made available via the server 32, made available electronically to the party 46 to whom ownership of each animal in question is to be transferred, for example by sms, by e- mail, or by facsimile, or by a combination of tow or more of said means.

Upon receipt of the transfer reference by the party 46 to whom ownership of each animal in question is to be transferred, the party 46 sends, via the Internet 40, a data request to the server 32. If ownership is to be transferred to a party who is not registered, the party may, by using the transfer reference access the data in the datasets 38 of the animals in question via the website. Receipt of the data request by the server 32 is notionally represented by block 90. Upon receipt of the data request 90, which data request includes the transfer reference, the server identifies the party 46 and causes the data contained in the dataset 38 of each animal in question to be made available to the party 46. Making available of said data is twofold in that the data can be viewed by the party 46 via the aforedescribed Internet website and in that the server 32 causes the data contained in the dataset 38 in question, automatically upon establishment of a communications link between the computer 48 and the server 32 to be downloaded onto the database of the party 46 contained on the computer 48. Further, upon receipt of said data request represented by block 90 by the server 32, the link, described above, which was established between the party 42 and the dataset 38 of each animal belonging to the party 42 is terminated and a new link is established between the party 46 and the each dataset 38 in respect of each animal transferred to the owner 46.

Further, if a dataset 38 in respect of an animal of a particular party associated with ownership has been updated, typically by an independent party 50, the server 32 is configured automatically upon establishment of a communications link between a computer associated with said party and the server 32 to download all updated data contained in the dataset of the animal in question to the database contained on the computer of said party, and to overwrite existing data contained on the database hosted on the computer of such party. Thus, if a dataset 38 in respect of an animal has been altered or the status of the animal has been changed on the database 36 by a party other than the party 42, 46 associated with ownership of the animal in question, all alterations or changes in status will automatically be reflected on the local database of the party 42, 46 every time the party establishes a communications link with the server 32.

The invention as described and illustrated thus provides for keeping of a central database containing information, from cradle to grave, of a multiplicity of animals. In particular, by providing for inclusion of the medical history, in particular blood or other test results, in said database by an independent laboratory or authority, an interested party can immediately, when provided with access to data contained on the database in respect of a particular animal, ascertain whether or not the animal is or was infected with a disease. The invention thus resists spreading of animal diseases by allowing a prospective owner of animal or any other interested party, in real time, to access data about the animal. Furthermore, as will be appreciated, the invention as described and illustrated provides for tracking or tracing of the whereabouts and ownership of animals, and provides a way of facilitating changes in ownership or whereabouts of animals. Further, the invention, by virtue of data about animals being kept on a centralized database, provides for easy generation of statistical data about said animals.

Claims

CLAIMS:

1. A method of keeping record of livestock, the method including: recording a unique identity which has been allocated to each of a multiplicity of animals belonging to a number of different parties, each unique identity being associated with a unique machine readable identity and a unique human readable identity given to an animal; receiving data about each animal in respect of which a unique identity has been recorded; storing the data about each animal as a separate dataset in a central database, and linking the recorded unique identity of each animal to the dataset relating to the animal; and in response to receipt of a data request from a requestor in respect of a particular animal identified in the data request by means of its unique identity, making at least some of the data in the dataset relating to said animal available.

2. A method as claimed in Claim 1 , which includes linking the unique machine readable identity and the unique human readable identity, so that an animal can be identified by using only one of the machine readable identity and the unique human readable identity given to the animal.

3. A method as claimed in Claim 1 or Claim 2, which includes periodically receiving updated data about an animal, and updating the dataset in respect of the animal in accordance with said updated data.

4. A method as claimed in any one of the preceding claims, which includes receiving additional data about an animal and adding said additional data to the dataset in respect of the animal.

5. A method as claimed in any one of the preceding claims, in which the data in each dataset includes data about one or more selected from the group consisting of: date of birth of the animal; gender of the animal; breed of the animal; breeding history of the animal; demographical information about to the animal; genetic information about to the animal; medical history of the animal; treatment history of the animal; information about ownership of the animal; geographical location of the animal; status of the animal; and nutritional information relating to the animal.

6. A method as claimed in Claim 5, in which the data about an animal is received from a party associated with ownership of the animal.

7. A method as claimed in Claim 5, in which the data about an animal is received from an independent party.

8. A method as claimed in Claim 6 or Claim 7, in which the data about an animal is electronically received from a location remote from the central database.

9. A method as claimed in any one of Claims 6 - 8 inclusive, in which the data request is received from a party associated with ownership of an animal.

10. A method as claimed in any one of Claims 6 - 8 inclusive, in which the data request is received from an independent party.

11. A method as claimed in Claim in Claim 9 or Claim 10, in which the data request is received from a location remote from the central database.

12. A method as claimed in Claim 11 , in which the data request is electronically received.

13. A method as claimed in any one of Claims 9 - 12 inclusive, in which data in the dataset is made available to the party from whom the data request is received.

14. A method as claimed in any one Claims 9 - 12 inclusive, in which data in the dataset is made available to a party other than the party from whom the data request is received.

15. A method as claimed in Claim 13 or Claim 14, in which the data is made available to a said party by electronically sending it to the party.

16. A method as claimed in Claim 13 or Claim 14, in which the data is made available to a said party by allowing the party electronically to view the data.

17. A method as claimed in Claim 15, in which, when said party is a party associated with ownership of an animal, the data is made available by causing the data automatically, in response to receipt of a data request from said party associated with ownership, electronically to be downloaded from the central database to an electronic database operated by said party associated with ownership and to overwrite existing data contained on said database operated by the party associated with ownership.

18. A method as claimed in any one of Claims 5 - 17 inclusive, which includes receiving from a party associated with ownership of an animal a transfer request to issue a transfer reference in respect of at least one animal of said party to be transferred, and in response to receipt of said transfer request, issuing to the party a unique transfer reference which can be linked to said at least one animal, and storing the transfer reference on the central database.

19. A method as claimed in Claim 18, which includes receiving from the party to whom a unique transfer reference is issued one of the unique machine readable identity and the unique human readable identity of at least one animal to be transferred, and linking the dataset of each said animal to the unique transfer reference.

20. A method as claimed in Claim 18, which includes simultaneously with receiving a transfer request, also receiving one of the unique machine readable identity and the unique human readable identity of at least one animal to be transferred, and linking the dataset of each such animal to the unique transfer reference prior to issuance of the transfer reference.

21. A method as claimed in any one of Claims 19 - 20 inclusive, in which the transfer reference is electronically issued.

22. A method as claimed in any one of Claims 19 - 21 inclusive, which includes receiving from a party to whom the unique transfer reference was issued a request to make the transfer reference available to a designated party and, in response to receiving said request, making the transfer reference available to the designated party.

23. A method as claimed in Claim 22, in which the transfer reference is made available to the designated party by electronically sending it to the designated party.

24. A method as claimed in Claim 22 or Claim 23, which includes receiving from the designated party to whom the unique transfer code was made available, a data request, including said transfer reference, for making available the data contained in the dataset of each animal whose dataset is linked to the transfer reference and, in response to receipt of a said data request, making data in said datasets available to the party from whom the data request was received.

25. A method as claimed in Claim 24, in which said making available of data is by permitting said data electronically to be downloaded from the central database to a remote electronic database operated by said party from whom the data request was received.

26. A method as claimed in Claim 24 or Claim 25, which includes linking, on the central database, the datasets of all animals belonging to a particular party.

27. A method as claimed in Claim 26, which includes, upon receipt of a data request including a transfer reference, causing the link on the central database between the dataset of each animal linked to the transfer reference and the party owning said animal to be terminated, and a new link to be established between the dataset of each said animal and a party from whom the data request including the transfer request is received.

28. A method as claimed in any one of the preceding claims, which includes prior to recording of the unique identity of each animal, allocating said unique identity to each animal.

29. A method as claimed in any one of the preceding claims, which includes simultaneously with receiving data about an animal and receiving a data request in respect of an animal also receiving one of the unique machine readable identity and the unique human readable identity of the animal, to permit identification of each animal in question.

30. A method as claimed in any one of the preceding claims, which includes verifying the identity of a party prior to receiving data about an animal from the party or prior to making data about an animal available to the party.

31. A method as claimed in Claim 30, in which includes assigning a user identity to each party from whom data will be received or to whom data will be made available, the user identity of each party being used to effect said verification of the identity of the party.

32. A method as claimed in Claim 31 , which includes requiring a party to register by furnishing predetermined information, prior to assigning a user identity to a party, and upon receipt of said information assigning a user identity to a party.

33. A method as claimed in any one of the preceding claims, which includes providing a data interface via which the data about each animal is received, and via which data about each animal can be made available.

34. A method as claimed in any one of the preceding claims, in which the unique machine readable identity given to each animal is in the form of a two-dimensional matrix code.

35. A system for keeping record of livestock, the system including: a data server for connection to a distributed network, the data server being configured to store a dataset in respect of each of a multiplicity of animals belonging to a number of different parties in respect of which record is to be kept, each dataset comprising a unique identity of the animal, which unique identity is associated with a unique machine readable identity and a unique human readable allocated to the animal, the data server further being configured when connected to a said distributed network: to receive, via the distributed network, data about animals in respect of which datasets are stored, and to include said received data in the dataset relating to the animal; and to receive a data request in respect of an animal in respect of which a dataset is stored from a location remote from the data server, in which request at least some of the data contained in the dataset relating to the animal is requested and, in response to receipt of the data request, to retrieve the requested data from the database and to make it available.

36. A system as claimed in Claim 35 which includes access means operatively connected to the data server for accessing each dataset.

37. A system as claimed in Claim 36, in which the data server is configured to host a database containing each dataset.

38. A system as claimed in Claim 37, in which the access means is in the form of a network interface providing for said connection of the data server to a distributed network.

39. A system as claimed in Claim 38, in which the access means includes a user interface to the data server.

40. A system as claimed in Claim 39, in which the user interface is in the form of any one of an Internet portal, a wireless application protocol portal and a cellular telephone interface.

41. A system as claimed in any one of Claims 35 - 40 inclusive, in which the unique machine readable identity and the unique human readable identity allocated to each animal are linked, so that an animal can be identified by using only one of the machine readable identity and the unique human readable identity given to the animal.

42. A system as claimed in Claim 41 , in which the data server is configured periodically to receive updated data about an animal and to update the dataset in respect of the animal accordingly.

43. A system as claimed in Claim 41 or Claim 42, in which the data server is configured to receive additional data about an animal and to add said additional data to the dataset in respect of the animal.

44. A system as claimed in Claim 43, in which each dataset provides for storage of data about one or more aspects of an animal selected from the group consisting of: date of birth of the animal; gender of the animal; breed of the animal; breeding history of the animal; demographical information about to the animal; genetic information about to the animal; medical history of the animal; treatment history of the animal; information about ownership of the animal; geographical location of the animal; status of the animal; and nutritional information relating to the animal.

45. A system as claimed in Claim 44, in which the data server is configured to receive data from a party associated with ownership of the animal.

46. A system as claimed in Claim 44 or Claim 45, in which the data server is configured to receive data from an independent party.

47. A system as claimed in Claim 46, in which the data server is configured to receive a data request from a party associated with ownership of an animal.

48. A system as claimed in Claim 46 or Claim 47, in which the data server is configured to receive a data request from an independent party.

49. A system as claimed in Claim 48, in which the data server is configured to make requested data available to the party from whom the data request is received.

50. A system as claimed Claim 48 or Claim 49, in which the data server is configured to make requested data available to a party other than the party from whom the data request is received.

51. A system as claimed in Claim 50, in which the data server is configured to make the requested data available to a said party by electronically sending it to the party.

52. A system as claimed in Claim 50, in which the data server is configured to make the requested data available to a said party by allowing the party via the user interface to view the data.

53. A system as claimed in Claim 51 , in which, when said party to whom the data is made available is a party associated with ownership of an animal, the date server is configured such that the data is made available by causing the data automatically, in response to receipt of a data request from said party associated with ownership, electronically to be downloaded via the distributed network to an electronic database operated by said party and to overwrite existing data contained on said database operated by the party associated with ownership.

54. A system as claimed in any one of Claims 44 - 53 inclusive, in which the data server is configured to receive from a party associated with ownership of an animal a transfer request to issue a transfer reference in respect of at least one animal of said party to be transferred, and in response to receipt of said transfer request, to issue to the party a unique transfer reference which can be linked to said at least one animal, and to store the transfer reference on the central database.

55. A system as claimed in Claim 54, in which the data server is configured to receive from the party to whom a unique transfer reference is issued one of the unique machine readable identity and the unique human readable identity of at least one animal to be transferred, and linking the dataset of each said animal to the unique transfer reference.

56. A system as claimed in Claim 54, which is configured, simultaneously with receiving a transfer request, also to receive one of the unique machine readable identity and the unique human readable identity of at least one animal to be transferred, and linking the dataset of each such animal to the unique transfer reference prior to issuance of the transfer reference.

57. A system as claimed in any one of Claim 54 - 56 inclusive, in which the data server is configured electronically to issue the transfer reference.

58. A system as claimed in any one of Claims 54 - 57 inclusive, in which the data server is configured to receive from a party to whom the unique transfer reference was issued a request to make the transfer reference available to a designated party and, in response to receiving said request, making the transfer reference available to the designated party.

59. A system as claimed in Claim 58, in which the data server is configured to make the transfer reference available to the designated party by electronically sending it to the designated party.

60. A system as claimed in Claim 58 or Claim 59, in which the data server is configured to receive from the designated party to whom the unique transfer code was made available, a data request, including said transfer reference, for making available the data contained in the dataset of each animal whose dataset is linked to the transfer reference and, in response to receipt of a said data request, making data in said datasets available to the party from whom the data request was received.

61. A system as claimed in Claim 60, in which the data server is configured to make the data available by permitting said data electronically to be downloaded via the distributed network to a remote electronic database operated by said party from whom the data request was received.

62. A system as claimed in Claim 60 or Claim 61 , in which the data server is configured to link the datasets of all animals belonging to a particular party.

63. A system as claimed in Claim 62, in which the data server is configured, upon receipt of a data request including a transfer reference, to terminate the link between the dataset of each animal linked to the transfer reference and the party owning said animal, and to cause a new link to be established between the dataset of each said animal and a party from whom the data request including the transfer request is received.

64. A system as claimed in any one of Claims 35 - 63 inclusive, in which the data server is configured simultaneously with receiving data about an animal and receiving a data request in respect of an animal also to receive one of the unique machine readable identity and the unique human readable identity of the animal, to permit identification of each animal in question.

65. A system as claimed in any one Claim 35 - 64 inclusive, in which the data server is configured to verify the identity of a party prior to receiving data about an animal from the party or prior to making data about an animal available to the party.

66. A system as claimed in Claim 65, in which the data server is configured to assign a user identity to each party from whom data will be received or to whom data will be made available, the user identity of each party being used to effect said verification of the identity of the party.

67. A system as claimed in Claim 66, in which the data server is configured to require a party to register by furnishing predetermined information, prior to assigning a user identity to a party, and upon receipt of said information assigning a user identity to a party.

68. A system as claimed in any one of Claims 35 - 67 inclusive, in which the unique machine readable identity given to each animal is in the form of a two- dimensional matrix code.