[prev in list] [next in list] [prev in thread] [next in thread] 

List:       openmrs-implementers
Subject:    Re: Looking for "best practices" in mapping
From:       "'Andrew Kanter' via OpenMRS Implementers" <implementers () openmrs ! org>
Date:       2014-08-18 21:46:24
Message-ID: 1408398384.65016.YahooMailNeo () web163806 ! mail ! gq1 ! yahoo ! com
[Download RAW message or body]

I answered in OpenMRS Talk too
Sara,
Generally I feel that terminology is not an easy thing for most people to do without \
additional training and that is why I created the CIEL dictionary to help people. It \
is MUCH easier to find an interface terminology which is the same thing as the term \
you are mapping (SAME-AS) and then rely on someone else's maps to get to the \
reference terminology (SNOMED, etc.). In your example, it sounds like you are trying \
to map to a categorical terminology like ICD. You could map it NARROWER-THAN to ALL \
of those. Fungal skin infection would be the closest but none of them are SAME-AS. \
However, if you are ICD coding, then there are special rules which dictate which ICD \
code should be used for a given term, and those might not be totally obvious from the \
term and the categories. In general you should only map to the closest map and not \
any that are in the same hierarchy (so Fungal infection is a parent of fungal skin \
infection and would be redundant). There are other mapping relationship types which \
might be added. You should probably not have two SAME-AS maps within the same mapped \
terminology. Happy to provide more detail if needed.
  
-------------------- 
Andrew S. Kanter, MD MPH FACMI


Asst. Prof. of Clinical Biomedical Informatics and Clinical Epidemiology

Columbia University
Email: andrew.kanter@dbmi.columbia.edu 
Mobile: +1 (646) 469-2421
Office: +1 (212) 305-4842
Skype: akanter-ippnw
Yahoo: andy_kanter


On Monday, August 18, 2014 9:57 AM, Sara Armson <sarmson@ampath.or.ke> wrote:
 

> 
> 
> I am looking for best practices for mapping concepts to another dictionary using \
> the terms: SAME-AS, NARROWER-THAN, & BROADER-THAN.   
> 
> EXAMPLE
> If I am mapping "Tinea Versicolor" (a fungal infection of the skin) and the \
> dictionary I am mapping to contains: 1) "Infection"  
> 2) "Fungal Infection"
> 3) "Fungal Skin Infection"
> 
> 
> Questions:
> Has anyone developed an internal best practice procedure for mapping an instance \
> like this? Should all 3 be mapped?  
> Should only the closest term be mapped?  
> Does mapping best practices vary based on other factors?
> Does anyone have an suggestions for developing a best practice?
> 
> 
> (I cross-posted this question here.   Please consider using  the OpenMRS Talk \
> Terminology board) 
> 
-- 
> OpenMRS Implementers: http://go.openmrs.org/implementers
> Post: implementers@openmrs.org
> Unsubscribe: implementers+unsubscribe@openmrs.org
> Manage your OpenMRS subscriptions at https://id.openmrs.org/
> To unsubscribe from this group and stop receiving emails from it, send an email to \
> implementers+unsubscribe@openmrs.org. 
> 
> 

-- 
OpenMRS Implementers: http://go.openmrs.org/implementers
Post: implementers@openmrs.org
Unsubscribe: implementers+unsubscribe@openmrs.org
Manage your OpenMRS subscriptions at https://id.openmrs.org/

To unsubscribe from this group and stop receiving emails from it, send an email to \
implementers+unsubscribe@openmrs.org.


[Attachment #3 (text/html)]

<html><body><div style="color:#000; background-color:#fff; font-family:HelveticaNeue, \
Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif;font-size:14pt"><div \
class="" style=""><span class="" style="">I answered in OpenMRS Talk \
too</span></div><div style="color: rgb(34, 34, 34); font-family: Helvetica, Arial, \
sans-serif; font-size: 14px; line-height: 19px;" class="">Sara,<br class="" \
style="">Generally I feel that terminology is not an easy thing for most people to do \
without additional training and that is why I created the CIEL dictionary to help \
people. It is MUCH easier to find an interface terminology which is the same thing as \
the term you are mapping (SAME-AS) and then rely on someone else's maps to get to the \
reference terminology (SNOMED, etc.). In your example, it sounds like you are trying \
to map to a categorical terminology like ICD. You could map it NARROWER-THAN to ALL \
of those. Fungal skin infection would be the closest but none of  them are SAME-AS. \
However, if you are ICD coding, then there are special rules which dictate which ICD \
code should be used for a given term, and those might not be totally obvious from the \
term and the categories.</div><div style="color: rgb(34, 34, 34); font-family: \
Helvetica, Arial, sans-serif; font-size: 14px; line-height: 19px;" class="">In \
general you should only map to the closest map and not any that are in the same \
hierarchy (so Fungal infection is a parent of fungal skin infection and would be \
redundant). There are other mapping relationship types which might be added. You \
should probably not have two SAME-AS maps within the same mapped \
terminology.</div><div style="background-color: transparent;" class=""><span class="" \
style=""></span></div><div style="color: rgb(34, 34, 34); font-family: Helvetica, \
Arial, sans-serif; font-size: 14px; line-height: 19px;" class="">Happy to provide \
more detail if needed.</div><div class="" style=""></div><div  class="" \
style="">&nbsp;</div><div class="" style=""><b class="" style="">-------------------- \
<br class="" style="">Andrew S. Kanter, MD MPH FACMI<br class="" style=""><span \
class="" style="font-weight: normal;"><b class="" style=""><br class="" \
style=""></b></span></b></div><div style="color:rgb(0, 0, \
0);font-size:13px;font-family:arial, helvetica, clean, \
sans-serif;background-color:transparent;font-style:normal;" class="">Asst. Prof. of \
Clinical Biomedical Informatics and Clinical Epidemiology<br class="" \
style=""></div><div style="color:rgb(0, 0, \
0);font-size:13px;background-color:transparent;font-style:normal;font-family:arial, \
helvetica, clean, sans-serif;" class="">Columbia University<br class="" \
style="">Email: andrew.kanter@dbmi.columbia.edu <br class="" style="">Mobile: +1 \
(646) 469-2421<br class="" style="">Office: +1 (212) 305-4842<br class="" \
style="">Skype: akanter-ippnw<br class="" style="">Yahoo: andy_kanter</div> <div  \
class="qtdSeparateBR"><br><br></div><div class="yahoo_quoted" style="display: \
block;"> <div style="font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, \
Lucida Grande, sans-serif; font-size: 14pt;" class=""> <div style="font-family: \
HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; \
font-size: 12pt;" class=""> <div dir="ltr" class="" style=""> <font size="2" \
face="Arial" class="" style=""> On Monday, August 18, 2014 9:57 AM, Sara Armson \
&lt;sarmson@ampath.or.ke&gt; wrote:<br class="" style=""> </font> </div> <blockquote \
style="border-left: 2px solid rgb(16, 16, 255); margin-left: 5px; margin-top: 5px; \
padding-left: 5px;" class="">  <br class="" style=""><br class="" style=""> <div \
class="" style=""><div id="yiv1562408237" class="" style=""><div dir="ltr" class="" \
style=""><div class="" style="">I am looking for best practices for mapping concepts \
to another dictionary using the terms: SAME-AS, NARROWER-THAN, &amp;  \
BROADER-THAN.&nbsp;</div><div class="" style=""><br class="" style=""></div><div \
class="" style="">EXAMPLE</div><div class="" style="">&nbsp;If I am mapping "Tinea \
Versicolor" (a fungal infection of the skin) and the dictionary I am mapping to \
contains:</div><div class="" style="">1) "Infection"&nbsp;</div><div class="" \
style="">2) "Fungal Infection"</div><div class="" style="">3) "Fungal Skin \
Infection"</div><div class="" style=""><br class="" style=""></div><div class="" \
style="">Questions:</div><div class="" style="">Has anyone developed an internal best \
practice procedure for mapping an instance like this?</div><div class="" \
style="">Should all 3 be mapped?&nbsp;</div><div class="" style="">Should only the \
closest term be mapped?&nbsp;</div><div class="" style="">Does mapping best practices \
vary based on other factors?</div><div class="" style="">Does anyone have an \
suggestions for developing a best practice?</div><div class=""  style=""><br class="" \
style=""></div><div class="" style="">(I cross-posted this question <a rel="nofollow" \
target="_blank" href="https://talk.openmrs.org/t/looking-for-best-practices-in-mapping/521/1" \
class="" style="">here</a>. &nbsp;Please consider using&nbsp;the OpenMRS Talk \
Terminology board)</div><div class="" style=""><br class="" style=""></div></div>



-- <br class="" style="">
OpenMRS Implementers: <a rel="nofollow" target="_blank" \
href="http://go.openmrs.org/implementers" class="" \
                style="">http://go.openmrs.org/implementers</a><br class="" style="">
Post: implementers@openmrs.org<br class="" style="">
Unsubscribe: implementers+unsubscribe@openmrs.org<br class="" style="">
Manage your OpenMRS subscriptions at <a rel="nofollow" target="_blank" \
href="https://id.openmrs.org/" class="" style="">https://id.openmrs.org/</a><br \
class="" style="">



To unsubscribe from this group and stop receiving emails from it, send an email to <a \
rel="nofollow" ymailto="mailto:implementers+unsubscribe@openmrs.org" target="_blank" \
href="mailto:implementers+unsubscribe@openmrs.org" class="" \
style="">implementers+unsubscribe@openmrs.org</a>.<br class="" style=""></div><br \
class="" style=""><br class="" style=""></div> </blockquote>  </div> </div>   </div> \
</div></body></html>

<p></p>

-- <br />
OpenMRS Implementers: <a \
href="http://go.openmrs.org/implementers">http://go.openmrs.org/implementers</a><br \
                />
Post: implementers@openmrs.org<br />
Unsubscribe: implementers+unsubscribe@openmrs.org<br />
Manage your OpenMRS subscriptions at <a \
href="https://id.openmrs.org/">https://id.openmrs.org/</a><br />

<p></p>

To unsubscribe from this group and stop receiving emails from it, send an email to <a \
href="mailto:implementers+unsubscribe@openmrs.org">implementers+unsubscribe@openmrs.org</a>.<br \
/>



[prev in list] [next in list] [prev in thread] [next in thread] 

Configure | About | News | Add a list | Sponsored by KoreLogic