The Event Definitions form is where the event structure is determined for the production system. The event structure can be manipulated to suit the management system used in the monitored herd(s). The contents of the form are as follows:
- The user is
offered the choice of printing the currently displayed event only, or the entire
event structure.
-
Self-explanatory buttons to edit or delete the currently displayed event, or to
add a new event
- the code
(maximum 5 characters) used throughout the program to refer to the event, and
the full text description.
- Every event is
given a class (selected from the options in the drop-down box) which is used by
the program to determine how to respond to an instance of the event. In this way
the program can maintain checks that all female animals have a scheduled
fertility or oestrus event. It also enables running totals of lameness and
mastitis events.
- If the event
can be scheduled to occur in the future (anticipated return to heat date,
pregnancy diagnosis due date etc) then this determines if that event should
appear on action lists printed for the owner/herdsman
and/or the veterinarian. A scheduled HEAT event, for
example, is of interest to the owner, but not to the veterinarian while a
scheduled PD (pregnancy diagnosis) is relevant to both.
- Events of
certain classes (including oestrus and observation/treatment) can be defined as
transient. These will appear as scheduled events but then be removed once
confirmed to reduce the events stored in the animal record. A farmer check
following treatment of an animal would be a good example of a transient event.
The check event is scheduled so appears in the action lists at the appropriate
time. The event is confirmed and will be removed from the animal record when it
is saved. If the animal required further treatment then that would be entered as
a new event.
- In seasonal
breeding herds the scheduling of some events, such as a service, can be delayed
until the start of the breeding season as defined in Herd
Records...Options.
- Many events can
have results or outcomes. A pregnancy diagnosis, for example, can result in
positive, negative, unsure etc. The result will determine what happens next to
the animal. For example, if the animal is pregnant then, at least, a calving
event will be scheduled. If negative, another PD or fertility treatment may be
scheduled. Note that results should be mutually exclusive. The possible results,
their associated follow-up events and any standard supplies (drugs etc) are
entered in the results grid:
-
No.: The sequence in which the event results should be offered in the Event
pad or Parity data and events screen
Result name: The name of the possible results (Positive, Negative -
retry, Negative - cull)
Default supplies: Any supplies (see Supplies)
that are routinely administered in association with the result
Follow-up events: The event or events that should be scheduled in an
animal's record as a consequence of the associated result. Hence a positive PD
may schedule a calving event.
- Ay number of
categories may be defined for an event. They are not mutually exclusive so more
than one category may apply. For example a lameness event may have Front left,
Front right, Back left, Back right defined as categories to indicate the
foot/feet affected. Further categories, such as sole ulcer, laminitis etc may
also be included.
- For scheduled
vet events, it is useful to know about associated events that have already
occurred to the animal. Entering event codes in the grid will ensure that actual
events of that type are included for reference in the short version of the vet
list. For example, when a PD is scheduled it is important to know about any
earlier services, fertility or PD events that may have a bearing on the
scheduled event.
Note: |
|