Statements in which the resource exists.
SubjectPredicateObjectContext
pubmed-article:19119392rdf:typepubmed:Citationlld:pubmed
pubmed-article:19119392lifeskim:mentionsumls-concept:C0037928lld:lifeskim
pubmed-article:19119392lifeskim:mentionsumls-concept:C0039144lld:lifeskim
pubmed-article:19119392lifeskim:mentionsumls-concept:C0817096lld:lifeskim
pubmed-article:19119392lifeskim:mentionsumls-concept:C1314792lld:lifeskim
pubmed-article:19119392lifeskim:mentionsumls-concept:C0085973lld:lifeskim
pubmed-article:19119392lifeskim:mentionsumls-concept:C0007320lld:lifeskim
pubmed-article:19119392pubmed:issue2lld:pubmed
pubmed-article:19119392pubmed:dateCreated2009-1-2lld:pubmed
pubmed-article:19119392pubmed:abstractTextMyelopathy is a form of neurological disease caused by compression of the spinal cord. Upper and lower quarter screens are commonly used in identifying myelopathy, although most of the screen components demonstrate poor or unstudied diagnostic value. The purpose of this case report is to describe the diagnostic process in detecting syringomyelia, an intramedullary lesion that may cause myelopathy. The patient was a 47-year-old female with a thoracic syrinx that was discovered by spinal magnetic resonance imaging (MRI) following a complicated and delayed clinical diagnostic course. Following surgical intervention and a two-week inpatient rehabilitation stay, the patient was discharged using a rolling walker for ambulation and was performing most transfers with modified independence. A complicating pattern of signs and symptoms combined with a diagnostic process guided by poorly studied screen components demonstrates the diagnostic dilemma associated with identifying the cause of myelopathy within the thoracic spine. This also indicates the need for further investigation of individual and clustered components of the neurological screen to improve the ability to identify patients in need of complete imaging studies in a more timely fashion.lld:pubmed
pubmed-article:19119392pubmed:commentsCorrectionshttp://linkedlifedata.com/r...lld:pubmed
pubmed-article:19119392pubmed:commentsCorrectionshttp://linkedlifedata.com/r...lld:pubmed
pubmed-article:19119392pubmed:commentsCorrectionshttp://linkedlifedata.com/r...lld:pubmed
pubmed-article:19119392pubmed:commentsCorrectionshttp://linkedlifedata.com/r...lld:pubmed
pubmed-article:19119392pubmed:commentsCorrectionshttp://linkedlifedata.com/r...lld:pubmed
pubmed-article:19119392pubmed:commentsCorrectionshttp://linkedlifedata.com/r...lld:pubmed
pubmed-article:19119392pubmed:commentsCorrectionshttp://linkedlifedata.com/r...lld:pubmed
pubmed-article:19119392pubmed:commentsCorrectionshttp://linkedlifedata.com/r...lld:pubmed
pubmed-article:19119392pubmed:commentsCorrectionshttp://linkedlifedata.com/r...lld:pubmed
pubmed-article:19119392pubmed:commentsCorrectionshttp://linkedlifedata.com/r...lld:pubmed
pubmed-article:19119392pubmed:commentsCorrectionshttp://linkedlifedata.com/r...lld:pubmed
pubmed-article:19119392pubmed:commentsCorrectionshttp://linkedlifedata.com/r...lld:pubmed
pubmed-article:19119392pubmed:commentsCorrectionshttp://linkedlifedata.com/r...lld:pubmed
pubmed-article:19119392pubmed:commentsCorrectionshttp://linkedlifedata.com/r...lld:pubmed
pubmed-article:19119392pubmed:commentsCorrectionshttp://linkedlifedata.com/r...lld:pubmed
pubmed-article:19119392pubmed:commentsCorrectionshttp://linkedlifedata.com/r...lld:pubmed
pubmed-article:19119392pubmed:commentsCorrectionshttp://linkedlifedata.com/r...lld:pubmed
pubmed-article:19119392pubmed:commentsCorrectionshttp://linkedlifedata.com/r...lld:pubmed
pubmed-article:19119392pubmed:commentsCorrectionshttp://linkedlifedata.com/r...lld:pubmed
pubmed-article:19119392pubmed:commentsCorrectionshttp://linkedlifedata.com/r...lld:pubmed
pubmed-article:19119392pubmed:commentsCorrectionshttp://linkedlifedata.com/r...lld:pubmed
pubmed-article:19119392pubmed:commentsCorrectionshttp://linkedlifedata.com/r...lld:pubmed
pubmed-article:19119392pubmed:commentsCorrectionshttp://linkedlifedata.com/r...lld:pubmed
pubmed-article:19119392pubmed:commentsCorrectionshttp://linkedlifedata.com/r...lld:pubmed
pubmed-article:19119392pubmed:commentsCorrectionshttp://linkedlifedata.com/r...lld:pubmed
pubmed-article:19119392pubmed:languageenglld:pubmed
pubmed-article:19119392pubmed:journalhttp://linkedlifedata.com/r...lld:pubmed
pubmed-article:19119392pubmed:statusPubMed-not-MEDLINElld:pubmed
pubmed-article:19119392pubmed:issn1066-9817lld:pubmed
pubmed-article:19119392pubmed:authorpubmed-author:KouD MDMlld:pubmed
pubmed-article:19119392pubmed:authorpubmed-author:GoodeAdamAlld:pubmed
pubmed-article:19119392pubmed:authorpubmed-author:Rene...lld:pubmed
pubmed-article:19119392pubmed:issnTypePrintlld:pubmed
pubmed-article:19119392pubmed:volume16lld:pubmed
pubmed-article:19119392pubmed:ownerNLMlld:pubmed
pubmed-article:19119392pubmed:authorsCompleteYlld:pubmed
pubmed-article:19119392pubmed:pagination82-8lld:pubmed
pubmed-article:19119392pubmed:year2008lld:pubmed
pubmed-article:19119392pubmed:articleTitleIdentifying myelopathy caused by thoracic syringomyelia: a case report.lld:pubmed
pubmed-article:19119392pubmed:affiliationStaff Physical Therapist, University of North Carolina Hospital, Chapel Hill, NC.lld:pubmed
pubmed-article:19119392pubmed:publicationTypeJournal Articlelld:pubmed