2002
DOI: 10.1007/s10278-002-5010-4
|View full text |Cite
|
Sign up to set email alerts
|

Challenges in Image Acquisition and Distribution for Clinical Image Service

Abstract: We have developed a centralized application for acquiring images from multiple picture archiving and communication systems (PACS) and distributing images to a clinical image web server and other repositories. Our flexible strategy addresses a number of administrative challenges associated with delivering images into clinical, research, and test environments. DICOM images flow from PACSs and modalities to a UNIX-based "distributor" application, which relays them to one or more destinations. Image volume and tra… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1

Citation Types

0
3
0

Year Published

2003
2003
2007
2007

Publication Types

Select...
2
1

Relationship

1
2

Authors

Journals

citations
Cited by 3 publications
(3 citation statements)
references
References 0 publications
0
3
0
Order By: Relevance
“…Issues related to modification, analysis and communication of DICOM objects, community wide sharing of images have been addressed [27][28][29][30][31][32][33][34][35]. There are DICOM standards based toolkits such as PixelMed available for developers to handle PACS systems programmatically [36] .…”
Section: Background and Related Workmentioning
confidence: 99%
“…Issues related to modification, analysis and communication of DICOM objects, community wide sharing of images have been addressed [27][28][29][30][31][32][33][34][35]. There are DICOM standards based toolkits such as PixelMed available for developers to handle PACS systems programmatically [36] .…”
Section: Background and Related Workmentioning
confidence: 99%
“…Assuming an average mix of images [13], an effective UC of 4.0 GB/h or 96 GB per day appears to be a careful and realistic approximation. The average daily image production in PACS installations strongly varies: 3.4 GB/day [1]; 6.2 GB/day [14]; 8 GB/day [15]; 9 GB/day [16]; 19 GB/day [11]; 20-30 GB/day [17]; and even 34 GB/day [18] in a quite large installation (values provided in Terabyte per year were divided by 365 for the ease of comparison, although this is not fully correct). Even when those amounts do not include the prior examinations, which are estimated to be one-third of the daily production [16], and the fact that the data production is likely to rise with the installation of multislice CT [19], it is concluded that a UC of 96 GB/day is sufficient.…”
Section: Upload Performancementioning
confidence: 99%
“…Our Philips PACS cannot be configured to route inbound studies to multiple destinations; studies destined for the Philips PACS are sent from their modalities to the IRN pool, which can simultaneously route to the Philips PACS and to the Imageweb server. 3 …”
Section: Image Flowmentioning
confidence: 99%