Find additional IRI prefixes to add to terminology.hl7.org

[gaurav]

UP-364 and UP-406 have now been implemented! Once we confirm that everything looks as we expect, we should complete and submit MeSH IRIs as our next IRI stem request.

Once that's done, it would be useful to have the next IRI stem request include multiple prefixes. Here are some candidates:

1. RadLex at https://terminology.hl7.org/CodeSystem-RadLex.html

   • Prefix: http://www.radlex.org/RID/ (e.g. http://radlex.org/RID/RID10417)
   • I can't find official documentation of this, but it is used in the official RadLex OWL file, the official WebProtege ontology and on BioPortal.
   • They confirmed by e-mail that they don't have this documentation anywhere, but we can probably use the OWL file as sufficient evidence that this is the intended URL prefix.

2. Human Phenotype Ontology at https://terminology.hl7.org/CodeSystem-HPO.html

   • Prefix: http://purl.obolibrary.org/obo/HP_ (e.g. http://purl.obolibrary.org/obo/HP_0032503)
   • See https://github.com/w3c/hcls-fhir-rdf/issues/127
   • Adding this would be complicated. I think trusting in the official OWL file might be the simplest solution here.

3. MONDO Disease Ontology at https://terminology.hl7.org/CodeSystem-MONDO.html

   • Prefix: http://purl.obolibrary.org/obo/MONDO_ (e.g. http://purl.obolibrary.org/obo/MONDO_0100096)
   • See https://github.com/w3c/hcls-fhir-rdf/issues/127
   • Now documented at https://github.com/monarch-initiative/mondo?tab=readme-ov-file#identifiers

Other options:

• http://dicom.nema.org/resources/ontology/DCM
• https://evs.nci.nih.gov/ftp1/NCI_Thesaurus/Thesaurus.OWL.zip
• SNOMED?

Next steps:

• [ ] Are any of these included in the examples? It would be useful for testing.

You can assign me to this issue.

[gaurav]

RadLex is used in a FHIR example: https://www.hl7.org/fhir/R5/imagingstudy-example-xr.json.html

[gaurav]

Note that we can't currently add "iri-stem" to NamingSystem.uniqueId.type -- this change was made in FHIR R5, but terminology.hl7.org is still on FHIR R4. I think that means that we can currently add concept IRIs to CodeSystems but not to NamingSystems. Marc Duteau is looking into whether they can work around this. I'll report back if I hear more from him.

[gaurav]

For MONDO, we can reference the OBO Foundry Identifier Policy, which gives the Format of Foundry-compliant URIs as "http://purl.obolibrary.org/obo/" IDSPACE "_" LOCALID and https://mondo.readthedocs.io/en/latest/editors-guide/f-entities/, which specifies that "All classes are in MONDO ID space". I'll see if I can find similar verbiage for HPO.

[gaurav]

DECISIONS on Jun 20, 2024 meeting:

• If we can proceed with updating just CodeSystems and not NamingSystems, we should try that as a way to get the reviews moving.
• We can consider an officially published OWL file containing resource IRIs are representative of their IRI stem. Resolvable URLs are less clear, and we should only get to those once we have added IRI stems for all the resources with officially published OWL files.