Skip to content

Standardise or make it possible to discover extended reason codes for death, departure, and do not breed #533

@cookeac

Description

@cookeac

Issue #454 defined an icarReasonIdentifierType to support the country-specific extended reason codes, and defined a central place to register these here: https://github.com/adewg/ICAR/blob/ADE-1/types/icarReasonIdentifierType.json

However, this is human-readable, and the form in which dairy data organisations (DDOs) or other country-specific recording services organise their reason lists are not specified.

It would be helpful if:

  • ADE contained a master list of reason identifier schemes in JSON format to make it easy for software developers to use, and
  • The content of the human-readable format should be specified so that DDOs and recording services know what to provide, and
  • ADE specified a simple JSON format (schema) that DDOs could publish, and that software vendors could then ingest to configure their software. This would save software vendors time from having to code their own list of values and mappings for each country. This would also mean that DDOs could maintain their own schemes on their own server, and the display label could be provided in their local translation (rather than a centralised service).

An example JSON specification might be something like the following (this is overly simplistic and not a real proposal):

{
   "code": "ABCD",
   "displayLabel" : "Acute Binary Mastitis",
   "description" : "The cause of departure is acute binary mastitis",
   "mapping" [ { "enumeration" : "icarDepartureReasonType", "value": "Mastitis" }, 
                       { "enumeration" : "icarDeathReasonType", "value" : "Disease" }]
}

Metadata

Metadata

Assignees

No one assigned

    Labels

    agenda-next-meetingnext-minor-releaseThe issue is not scheduled for the current release, but planned for a release soon after that.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions