Skip to content

fix: curate ICD10CM to Bioregistry's icd10data URI format - #80

Open
kevinschaper wants to merge 3 commits into
mainfrom
fix/icd10cm-prefix
Open

kevinschaper wants to merge 3 commits into
mainfrom
fix/icd10cm-prefix

Conversation

@kevinschaper

@kevinschaper kevinschaper commented Feb 19, 2026 •

Copy link
Copy Markdown
Contributor

Summary

  • The pinned bioregistry release makes https://icd.codes/icd10cm/ the canonical ICD10CM namespace. That host has been dead since 2025-07 and Bioregistry now marks the provider as gone.
  • Following @matentzn's pointer, this follows Bioregistry's own URI format, https://www.icd10data.com/search?s=, by adding ICD10CM to linked_data.curated.yaml. It is a search page rather than a concept URI, but it is what Bioregistry resolves to, and a later bioregistry bump will agree with it instead of fighting the override.
  • icd.codes and the BioPortal PURL stay as prefix_alias rows, so compression of existing URIs keeps working.
  • Adds a regression test that checks the canonical namespace in linked_data and the three merged contexts, and the aliases in the dynamically merged context.

For reviewers

  • Rebuilt on current main. The earlier version of this PR carried a stale make etl refresh and a Poetry 2 lock file; both are gone.
  • The CSV rows were produced with the package's own ingest, merge and writer. Only the ICD10CM rows change. A full make etl was not run, to avoid burying this in an upstream refresh.
  • CI will show the test_w3id failure until fix: read w3id namespaces from ids/ after upstream move #84 is merged. It also fails on main.

https://claude.ai/code/session_01GvqCPLs6vPfQbS73ca2jJw

Comment thread src/prefixmaps/data/linked_data.csv Outdated
linkml,biolink,https://w3id.org/biolink/vocab/,canonical
linkml,dcterms,http://purl.org/dc/terms/,canonical
linkml,foaf,http://xmlns.com/foaf/0.1/,canonical
linkml,ICD10CM,http://purl.bioontology.org/ontology/ICD10CM/,canonical

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I am not against this, note that Bioregistrysuggests this:

https://www.icd10data.com/search?s=

Which is a bit of a hack - redirecting to the search page rather than the concept page for which you cant construct a URI.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good call, thanks. I've switched this to Bioregistry's https://www.icd10data.com/search?s= so we follow upstream rather than carrying a local opinion. Bioregistry now marks the icd.codes provider as gone (2025-07-28), so the pinned release here is just behind. The BioPortal PURL and icd.codes remain as prefix aliases. Branch is rebuilt on current main with only the ICD10CM rows changed.

@matentzn

matentzn commented Jul 1, 2026

Copy link
Copy Markdown

Did you think about this @kevinschaper

Older bioregistry releases, including the one pinned here, make
https://icd.codes/icd10cm/ the canonical ICD10CM namespace. That host
has been dead since 2025-07 and Bioregistry now marks the provider as
gone; its own URI format is https://www.icd10data.com/search?s=.

Add ICD10CM to linked_data.curated.yaml with that namespace, so the
merged contexts follow Bioregistry regardless of the pinned release.
icd.codes and the BioPortal PURL stay as prefix aliases.

The CSV rows were produced with the package's own ingest, merge and
writer, and only the ICD10CM rows change. A full `make etl` was not
run, to avoid burying this in an upstream refresh.

Claude-Session: https://claude.ai/code/session_01GvqCPLs6vPfQbS73ca2jJw
@kevinschaper kevinschaper changed the title fix: override ICD10CM canonical prefix to use purl.bioontology.org fix: curate ICD10CM to Bioregistry's icd10data URI format Nov 6, 2026

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants