| pubmed-article:19285570 | rdf:type | pubmed:Citation | lld:pubmed |
| pubmed-article:19285570 | lifeskim:mentions | umls-concept:C1527148 | lld:lifeskim |
| pubmed-article:19285570 | lifeskim:mentions | umls-concept:C0033213 | lld:lifeskim |
| pubmed-article:19285570 | lifeskim:mentions | umls-concept:C0439617 | lld:lifeskim |
| pubmed-article:19285570 | lifeskim:mentions | umls-concept:C0024779 | lld:lifeskim |
| pubmed-article:19285570 | lifeskim:mentions | umls-concept:C2698172 | lld:lifeskim |
| pubmed-article:19285570 | lifeskim:mentions | umls-concept:C1708533 | lld:lifeskim |
| pubmed-article:19285570 | lifeskim:mentions | umls-concept:C0028275 | lld:lifeskim |
| pubmed-article:19285570 | lifeskim:mentions | umls-concept:C1623497 | lld:lifeskim |
| pubmed-article:19285570 | lifeskim:mentions | umls-concept:C1708476 | lld:lifeskim |
| pubmed-article:19285570 | lifeskim:mentions | umls-concept:C1706387 | lld:lifeskim |
| pubmed-article:19285570 | pubmed:issue | 3 | lld:pubmed |
| pubmed-article:19285570 | pubmed:dateCreated | 2009-5-25 | lld:pubmed |
| pubmed-article:19285570 | pubmed:abstractText | Large-scale mapping efforts have been done in attempts to migrate systems that use proprietary concepts to ones that use terminological standards such as SNOMED CT. As efforts move towards implementation, the target maps should retain a predictable structure including those targets requiring post-coordination of SNOMED CT concepts. In this paper, we compared the editorial guidelines of two versions of SNOMED CT (January 2005 and July 2006, respectively) and noted how the revisions affected a single, comprehensive set of mapped concepts (n=2002) from a legacy system. Changes made to the categories and guidelines for approved attributes were noted and then evaluated against the post-coordinated maps (n=1570) from the original mapping effort. Seventy-one percent (n=1118) of the concepts were affected due to changes made in either SNOMED CT categories or to the revision of approved attributes. While the efforts of each subsequent SNOMED CT version aim for continual improvement, changes made to its core structure and post-coordination guidelines make it more difficult to migrate proprietary data to this reference standard. Attention must be paid to auditing the processes used in terminology development to include the impact that their revisions may have on real-world clinical implementation. | lld:pubmed |
| pubmed-article:19285570 | pubmed:grant | http://linkedlifedata.com/r... | lld:pubmed |
| pubmed-article:19285570 | pubmed:commentsCorrections | http://linkedlifedata.com/r... | lld:pubmed |
| pubmed-article:19285570 | pubmed:commentsCorrections | http://linkedlifedata.com/r... | lld:pubmed |
| pubmed-article:19285570 | pubmed:commentsCorrections | http://linkedlifedata.com/r... | lld:pubmed |
| pubmed-article:19285570 | pubmed:commentsCorrections | http://linkedlifedata.com/r... | lld:pubmed |
| pubmed-article:19285570 | pubmed:commentsCorrections | http://linkedlifedata.com/r... | lld:pubmed |
| pubmed-article:19285570 | pubmed:commentsCorrections | http://linkedlifedata.com/r... | lld:pubmed |
| pubmed-article:19285570 | pubmed:commentsCorrections | http://linkedlifedata.com/r... | lld:pubmed |
| pubmed-article:19285570 | pubmed:commentsCorrections | http://linkedlifedata.com/r... | lld:pubmed |
| pubmed-article:19285570 | pubmed:commentsCorrections | http://linkedlifedata.com/r... | lld:pubmed |
| pubmed-article:19285570 | pubmed:commentsCorrections | http://linkedlifedata.com/r... | lld:pubmed |
| pubmed-article:19285570 | pubmed:commentsCorrections | http://linkedlifedata.com/r... | lld:pubmed |
| pubmed-article:19285570 | pubmed:commentsCorrections | http://linkedlifedata.com/r... | lld:pubmed |
| pubmed-article:19285570 | pubmed:commentsCorrections | http://linkedlifedata.com/r... | lld:pubmed |
| pubmed-article:19285570 | pubmed:commentsCorrections | http://linkedlifedata.com/r... | lld:pubmed |
| pubmed-article:19285570 | pubmed:commentsCorrections | http://linkedlifedata.com/r... | lld:pubmed |
| pubmed-article:19285570 | pubmed:language | eng | lld:pubmed |
| pubmed-article:19285570 | pubmed:journal | http://linkedlifedata.com/r... | lld:pubmed |
| pubmed-article:19285570 | pubmed:citationSubset | IM | lld:pubmed |
| pubmed-article:19285570 | pubmed:status | MEDLINE | lld:pubmed |
| pubmed-article:19285570 | pubmed:month | Jun | lld:pubmed |
| pubmed-article:19285570 | pubmed:issn | 1532-0480 | lld:pubmed |
| pubmed-article:19285570 | pubmed:author | pubmed-author:RosenbloomS... | lld:pubmed |
| pubmed-article:19285570 | pubmed:author | pubmed-author:WadeGeraldine... | lld:pubmed |
| pubmed-article:19285570 | pubmed:issnType | Electronic | lld:pubmed |
| pubmed-article:19285570 | pubmed:volume | 42 | lld:pubmed |
| pubmed-article:19285570 | pubmed:owner | NLM | lld:pubmed |
| pubmed-article:19285570 | pubmed:authorsComplete | Y | lld:pubmed |
| pubmed-article:19285570 | pubmed:pagination | 490-3 | lld:pubmed |
| pubmed-article:19285570 | pubmed:dateRevised | 2010-9-23 | lld:pubmed |
| pubmed-article:19285570 | pubmed:meshHeading | pubmed-meshheading:19285570... | lld:pubmed |
| pubmed-article:19285570 | pubmed:meshHeading | pubmed-meshheading:19285570... | lld:pubmed |
| pubmed-article:19285570 | pubmed:meshHeading | pubmed-meshheading:19285570... | lld:pubmed |
| pubmed-article:19285570 | pubmed:year | 2009 | lld:pubmed |
| pubmed-article:19285570 | pubmed:articleTitle | The impact of SNOMED CT revisions on a mapped interface terminology: terminology development and implementation issues. | lld:pubmed |
| pubmed-article:19285570 | pubmed:affiliation | Clinical Informatics Consulting, Atlanta, GA, USA. gw@clinicalinformatics.us | lld:pubmed |
| pubmed-article:19285570 | pubmed:publicationType | Journal Article | lld:pubmed |
| pubmed-article:19285570 | pubmed:publicationType | Research Support, N.I.H., Extramural | lld:pubmed |
| http://linkedlifedata.com/r... | pubmed:referesTo | pubmed-article:19285570 | lld:pubmed |
