PubMed Health⌕ Search
Home/Archive/PubMed

PubMed · 15645332

Validating DICOM content in a remote storage model.

Pattanasak Mongkolwat·Pankit Bhalodia·James A Gehl·David S Channin
View original source ↗Export metadata ↓

Abstract

Verifying the integrity of DICOM files transmitted between separate archives (eg, storage service providers, network attached storage, or storage area networks) is of critical importance. The software application described in this article retrieves a specified number of DICOM studies from two different DICOM storage applications; the primary picture archiving and communication system (PACS) and an off-site long-term archive. The system includes a query/retrieve (Q/R) module, storage service class provider (SCP), a DICOM comparison module, and a graphical user interface. The system checks the two studies for DICOM 3.0 compliance and then verifies that the DICOM data elements and pixel data are identical. Discrepancies in the two data sets are recorded with the data elements (tag number, value representation, value length, and value field) and pixel data (pixel value and pixel location) in question. The system can be operated automatically, in batch mode, and manually to meet a wide variety of use cases. We ran this program on a 15% statistical sample of 50,000 studies (7500 studies examined). We found 2 pixel data mismatches (resolved on retransmission) and 831 header element mismatches. We subsequently ran the program against a smaller batch of 1000 studies, identifying no pixel data mismatches and 958 header element mismatches. Although we did not find significant issues in our limited study, given other incidents that we have experienced when moving images between systems, we conclude that it is vital to maintain an ongoing, automatic, systematic validation of DICOM transfers so as to be proactive in preventing possibly catastrophic data loss.

Explore related subjects

Computer Communication NetworksDatabase Management SystemsHumansImage Processing, Computer-AssistedInformation Storage and RetrievalRadiology Information SystemsSoftware ValidationJournal Article

Keep this discovery

Explore connections, maps & timelines

BibTeXRIS

Pattanasak Mongkolwat, Pankit Bhalodia, James A Gehl, David S Channin. 2005. Validating DICOM content in a remote storage model.. https://doi.org/10.1007/s10278-004-1034-2

Cite the original work for its findings. Save a collection to share your selection of sources.

KEEP EXPLORING

Related citations

PubMed2005

Standardization of teleradiology using Dicom e-mail: recommendations of the German Radiology Society.

Until recently there has been no standard for an interoperable and manufacturer-independent protocol for secure teleradiology connections. This was one of the main reasons for the limited use of teleradiology in Germany. Various teleradiology solutions have been developed in the past, but the vast majority have not been interoperable. Therefore an ad hoc teleradiology connection was impossible even between partners who were already equipped with teleradiology workstations. Based on the evaluation of vendor-independent protocols in recent years the IT Working Group (AGIT) of the German Radiology Society set up an initiative to standardize basic teleradiology. An e-mail based solution using the Dicom standard for e-mail attachments with additional encryption according to the OpenPGP standard was found to be the common denominator. This protocol is easy to implement and safe for personalized patient data and fulfills the legal requirements for teleradiology in Germany and other countries. The first version of the recommendation was presented at the 85th German Radiology Convention in 2004. Eight commercial and three open-source implementations of the protocol are currently available; the protocol is in daily use in over 50 hospitals and institutions.

Computer Communication Networks↗
PubMed2005

HL7 Clinical Document Architecture, Release 2.

Clinical Document Architecture, Release One (CDA R1), became an American National Standards Institute (ANSI)-approved HL7 Standard in November 2000, representing the first specification derived from the Health Level 7 (HL7) Reference Information Model (RIM). CDA, Release Two (CDA R2), became an ANSI-approved HL7 Standard in May 2005 and is the subject of this article, where the focus is primarily on how the standard has evolved since CDA R1, particularly in the area of semantic representation of clinical events. CDA is a document markup standard that specifies the structure and semantics of a clinical document (such as a discharge summary or progress note) for the purpose of exchange. A CDA document is a defined and complete information object that can include text, images, sounds, and other multimedia content. It can be transferred within a message and can exist independently, outside the transferring message. CDA documents are encoded in Extensible Markup Language (XML), and they derive their machine processable meaning from the RIM, coupled with terminology. The CDA R2 model is richly expressive, enabling the formal representation of clinical statements (such as observations, medication administrations, and adverse events) such that they can be interpreted and acted upon by a computer. On the other hand, CDA R2 offers a low bar for adoption, providing a mechanism for simply wrapping a non-XML document with the CDA header or for creating a document with a structured header and sections containing only narrative content. The intent is to facilitate widespread adoption, while providing a mechanism for incremental semantic interoperability.

Computer Communication Networks↗
PubMed2005

Human-computer interaction reflected in the design of user interfaces for general practitioners.

PURPOSE: To address the problem of properly built health information systems in general practice as an important issue for their approval and use in clinical practice. We present how a national general practitioner (GP) network was built, put in practice and several results of its activity seen from the clinician's and the software application team's points of view. METHODS: We used a multi-level incremental development appropriate for the conditions of the required information system. After the development of the first version of the software components (based on rapid prototyping) of the sentinel network, a questionnaire addressed the needs and improvements required by the health professionals. Based on the answers, the functionality of the system and the interface were improved regarding the real needs expressed by the end-users. RESULTS: The network is functional and the collected data from the network are being processed using statistical methods. The academic software team developed a GP application that is well received by the GPs in the network, as resulted from the survey and discussions during the training period. As an added confirmation, several GPs outside the network enrolled after seeing the software at work. Another confirmation that we did a good job was that after the final presentation of the results of the project a representative from the Romanian Society for Cardiology expressed the wish of this society to access the data yielded by the network.

Computer Communication Networks↗