Statements in which the resource exists as a subject.
PredicateObject
rdf:type
lifeskim:mentions
pubmed:issue
3
pubmed:dateCreated
2009-5-25
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.
pubmed:grant
pubmed:commentsCorrections
http://linkedlifedata.com/resource/pubmed/commentcorrection/19285570-10566317, http://linkedlifedata.com/resource/pubmed/commentcorrection/19285570-12463944, http://linkedlifedata.com/resource/pubmed/commentcorrection/19285570-12467801, http://linkedlifedata.com/resource/pubmed/commentcorrection/19285570-14728263, http://linkedlifedata.com/resource/pubmed/commentcorrection/19285570-14728577, http://linkedlifedata.com/resource/pubmed/commentcorrection/19285570-16501179, http://linkedlifedata.com/resource/pubmed/commentcorrection/19285570-16501181, http://linkedlifedata.com/resource/pubmed/commentcorrection/19285570-16779133, http://linkedlifedata.com/resource/pubmed/commentcorrection/19285570-16929044, http://linkedlifedata.com/resource/pubmed/commentcorrection/19285570-17238315, http://linkedlifedata.com/resource/pubmed/commentcorrection/19285570-17276736, http://linkedlifedata.com/resource/pubmed/commentcorrection/19285570-17693132, http://linkedlifedata.com/resource/pubmed/commentcorrection/19285570-17947616, http://linkedlifedata.com/resource/pubmed/commentcorrection/19285570-7048091, http://linkedlifedata.com/resource/pubmed/commentcorrection/19285570-9357704
pubmed:language
eng
pubmed:journal
pubmed:citationSubset
IM
pubmed:status
MEDLINE
pubmed:month
Jun
pubmed:issn
1532-0480
pubmed:author
pubmed:issnType
Electronic
pubmed:volume
42
pubmed:owner
NLM
pubmed:authorsComplete
Y
pubmed:pagination
490-3
pubmed:dateRevised
2010-9-23
pubmed:meshHeading
pubmed:year
2009
pubmed:articleTitle
The impact of SNOMED CT revisions on a mapped interface terminology: terminology development and implementation issues.
pubmed:affiliation
Clinical Informatics Consulting, Atlanta, GA, USA. gw@clinicalinformatics.us
pubmed:publicationType
Journal Article, Research Support, N.I.H., Extramural