CTS2/doc/ExternalURI
Introduction
Section 2.1.3 of CTS2 Core Model Specification differentiates persistent and local URI's. Local URI's resolve to "digital resources" that serve to describe external resources. Persistent URI's reference resources that the CTS2 information is about.
While CTS2 supports the ability to reference the same resource (Class, Property, Individual, Code System, Map, Document, ...) with more than one URI, it is still in everyone's best interest to use as few URI's for any given resource as is possible - ideally, one. To accomplish this goal, the CTS2 community has been actively pursuing the establishment of official URI's - ideally sanctioned by the body that is primarily responsible for publishing the terminologies themselves.
Ideally, an official, sanctioned URI will have the following characteristics:
- It will use the http protocol
- The host portion of the URI will be owned by the same organization that publishes the terminology, map, value set or other resource
- The URI will resolve to a page that will, at a bare minimum, confirm that the URI is, indeed, sanctioned by the publishing body.
The sections below describe the various URI schemes that are in various stages of being implemented:
URI Schemes
IHTSDO / SNOMED CT
- Documentation:
- SNOMED CT URI Specification (Version 0.5, January 2013) - internal document, not yet published
- SNOMED CT URI Guide (Version 0.3, January 7, 2013) - internal document, not yet published
- Base URI: http://snomed.info/
- Code System -
- Editions - http://snomed.info/sct/{sctid}
- Modules - http://snomed.info/module/{sctid}
- Code System Version
- Concept Identifiers - http://snomed.info/id/{sctid}
- Relationship Identifiers - http://snomed.info/id/{sctid}
- Description Identifiers - http://snomed.info/id/{sctid}
- Refset Entry Identifiers - http://snomed.info/id/{uuid}
- Columns in release files - http://snomed.info/field{tablename}.{fieldname}
The CTS2 Implementation Guide proposes the following additions:
- Value Set
- Simple Refset (Value Set) - http://snomed.info/id/{sctid} (sctid is the refsetId)
- Version of Simple Refset - http://snomed.info/id/{sctid}/version/{timestamp} - where timestamp is the timestamp of the describing module
- Map
- Simple of Complex Map (Map) - http://snomed.info/id/{sctid} (sctid is the map refsetId)
- Version of Map - http://snomed.info/id/{sctid}/version/{timestamp} - where timestamp is the timestamp of the describing module
WHO / ICD, etc.
The following documentation is not yet final and is awaiting verification from the WHO.
- Documentation: - (not yet published)
- Base URI: http://id.who.int/
- Code System -
- ICD-9 - http://id.who.int/icd/release/9
- ICD-10 - http://id.who.int/icd/release/10
- ICD-11 morbidity linearization - http://id.who.int/icd/release/11/morbidity
- ICD-11 mortality linearization - http://id.who.int/icd/release/11/mortality
- ICD-11 foundation layer - http://id.who.int/icd/entity
- Code System Version - Note that, in the ICD world, there is a distinction between release (icd-8, icd-9, icd-10) and version (icd-9 2010, icd-10 2012). From the CTS2 perspective, releases are different code systems (as, unfortunately, are national modifications...). Versions, however, are simply variants. We recognize the fact that ICD codes sometimes get re-purposed across versions.
- ICD-9 2010 - http://id.who.int/icd/release/9/version/2010
- ICD-10 2013 - http://id.who.int/icd/release/10/version/2013
(to be continued)
HL7
To date, HL7 has used ISO Object Identifiers (OIDS) to reference code systems and value sets. Unfortunately, there is no sanctioned algorithmic way to reference versions of code systems, concepts in code systems or specific definitions (versions) of value sets without assigning a unique numeric identifier to each resource. While the OID approach works in structured data represented in the HL7 V3 or ISO 21090 data types, there is currently no way to represent a specific concept in a specific code system as a single URI. For this reason, we advocate the use of http URI's throughout.
Fortunately, HL7 is encountering the same issue as part of the MIF to OWL conversion project. More to come shortly
UMLS
An ideal URI would be created by the terminology publisher, as described in the previous sections. When this is not available, however, the next option is to use a URI generated by an authoritative resource that is knowledgeable about the terminology publisher and can act as a proxy for the actual publisher. The NLM fits this role perfectly when it comes to the medical terminologies that are published in the UMLS. The NLM has proposed the following identification scheme:
- Base URI: http://umls.nlm.nih.gov/
- Code System: http://umls.nlm.nih.gov/sab/{RSAB} - where RSAB is the UMLS Root Source Abbreviation.
- http://umls.nlm.nih.gov/sab/FMA - Foundational Model of Anatomy
- http://umls.nlm.nih.gov/sab/LNC - LOINC
- http://umls.nlm.nih.gov/sab/MTH - UMLS Metathesaurus itself
- Code System Version: http://umls.nlm.nih.gov/sab/{RSAB}/version/{VSAB} - where VSAB is the UMLS Version Source Abbreviation
- http://umls.nlm.nih.gov/sab/FMA/version/FMA3_1
- http://umls.nlm.nih.gov/sab/LNC/version/LNC238 - LOINC version 238
- http://umls.nlm.nih.gov/sab/MTH/version/MTH2012AA - UMLS Metathaurus 2012AA release (Note: this VSAB will have to be added to the UMLS)
- Concept Code: The UMLS URI's will differentiate three different types of concept identifier:
- Source CUI: http://umls.nlm.nih.gov/sab/{RSAB}/scui/{SCUI} - Concept UNIQUE identifier in the context of the publishing organization
- http://umls.nlm.nih.gov/sab/RXNORM/scui/310115 - EPINEPHRINE BITARTRATE 0.3MG INHALATION AEROSOL W/ADAPTER (ML) in RxNORM
- http://umls.nlm.nih.gov/sab/FMA/scui/86917 - Musculature of abdomen in FMA
- http://umls.nlm.nih.gov/sab/LNC/scui/5964-2 - Prothrombin time (PT) in Blood by Coagulation assay
- UMLS CUI: http://umls.nlm.nih.gov/sab/MTH/cui/{CUI}
- http://umls.nlm.nih.gov/sab/MTH/cui/C0365405 - UMLS concept code for Prothrombin time (PT) in Blood by Coagulation assay
- Source CUI: http://umls.nlm.nih.gov/sab/{RSAB}/scui/{SCUI} - Concept UNIQUE identifier in the context of the publishing organization
- Value Set: - (to be determined)
- Value Set Definition: - (to be determined)
- Resolved Value Set: - (to be determined)
- Map:
- Map Version: