Farms Health Status (v7.26)

Farm Health Status transactions are recorded and are used to update details related to the farm. Farms will display the  test results for the lab test codes. Posting Farm Health Status transactions will override health status transactions posted for entities. The variables of the health status are user defined in Lab Test Codes.

Health Status is used to control the following transactions:

1. Placements - if the registry switch for Poultry>Validate Placement Health Status is selected, the following validation occurs:

   1. Placement Control Status>Tracked - user will be warned if the days out defined on the lab test code has not met the required number of days. Placement can still be posted as it is only a warning message. BRPA placements will be projected based on the health status of the farm.

2. Transfers - if the registry switch for Poultry>Validate Transfer Health Status is selected, validation will be added to transfers based on the following options defined on the Lab Test Code. The most critical status will override others. If the farm has a 'No Transfer' status for one lab test code, then that entity cannot be transferred.

   1. Not Tracked - lab test code has no effect on the health status tracking process

   2. Tracked - lab test code is tracked on the farm or entity, however there is no further logic related to health status. It is used for reporting purposes only.

   3. Transfer to the Same Status - entities can only be transferred to entities that have the same health status.

   4. No Transfer - entities cannot be transferred. The transfer transaction can be created, however, the transaction cannot be posted.

3. Processing - if the registry switch for Plants>BRPA General>Validate Processing Health Status is selected, validation will be added to transfers based on the following options defined on the Lab Test Code. The most critical status will override others. If the farm has an 'End of Week' status for one lab test code, then that code will determine where the farm is planned for processing.

   1. Not Tracked - lab test code has no effect on the health status tracking process

   2. Tracked - lab test code is tracked on the farm or entity, however there is no further logic related to health status. It is used for reporting purposes only.

   3. End of Day  - BRPA will plan for entities to be processed at the end of the processing day. The projection for entities with this status will be displayed in a different color and the user has the option to manually move the projection.

   4. End of Week  - BRPA will plan for entities to be processed at the end of the day for the processing week. For example, if the end of week is defined as Friday, 'End of Week' entities will be processed at the end of Friday. The projection for entities with this status will be displayed in a different color and the user has the option to manually move the projection.

Before creating a Health Status transaction, the following must be created:

• Lab Test Codes

The following procedures are outlined in the Farm Health Status document:

• Creating a Farm Health Status Transaction
• Posting a Farm Health Status Transaction

Create a Farm Health Status Transaction

1. In LMTS>LIM>Transactions>Health Status, select Farms.
2. Click the button to create a new farm health status transaction.
3. In the New Record dialog box, from the Farm No drop-down menu, select the farm where the chicks are located.
4. Enter the transaction Date which will represent the test date.
5. In the Farms Health Status screen, click  to add a new transaction line.

6. From Analysis No, select the analysis code to identify the lab test.
7. Analysis Name will default in based on the selected Analysis No.
8. Ref No is a unique reference number used to identify the transaction, and can be manually or automatically entered. If system generated, the Ref No will be assigned when the record is saved.
9. From Health Status, select the status of the animals` health. Available options are Negative or Positive.
10. Transfer Control Status is a read-only field that represents the transfer status of the entity. The Transfer Control Status is defined in Lab Test Codes. Note that the registry switch for Poultry>Validate Transfer Health Status must be selected for the logic to be initiated. The following are the available options:
    1.  Not Tracked - lab test code has no effect on the health status tracking process

    2. Tracked - lab test code is tracked on the farm or entity, however there is no further logic related to health status. It is used for reporting purposes only.

    3. Transfer to the Same Status - entities can only be transferred to entities that have the same health status.

    4. No Transfer - entities cannot be transferred. The transfer transaction can be created, however, the transaction cannot be posted. 
11. Placement Control Status is a read-only field that represents the placement status of the entity. The Placement Control Status is defined in Lab Test Codes. Note that the registry switch for Poultry>Validate Placement Health Status must be selected for the logic to be initiated. The following are the available options:
    1. Not Tracked - lab test code has no effect on the health status tracking process

    2. Tracked - user will be warned if the days out defined on the lab test code has not met the required number of days. Placement can still be posted as it is only a warning message. BRPA placements will be projected based on the health status of the prior entity.

12. Processing Control Status is a read-only field that represents the processing status of the entity. The Processing Control Status is defined in Lab Test Codes. Note that the registry switch for Plants>BRPA>General>Validate Processing Health Status must be selected for the logic to be initiated. The following are the available options:
    1. Not Tracked - lab test code has no effect on the health status tracking process

    2. Tracked - lab test code is tracked on the farm or entity, however there is no further logic related to health status. It is used for reporting purposes only.

    3. End of Day  - BRPA will plan for entities to be processed at the end of the processing day. The projection for entities with this status will be displayed in a different color and the user has the option to manually move the projection.

    4. End of Week  - BRPA will plan for entities to be processed at the end of the day for the processing week. For example, if the end of week is defined as Friday, 'End of Week' entities will be processed at the end of Friday. The projection for entities with this status will be displayed in a different color and the user has the option to manually move the projection.

13. In the Comments field, enter any additional information related to the transaction.
14. The Attachment section can be used to attach any type of file related to the health status transaction.
15. Selecting the Void flag will reverse the health status check.

Post a Farm Health Status Transaction

The posting process deletes existing data for the lab test code and updates with a record type of Farm Status. Farms will only display the most recent test results for the lab test code and will be updated any time a lab test is posted for the farm regardless if the health status is negative or positive. The following is the update logic for posting health status records.

• Farm health status overrides all entity posting status
• FF overrides FFH and FFHP transactions
• FFH overrides FFHP transactions
• FFHP is only applicable to that granularity

1. In the Farm Health Status main index, select the required transaction and right-click to select 'Post'. Alternatively, click the green check mark    in the top menu bar and select 'Post'.
2. To un-post a health status transaction, select the required transaction and right-click to select 'Unpost'.  This process will set the record status to 'Reversed' status, which allows the record to be edited. The health status will be removed from the farm until the record is posted again.