-
Notifications
You must be signed in to change notification settings - Fork 74
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 ICD11 as a prefix for Disease #1531
Comments
Note that other Monarch Initiative projects use the prefix |
bioregistry defines @gaurav - which resources are you consuming with this set of cross references? Primarily MONDO? |
Yup, primarily MONDO! I'm happy to translator |
I saw the release candidate and there's an inconsistency in the format of "ICD11". At the top (line 80), the format is all-lowercase Note: if the desired format is |
Hi @colleenXu - yes, I agree, it is inconsistent. We're in the middle of trying to reconcile all of this with bioregistry, bioportal, and linkml/prefixmaps. I hope by the time this all gets done in those repos, that we'll have a capitalized version of the prefix to match the others, but I wanted to get a "stop-gap" prefix in place in the meantime as this kind of work often takes awhile. |
So in the meantime...should the release candidate be consistent in all lower-case or all-caps? |
Is your feature request related to a problem? Please describe.
Biolink Model supports
ICD9
andICD10
as prefixes for Disease:biolink-model/biolink-model.yaml
Lines 8136 to 8186 in a2ec41e
We should also support
ICD11
, which came out in Nov 2021. NodeNorm would like to add support for ICD11 mappings, but this would requireICD11
becoming an allowed prefix in the Biolink Model.What working group (or team) did this request originate from?
NodeNorm (Translator SRI)
Note: This is relevant for members of NCATS Translator.
Describe the solution you'd like
Add
ICD11
as a prefix for Disease (presumably just aboveICD10
).Additional information to support this request (optional)
N/A
Tag relevant members for discussion
@sierra-moxon
The text was updated successfully, but these errors were encountered: