Statements in which the resource exists.
SubjectPredicateObjectContext
pubmed-article:1448241rdf:typepubmed:Citationlld:pubmed
pubmed-article:1448241lifeskim:mentionsumls-concept:C0333052lld:lifeskim
pubmed-article:1448241lifeskim:mentionsumls-concept:C0028582lld:lifeskim
pubmed-article:1448241lifeskim:mentionsumls-concept:C0678640lld:lifeskim
pubmed-article:1448241lifeskim:mentionsumls-concept:C0180853lld:lifeskim
pubmed-article:1448241lifeskim:mentionsumls-concept:C1549642lld:lifeskim
pubmed-article:1448241lifeskim:mentionsumls-concept:C1301627lld:lifeskim
pubmed-article:1448241lifeskim:mentionsumls-concept:C2348235lld:lifeskim
pubmed-article:1448241pubmed:issue9lld:pubmed
pubmed-article:1448241pubmed:dateCreated1992-12-24lld:pubmed
pubmed-article:1448241pubmed:abstractTextWorking Group 1 of the European project COST-B2 on quality assurance of nuclear medicine software has been concerned with the development of an appropriate mechanism for the transfer of nuclear medicine image data files between computer systems from different vendors. To this end a protocol based upon Report No. 10 of the American Association of Physicists in Medicine (AAPM) [1] was adopted. A previous publication [2] gave a specification (V3.2) for an intermediate file format with a list of key-value pairs for the header data associated with nuclear medicine image data files. This paper presents a revised specification for the intermediate file format and associated keys, now called V3.3, which has evolved from the experience in using the earlier version. It is hoped that the modifications proposed will improve the definition and usability of the file format as given in the earlier version.lld:pubmed
pubmed-article:1448241pubmed:languageenglld:pubmed
pubmed-article:1448241pubmed:journalhttp://linkedlifedata.com/r...lld:pubmed
pubmed-article:1448241pubmed:citationSubsetIMlld:pubmed
pubmed-article:1448241pubmed:statusMEDLINElld:pubmed
pubmed-article:1448241pubmed:monthSeplld:pubmed
pubmed-article:1448241pubmed:issn0143-3636lld:pubmed
pubmed-article:1448241pubmed:authorpubmed-author:Todd-Pokropek...lld:pubmed
pubmed-article:1448241pubmed:authorpubmed-author:CradduckT DTDlld:pubmed
pubmed-article:1448241pubmed:authorpubmed-author:DeconinckFFlld:pubmed
pubmed-article:1448241pubmed:issnTypePrintlld:pubmed
pubmed-article:1448241pubmed:volume13lld:pubmed
pubmed-article:1448241pubmed:ownerNLMlld:pubmed
pubmed-article:1448241pubmed:authorsCompleteYlld:pubmed
pubmed-article:1448241pubmed:pagination673-99lld:pubmed
pubmed-article:1448241pubmed:dateRevised2006-11-15lld:pubmed
pubmed-article:1448241pubmed:meshHeadingpubmed-meshheading:1448241-...lld:pubmed
pubmed-article:1448241pubmed:meshHeadingpubmed-meshheading:1448241-...lld:pubmed
pubmed-article:1448241pubmed:meshHeadingpubmed-meshheading:1448241-...lld:pubmed
pubmed-article:1448241pubmed:meshHeadingpubmed-meshheading:1448241-...lld:pubmed
pubmed-article:1448241pubmed:meshHeadingpubmed-meshheading:1448241-...lld:pubmed
pubmed-article:1448241pubmed:year1992lld:pubmed
pubmed-article:1448241pubmed:articleTitleA file format for the exchange of nuclear medicine image data: a specification of Interfile version 3.3.lld:pubmed
pubmed-article:1448241pubmed:affiliationUniversity College London, UK.lld:pubmed
pubmed-article:1448241pubmed:publicationTypeJournal Articlelld:pubmed
pubmed-article:1448241pubmed:publicationTypeResearch Support, Non-U.S. Gov'tlld:pubmed
http://linkedlifedata.com/r...pubmed:referesTopubmed-article:1448241lld:pubmed
http://linkedlifedata.com/r...pubmed:referesTopubmed-article:1448241lld:pubmed