Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add Animal Health Status to Animal Resource #148

Closed
thomasd-gea opened this issue Aug 31, 2020 · 8 comments
Closed

Add Animal Health Status to Animal Resource #148

thomasd-gea opened this issue Aug 31, 2020 · 8 comments
Labels
stale-issue Identifies that an issue is stale and will be closed unless reactivated. this-release Scheduled to be implemented for this release in development

Comments

@thomasd-gea
Copy link
Contributor

In issue #111 we discussed reproduction and lactation status values. In addition to this, a health status of an animal would also be very helpful. As possible values I'd like to propose:

  • Healthy
  • Suspicious
  • Ill
  • In Treatment
  • To Be Culled

On the animal, this would be an additional field defining the current status. In addition to this, a Health Check Event could be added so that an observation of a changed health status can be filed.

I think, the Health Check Event could be a little bit more complicated because you might need diagnosis codes etc., however, if everyone is OK with the status field at the animal I could add the health status field already for the 1.1 release.

@cookeac
Copy link
Collaborator

cookeac commented Sep 1, 2020

There has already been a lot of work done on health diagnosis, which I think covers the coding mentioned above.

When we initially raised the prospect of a Health Status, there was recognition that some more work needed to be done to determine both an appropriate enumeration (the set above looks like a good start), and also to think about how that might interact with different systems. I think we need to have that discussion before including in ADE 1.1. What do others think?

Also:

  • For me, in treatment and to be culled would typically be group (set) functions, and there might be several treatment groups.
  • If I were after one key piece of health information for an animal, it would be the withdrawal status of the animal (to save me having to process through all the health treatments to see if the animal could be milked, sold, culled, etc).

@erwinspeybroeck
Copy link
Collaborator

We didn't have until now a use case for a health status of an animal, although it seems logical and consistent to have one.

Regarding the withdrawal status we created an API with which one can ask for the current status regarding withdrawal on a location:
GET /{market-country-code}/customer/{customer-id}/indications/waiting-periods
with a response
[
{
"animalId": scheme + id,
"releaseMilkDateTime": "2020-09-02T05:55:17.114Z",
"indicationMilk" : enum : colostrum, antibiotics
"releaseMeatDateTime": "2020-09-02T05:55:17.114Z",
"antibioticsTestNeeded": true,
"numberOfAntibioticsTestsDone": 0,
"latestAntibioticsTestResult": true
}
]
This is based on specific conditions in the Netherlands and Belgium
In the Netherlands a farmer is obliged to withdraw milk during the first 3 days after calving
In Belgium a farmer needs, in case of antibiotics used in a treatment, at the end of the withdrawal period to perform a test on antibiotics, and only if that is showing a negative result he can release the milk.
Possibly there are other conditions in other countries ... I would be interested to know.

@cookeac cookeac added the enhancement New feature or request label Sep 11, 2020
@cookeac cookeac added this-release Scheduled to be implemented for this release in development and removed enhancement New feature or request labels Sep 28, 2020
@thomasd-gea
Copy link
Contributor Author

If we want to integrate this into the release, we should at least think about:

  • do we need "icarHealthStatusObservedEventRessoure"?
  • should the diagnosis event also get the same enum as a field? The diagnosis would then "imply" the new status of the animal after the event
  • do we want other/more/less values?

@cookeac cookeac removed the this-release Scheduled to be implemented for this release in development label May 6, 2021
@stale
Copy link

stale bot commented Sep 23, 2021

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale-issue Identifies that an issue is stale and will be closed unless reactivated. label Sep 23, 2021
@thomasd-gea
Copy link
Contributor Author

@AndreasSchultzGEA can you please take this issue with you into one of the next meetings? Maybe someone can propose a better enum set for the values?

@stale stale bot removed the stale-issue Identifies that an issue is stale and will be closed unless reactivated. label Sep 24, 2021
@AndreasSchultzGEA
Copy link
Collaborator

There is a PR prepared #253 which contains the ideas of this discussion.
Please review and provide information e.g. about the values of the health-status-values.

The withdrawal-topics should better be put into a separated issue.

@cvigorsICBF
Copy link
Collaborator

I mentioned the possibility of the status of 'Very Ill" on the call this morning that I thought I saw third party software using. I've had a quick look though the documentation, but I can't confirm that it is used. Therefore this suggestion can be ignored.

@cookeac cookeac added this-release Scheduled to be implemented for this release in development agenda-next-meeting labels Oct 7, 2021
@stale
Copy link

stale bot commented Feb 2, 2022

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale-issue Identifies that an issue is stale and will be closed unless reactivated. label Feb 2, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
stale-issue Identifies that an issue is stale and will be closed unless reactivated. this-release Scheduled to be implemented for this release in development
Projects
None yet
Development

No branches or pull requests

5 participants