ADL Terminology Binding

Revision as of 10:14, 11 January 2013 by Harold solbrig (Talk | contribs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

Proposal for ADL Terminology Binding


  1. Value Set Identifiers should be representable as URI's
    1. All CIMI authored value sets will derive their identifiers and URIs from the SNOMED CT CIMI namespace. This applies whether the content of the value set is in SNOMED CT space or not.
    2. Existing value sets will derive their URI's from the URI construction rules (ref)
  2. The 'canonical' and exchange format for value sets will be CTS2.
    1. "Extensional" value sets will be represented as ResolvedValueSet constructs. Optionally, "Extensional" value sets may be represented as ValueSetDefinition<code> constructs with
    2. Mappings and tools will be provided for translation between CTS2 and the HL7 Terminfo Extension formats and the IHTSDO value set definition grammar.


  1. Coded Terms - We need to provide an additional section that associates <code>terminology_id with a URI. A separate issue is whether the CIMI group wants to establish a separate namespace for the terminology_identifiers themselves - whether they want to assert that SNOMED CT will always be identified by the terminology identifier "snomed_ct" or whether they want to use more of the approach used by XML - where every document has a declarations section that maps document specific identifiers (e.g. xmlns:snomed_ct=""). The FHIR group is trying to take the more global approach, but Mayo's experience has been that it is hard enough to settle on a URI, let alone decide whether "SCT", "SNOMED CT", "snm", etc. is the official representation. Note: IF the decision is made to take the global approach, what CIMI would actually be doing is establishing a namespace. We would recommend that a scoping namespace be provided so that the world outside CIMI (yes - there is such a thing ;-) ) can formally say "snomed_ct" as it is defined by CIMI.



  1. Global Term Bindings
  2. Path Based Bindings
  3. Constraint_bindings
  4. Ordinal