Search
Back 

Forums

Welcome to the Forums for DTS 4. The following shortcuts are available for new posts and replies.

[br] = line break/new paragraph    [b] [/b] = bold font   
[i] [/i] = italicized font [u] [/u] = underlined font 
[sub] [/sub] = subscript text 
 [strike] [/strike] = strikethrough
[sub] [/sup] = superscript text    

DTS Forums

Map concepts from different namespaces
Last Post 18 Jun 2014 05:42 PM by Dr. DiTS. 1 Replies.
Printer Friendly
  •  
  •  
  •  
  •  
  •  
Sort:
PrevPrev NextNext
You are not authorized to post a reply.
Author Messages
Alba GarciaUser is Offline
New Member
New Member
Posts:47


--
17 Jun 2014 12:53 PM
    I would like to map one concept from namespace 1 to other concept in namespace 2 (both thesaurus).

    ¿Is it possible?

    How can I do it?

    Thanks in advance!
    Dr. DiTSUser is Offline
    Basic Member
    Basic Member
    Posts:110


    --
    18 Jun 2014 05:42 PM
    Mapping between namespaces is typically implemented via properties or associations. Some things to consider:



    1. Attribute Type – You will need to create metadata (a Property Type or Association Type) to represent the mapping. The type can be created in the source namespace, the target namespace, or even a separate, third namespace. Generally, the location of the type should represent the “authority” for the mapping, i.e., who is responsible for the mapping. In the case of SNOMED CT, for example, the mapping to ICD-9-CM is delivered as part of the SCT distribution, so the type would appropriately be created in the SNOMED namespace. If you (or another third party) created the mapping, then you might want to create a new namespace (“Jack’s Mapping”) and create the Attribute type here.


    2. Property Maps – One technique is to create a map Property whose Property value is the name or code of target (mapped) concept. Thus a Map-to-ICD-9 property on Myocardial Infarction in SCT might have a value of “410.9” referring to the ICD-9-CM code. Map Properties are relatively easy to create and do not require that the target namespace be present in order to populate. The downside is that when accessing the mapped concept, a separate lookup must be performed using the name or code in the Property value.


    3. Association Maps – Probably the most common map technique is to create an Concept Association between the two concepts. Use of Concept Associations requires that both the source and target namespaces be present when the association is created, but traversal is more efficient since after accessing the source concept’s associations, these associations contain direct links to the target concept.


    Hope this helps.
    You are not authorized to post a reply.


    Apelon

    We are a privately held international software and informatics company focusing on data standardization and interoperability. Apelon’s software and professional services help leading healthcare enterprises, HIT vendors and integrators, life sciences organizations and government agencies better manage standard terminologies and transition local data to these standards. Our solutions enable semantic interoperability, consistent data analysis, and standardized reporting of health information to improve the quality, comparability, and accessibility of clinical data.

    Latest Tweets

    Copyright 2019 by Apelon, Inc.