EC 12 - ABORT Event
The ABORT event declares that an animal's pregnancy has aborted. The app expects you to add pregnant females to this event, so it will not allow you to add an animal that is not in the PREGPregnant reproduction status.
See the topics below for help with this event:
- Define Details for this Event
- What Happens When I Process Changes for this Event?
- Need Help Adding Animals to this Event?
The details listed below are typical for an Abort event; however, be aware that the details you see in the mobile app may vary based on the DairyComp command that created the event. If any fields other than the animal IDAnimal identifier are required to process an animal, they will be marked with the * (asterisk) symbol in the app.
The ID of the animal whose pregnancy has aborted. This field is automatically populated with the animal ID when you add it to the list. You can tap the animal's ID number to view its CowCard.
When entering an Abort event for an animal, she will no longer remain in PREG status. Tap this field to select her new reproduction code:
- If the animal’s DDATDry date=0, select one of the following reproduction codes: No Bred, Fresh, Open/OK, or Bred.
- If the animal’s DDAT>0, select one of the following reproduction codes: No Bred, Fresh, Open/OK, Bred, or Dry.
Use the LACTLactation number CYCLE field to define whether this animal will start a new lactation cycle or begin a new one. If the animal's DCCDays carrying calf/pregnant is greater than 152 days, a new lactation should be started. If her DCC is less than 152, she should remain in her current lactation.
The technician who added the animal to this event. Tap this field to select from a list of available technicians.
The names and numbers in the TechnicianTech is short for Technician. list come from the Technician Table in DairyComp. This table is optional in DairyComp, so if you do not see any names here in the mobile app, you need to make sure that a DairyComp admin has created this table so that it can synchronize to the Platform. Once it has been created, a code number and name can be assigned to each technician, and members with DairyComp admin permissions can add and remove technician names as necessary. The mobile app requires an active data or WiFi connection to synchronize updates.
The Remark field allows you to type any notes that you would like to include about this animal when adding it to the event. The remark you enter here will be included as additional information in the animal's record.
Note that you will only see this option in the mobile event when REMRemark or comment is included as a condition in the DairyComp command that the Platform uses to create the event.
When DairyComp receives the updates from the Platform, it processes the following changes for each animal in the event:
- Records an Abort event and sets the EDAYEvent day to the date the event was completed in the mobile app.
- Changes the breeding result of the last BRED event to A (Abort) and sets the CDAT and SIRCSire of conception to 0 (zero).
- Updates the RPROReproductive code code to the one selected in the mobile app.
- Leaves the lactation cycle unchanged OR starts a new lactation cycle, depending on which option was selected in the mobile app.
- Sets the ABDAT and the ADDATAbortion Determination Date.
While the ABDAT (Abortion Date) is usually set to a time in the past, the ADDAT (Abortion Determination Date) records when the ABORT event was executed. For example, if today is 11/19/2019 and you run a VETLIST to check a cow for DRY confirmation, but you see that she aborted some time in the past and is now OPEN, you might estimate that the ABORT event occurred 90 days ago. In this case, the ABDAT (Abort Date) is the ADDAT (11/19/2019) – 90.
See Processing Your Changes for more information on how the mobile app, the Platform, and DairyComp work together to process your changes.
See the following topics:
- Create a New Event or Edit an Existing One
- Save Time when Adding Animals in Bulk
- Details Required to Process Animals in an Event
- Remove an Animal from an Event
Last Built: December 04, 2019