Add prefix [icd11.foundation]

[sierra-moxon]

Prefix

icd11.foundation

Name

International Classification of Diseases 11th Revision, Foundation

Homepage

https://icd.who.int/en

Source Code Repository

No response

Description

ICD11 foundation is the ontology underlying the ICD 11 codes.
Separate from a linearization, the single parent hierarchy from ICD 10, where there are chapters (e.g., Q24), sections (e.g., Q24.11-23), and actual codes (e.g. Q24.23), the icd11.foundation is more like an ontology.

License

No response

Publications

No response

Example Local Unique Identifier

1048673005

Regular Expression Pattern for Local Unique Identifier

^\d+$

URI Format String

http://id.who.int/icd/entity/$1

Wikidata Property

No response

Contributor Name

Sierra Moxon

Contributor GitHub

sierra-moxon

Contributor ORCiD

0000-0002-8719-7760

Contributor Email

[email protected]

Contact Name

No response

Contact ORCiD

No response

Contact GitHub

No response

Contact Email

No response

Additional Comments

prefix: icd11.foundation
expansion: http://purl.obolibrary.org/obo/mondo/sources/icd11foundation/

I'm unsure if this should replace the current icd11 prefix in Bioregistry or exist in addition to that prefix. But I do know that I need icd11.foundation somewhere in the registry to support: biolink/biolink-model#1531

resolvable URL: https://icd.who.int/browse/2024-01/foundation/en#1048673005
alternative URI: http://id.who.int/icd/entity/1048673005

[matentzn]

In the additional comment it says

expansion: http://purl.obolibrary.org/obo/mondo/sources/icd11foundation/

That should not be added to the record :P

[sierra-moxon]

Just three issues and three PRs (so far) to get this prefix going.

Could we improve this process?

use case:

• I need to make code-review changes to a PR that was automatically created
  issues:
• I don't have permission to edit files associated with the PR b/c the automated user created the PR (and likely I don't have write permission on the repo)
• I don't have permission to close the automated PR (even if I made a fork and issued a new PR, I'd still leave a trail of cruft behind)
• the PR automation doesn't re-trigger if we close and reopen the issue with changes

Some options:

• there is a GH settings/option called "Allow edits by maintainers" that allows users with write access to the repository (e.g., repository collaborators) to edit on a PR (I'd be happy with permission to edit my PRs)
• figure out how to re-trigger/edit PR based on changes to the templated fields in the issue

[matentzn]

Agreed @sierra-moxon

We actually use a comment "ontobot, go" or some such to instruct a GitHub action to reissue the pr when the op changed.. (in mondo). Maybe something like that can be done here. Or else what you suggest!