Statements in which the resource exists.
SubjectPredicateObjectContext
pubmed-article:21324188rdf:typepubmed:Citationlld:pubmed
pubmed-article:21324188lifeskim:mentionsumls-concept:C0030705lld:lifeskim
pubmed-article:21324188lifeskim:mentionsumls-concept:C0024117lld:lifeskim
pubmed-article:21324188lifeskim:mentionsumls-concept:C0805701lld:lifeskim
pubmed-article:21324188lifeskim:mentionsumls-concept:C2349101lld:lifeskim
pubmed-article:21324188lifeskim:mentionsumls-concept:C1137111lld:lifeskim
pubmed-article:21324188lifeskim:mentionsumls-concept:C2600053lld:lifeskim
pubmed-article:21324188pubmed:dateCreated2011-3-9lld:pubmed
pubmed-article:21324188pubmed:abstractTextAdministrative data is often used to identify patients with chronic obstructive pulmonary disease (COPD), yet the validity of this approach is unclear. We sought to develop a predictive model utilizing administrative data to accurately identify patients with COPD.lld:pubmed
pubmed-article:21324188pubmed:commentsCorrectionshttp://linkedlifedata.com/r...lld:pubmed
pubmed-article:21324188pubmed:commentsCorrectionshttp://linkedlifedata.com/r...lld:pubmed
pubmed-article:21324188pubmed:commentsCorrectionshttp://linkedlifedata.com/r...lld:pubmed
pubmed-article:21324188pubmed:commentsCorrectionshttp://linkedlifedata.com/r...lld:pubmed
pubmed-article:21324188pubmed:commentsCorrectionshttp://linkedlifedata.com/r...lld:pubmed
pubmed-article:21324188pubmed:commentsCorrectionshttp://linkedlifedata.com/r...lld:pubmed
pubmed-article:21324188pubmed:commentsCorrectionshttp://linkedlifedata.com/r...lld:pubmed
pubmed-article:21324188pubmed:commentsCorrectionshttp://linkedlifedata.com/r...lld:pubmed
pubmed-article:21324188pubmed:commentsCorrectionshttp://linkedlifedata.com/r...lld:pubmed
pubmed-article:21324188pubmed:commentsCorrectionshttp://linkedlifedata.com/r...lld:pubmed
pubmed-article:21324188pubmed:commentsCorrectionshttp://linkedlifedata.com/r...lld:pubmed
pubmed-article:21324188pubmed:commentsCorrectionshttp://linkedlifedata.com/r...lld:pubmed
pubmed-article:21324188pubmed:commentsCorrectionshttp://linkedlifedata.com/r...lld:pubmed
pubmed-article:21324188pubmed:commentsCorrectionshttp://linkedlifedata.com/r...lld:pubmed
pubmed-article:21324188pubmed:commentsCorrectionshttp://linkedlifedata.com/r...lld:pubmed
pubmed-article:21324188pubmed:commentsCorrectionshttp://linkedlifedata.com/r...lld:pubmed
pubmed-article:21324188pubmed:commentsCorrectionshttp://linkedlifedata.com/r...lld:pubmed
pubmed-article:21324188pubmed:commentsCorrectionshttp://linkedlifedata.com/r...lld:pubmed
pubmed-article:21324188pubmed:commentsCorrectionshttp://linkedlifedata.com/r...lld:pubmed
pubmed-article:21324188pubmed:commentsCorrectionshttp://linkedlifedata.com/r...lld:pubmed
pubmed-article:21324188pubmed:commentsCorrectionshttp://linkedlifedata.com/r...lld:pubmed
pubmed-article:21324188pubmed:commentsCorrectionshttp://linkedlifedata.com/r...lld:pubmed
pubmed-article:21324188pubmed:commentsCorrectionshttp://linkedlifedata.com/r...lld:pubmed
pubmed-article:21324188pubmed:commentsCorrectionshttp://linkedlifedata.com/r...lld:pubmed
pubmed-article:21324188pubmed:commentsCorrectionshttp://linkedlifedata.com/r...lld:pubmed
pubmed-article:21324188pubmed:commentsCorrectionshttp://linkedlifedata.com/r...lld:pubmed
pubmed-article:21324188pubmed:commentsCorrectionshttp://linkedlifedata.com/r...lld:pubmed
pubmed-article:21324188pubmed:commentsCorrectionshttp://linkedlifedata.com/r...lld:pubmed
pubmed-article:21324188pubmed:commentsCorrectionshttp://linkedlifedata.com/r...lld:pubmed
pubmed-article:21324188pubmed:commentsCorrectionshttp://linkedlifedata.com/r...lld:pubmed
pubmed-article:21324188pubmed:commentsCorrectionshttp://linkedlifedata.com/r...lld:pubmed
pubmed-article:21324188pubmed:commentsCorrectionshttp://linkedlifedata.com/r...lld:pubmed
pubmed-article:21324188pubmed:commentsCorrectionshttp://linkedlifedata.com/r...lld:pubmed
pubmed-article:21324188pubmed:commentsCorrectionshttp://linkedlifedata.com/r...lld:pubmed
pubmed-article:21324188pubmed:commentsCorrectionshttp://linkedlifedata.com/r...lld:pubmed
pubmed-article:21324188pubmed:commentsCorrectionshttp://linkedlifedata.com/r...lld:pubmed
pubmed-article:21324188pubmed:commentsCorrectionshttp://linkedlifedata.com/r...lld:pubmed
pubmed-article:21324188pubmed:commentsCorrectionshttp://linkedlifedata.com/r...lld:pubmed
pubmed-article:21324188pubmed:commentsCorrectionshttp://linkedlifedata.com/r...lld:pubmed
pubmed-article:21324188pubmed:commentsCorrectionshttp://linkedlifedata.com/r...lld:pubmed
pubmed-article:21324188pubmed:commentsCorrectionshttp://linkedlifedata.com/r...lld:pubmed
pubmed-article:21324188pubmed:commentsCorrectionshttp://linkedlifedata.com/r...lld:pubmed
pubmed-article:21324188pubmed:languageenglld:pubmed
pubmed-article:21324188pubmed:journalhttp://linkedlifedata.com/r...lld:pubmed
pubmed-article:21324188pubmed:citationSubsetIMlld:pubmed
pubmed-article:21324188pubmed:statusMEDLINElld:pubmed
pubmed-article:21324188pubmed:issn1472-6963lld:pubmed
pubmed-article:21324188pubmed:authorpubmed-author:AuDavid HDHlld:pubmed
pubmed-article:21324188pubmed:authorpubmed-author:JohnsonEricElld:pubmed
pubmed-article:21324188pubmed:authorpubmed-author:LeeTodd ATAlld:pubmed
pubmed-article:21324188pubmed:authorpubmed-author:UdrisEdmunds...lld:pubmed
pubmed-article:21324188pubmed:authorpubmed-author:AndersonSteph...lld:pubmed
pubmed-article:21324188pubmed:authorpubmed-author:CookeColin...lld:pubmed
pubmed-article:21324188pubmed:authorpubmed-author:JooMin JMJlld:pubmed
pubmed-article:21324188pubmed:issnTypeElectroniclld:pubmed
pubmed-article:21324188pubmed:volume11lld:pubmed
pubmed-article:21324188pubmed:ownerNLMlld:pubmed
pubmed-article:21324188pubmed:authorsCompleteYlld:pubmed
pubmed-article:21324188pubmed:pagination37lld:pubmed
pubmed-article:21324188pubmed:dateRevised2011-7-26lld:pubmed
pubmed-article:21324188pubmed:meshHeadingpubmed-meshheading:21324188...lld:pubmed
pubmed-article:21324188pubmed:meshHeadingpubmed-meshheading:21324188...lld:pubmed
pubmed-article:21324188pubmed:meshHeadingpubmed-meshheading:21324188...lld:pubmed
pubmed-article:21324188pubmed:meshHeadingpubmed-meshheading:21324188...lld:pubmed
pubmed-article:21324188pubmed:meshHeadingpubmed-meshheading:21324188...lld:pubmed
pubmed-article:21324188pubmed:meshHeadingpubmed-meshheading:21324188...lld:pubmed
pubmed-article:21324188pubmed:meshHeadingpubmed-meshheading:21324188...lld:pubmed
pubmed-article:21324188pubmed:meshHeadingpubmed-meshheading:21324188...lld:pubmed
pubmed-article:21324188pubmed:meshHeadingpubmed-meshheading:21324188...lld:pubmed
pubmed-article:21324188pubmed:meshHeadingpubmed-meshheading:21324188...lld:pubmed
pubmed-article:21324188pubmed:meshHeadingpubmed-meshheading:21324188...lld:pubmed
pubmed-article:21324188pubmed:meshHeadingpubmed-meshheading:21324188...lld:pubmed
pubmed-article:21324188pubmed:year2011lld:pubmed
pubmed-article:21324188pubmed:articleTitleThe validity of using ICD-9 codes and pharmacy records to identify patients with chronic obstructive pulmonary disease.lld:pubmed
pubmed-article:21324188pubmed:affiliationDivision of Pulmonary and Critical Care Medicine, University of Michigan, Ann Arbor, USA. cookecr@umich.edulld:pubmed
pubmed-article:21324188pubmed:publicationTypeJournal Articlelld:pubmed
pubmed-article:21324188pubmed:publicationTypeResearch Support, U.S. Gov't, Non-P.H.S.lld:pubmed
pubmed-article:21324188pubmed:publicationTypeResearch Support, Non-U.S. Gov'tlld:pubmed
pubmed-article:21324188pubmed:publicationTypeValidation Studieslld:pubmed