Statements in which the resource exists.
SubjectPredicateObjectContext
pubmed-article:17911795rdf:typepubmed:Citationlld:pubmed
pubmed-article:17911795lifeskim:mentionsumls-concept:C0033213lld:lifeskim
pubmed-article:17911795lifeskim:mentionsumls-concept:C0028275lld:lifeskim
pubmed-article:17911795lifeskim:mentionsumls-concept:C1623497lld:lifeskim
pubmed-article:17911795lifeskim:mentionsumls-concept:C1561577lld:lifeskim
pubmed-article:17911795lifeskim:mentionsumls-concept:C1514811lld:lifeskim
pubmed-article:17911795lifeskim:mentionsumls-concept:C1706387lld:lifeskim
pubmed-article:17911795lifeskim:mentionsumls-concept:C1706462lld:lifeskim
pubmed-article:17911795pubmed:issuePt 1lld:pubmed
pubmed-article:17911795pubmed:dateCreated2007-10-3lld:pubmed
pubmed-article:17911795pubmed:abstractTextSNOMED CT was created by the merger of SNOMED RT (Reference Terminology) and Read Codes Version 3 (also known as Clinical Terms Version 3). SNOMED CT is considered to be among the most extensive and comprehensive biomedical vocabularies available today. It is considered for use as the Reference Terminology of various institutions. We review the adequacy of SNOMED CT as a Reference Terminology and discuss the issues in its use as such. We discuss issues with content coverage of various clinical domains, data integrity and validity, and the update frequency of SNOMED CT, and why SNOMED CT alone is not adequate to serve as the Reference Terminology of a healthcare organization.lld:pubmed
pubmed-article:17911795pubmed:languageenglld:pubmed
pubmed-article:17911795pubmed:journalhttp://linkedlifedata.com/r...lld:pubmed
pubmed-article:17911795pubmed:citationSubsetTlld:pubmed
pubmed-article:17911795pubmed:chemicalhttp://linkedlifedata.com/r...lld:pubmed
pubmed-article:17911795pubmed:statusMEDLINElld:pubmed
pubmed-article:17911795pubmed:issn0926-9630lld:pubmed
pubmed-article:17911795pubmed:authorpubmed-author:LauLee MinLMlld:pubmed
pubmed-article:17911795pubmed:authorpubmed-author:NachimuthuSen...lld:pubmed
pubmed-article:17911795pubmed:issnTypePrintlld:pubmed
pubmed-article:17911795pubmed:volume129lld:pubmed
pubmed-article:17911795pubmed:ownerNLMlld:pubmed
pubmed-article:17911795pubmed:authorsCompleteYlld:pubmed
pubmed-article:17911795pubmed:pagination640-4lld:pubmed
pubmed-article:17911795pubmed:dateRevised2008-7-10lld:pubmed
pubmed-article:17911795pubmed:meshHeadingpubmed-meshheading:17911795...lld:pubmed
pubmed-article:17911795pubmed:meshHeadingpubmed-meshheading:17911795...lld:pubmed
pubmed-article:17911795pubmed:meshHeadingpubmed-meshheading:17911795...lld:pubmed
pubmed-article:17911795pubmed:meshHeadingpubmed-meshheading:17911795...lld:pubmed
pubmed-article:17911795pubmed:meshHeadingpubmed-meshheading:17911795...lld:pubmed
pubmed-article:17911795pubmed:meshHeadingpubmed-meshheading:17911795...lld:pubmed
pubmed-article:17911795pubmed:meshHeadingpubmed-meshheading:17911795...lld:pubmed
pubmed-article:17911795pubmed:meshHeadingpubmed-meshheading:17911795...lld:pubmed
pubmed-article:17911795pubmed:year2007lld:pubmed
pubmed-article:17911795pubmed:articleTitlePractical issues in using SNOMED CT as a reference terminology.lld:pubmed
pubmed-article:17911795pubmed:affiliationDepartment of Biomedical Informatics, University of Utah, Salt Lake City, Utah, USA.lld:pubmed
pubmed-article:17911795pubmed:publicationTypeJournal Articlelld:pubmed
pubmed-article:17911795pubmed:publicationTypeComparative Studylld:pubmed