Difference between revisions of "ADL Terminology Binding"

From CIMI
Jump to: navigation, search
(Created page with "Proposal for ADL Terminology Binding: # '''Value Set Identifiers should be representable as URI's''' ## ''' ''All'' CIMI authored value sets will derive their identifiers and...")
 
Line 2: Line 2:
  
 
# '''Value Set Identifiers should be representable as URI's'''
 
# '''Value Set Identifiers should be representable as URI's'''
## ''' ''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.
+
## ''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.
## ''' Existing value sets will derive their URI's from the URI construction rules (ref) '''
+
## Existing value sets will derive their URI's from the URI construction rules (ref)
 
# '''The 'canonical' and exchange format for value sets will be CTS2. '''  
 
# '''The 'canonical' and exchange format for value sets will be CTS2. '''  
 
## "Extensional" value sets will be represented as <code>ResolvedValueSet</code> constructs.  Optionally, "Extensional" value sets may be represented as <code>ValueSetDefinition<code> constructs with
 
## "Extensional" value sets will be represented as <code>ResolvedValueSet</code> constructs.  Optionally, "Extensional" value sets may be represented as <code>ValueSetDefinition<code> constructs with
 +
## Mappings and tools will be provided for translation between CTS2 and the HL7 Terminfo Extension formats and the IHTSDO value set definition grammar.
 +
# ''' Global Term Bindings '''
 +
# ''' Path Based Bindings '''
 +
# ''' Constraint_bindings '''
 +
# ''' Ordinal '''

Revision as of 11:26, 10 January 2013

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.
  3. Global Term Bindings
  4. Path Based Bindings
  5. Constraint_bindings
  6. Ordinal