345 Full
345 Full
,, ,
x
; :
PACS Mini
5
Refresher Course
Introduction to the ACR-NEMA DICOM
StLfldard
w. Dean Bidgood, Jr, MD Steven
#{149} C. Horii MD
In 1982, the American College of Radiology (ACR) and the National Electri-
cal Manufacturers Association (NEMA) formed a committee to develop stan-
dards for the interconnection of digital imaging devices. Version 1 .0 of the
standard, published in 1985, specifies a hardware interface supporting
point-to-point (not network) image transmission, a data dictionary (a set of
rules for encoding information), and a set of commands to initiate transac-
tions. Version 2.0, published in 1988, also addresses point-to-point image
transmission and provides semantic rules by which messages (streams of bits
representing information in transit from one device to another) are orga-
: nized. Version 3.0, also referred to as DICOM (Digital Imaging and Commu-
. nications in Medicine), will be finalized in 1992. The DICOM standard en-
: courages open systems interconnection of imaging equipment over standard
networks, while maintaining compatibility with earlier point-to-point con-
nection standards. The DICOM standard conforms fully with the Interna-
tional Standards Organization reference model for network communications
(ISORM), addresses the issue of conformance, and incorporates the concept
of object-oriented design.
U INTRODUCTION
. Overview
In 1982, the American College of Radiology (ACR) and the National Electrical Manu-
facturers Association (NEMA) formed the ACR-NEMA committee to develop stan-
dards to promote a generic digital image communication format, facilitate the devel-
Abbreviations: ACR = American College of Radiology, ASCII = American Standard Code for Information Interchange,
DICOM = Digital Imaging and Communications in Medicine, ISO = International Standards Organization, ISORM = In.
temational Standards Organization reference model for network communications, NEMA = National Electrical Manufac.
turers Association, 051 = open systems interconnection, TCP.IP = transmission control protocol-internet protocol,
UID = unique identifier value
I From the Department of Radiology, University of Florida College of Medicine. BoxJ-374 JHMHC. 1600 SW Archer Rd.
Gainesville, FL 32610-0374 (W.D.B.); the Department of Radiology, Gainesville VA Medical Center. Gainesville. Fla
(W.D.B.); and the Department ofRadiology. Georgetown University hospital, Washington, DC (S.C.H.). From the 1991
RSNA scientific assembly. Received November 18, 1991; accepted November 19. Address reprint requests to W.I).B.
C 1992
See the article by Horii and Bidgood in the May 1992 issue.
345
a. b.
Figure 1. Plain film from a barium enema examination, digitized for image processing. (a) In the digitized
image, the pixel value range has been restricted to 2 bits (four levels of intensity) to simulate the effect of
limiting the bit depth of the display memory. (b) Another digitized image, for which the gray scale has been
extended to 6 bits (64 levels of intensity). The pixels in a are no larger than those in b, but the intelligibility
of the former image suffers significantly due to poor rendering of the gray scale of the subject. (Courtesy of
Ken’ichiro Kajiwara, MD, Kurume University Hospital, Kurume, Japan.)
Nearly every computer has a built-in rou- cal industry, and present the industry’s views
tine for handling a stream of data to display to the government and other entities. NEMA
an image on its own monitor. Most computers is organized into divisions and subdivisions
even provide interfaces (such as serial and according to product lines. One of the associ-
parallel ports) to send messages over a cable. ation’s key functions is to provide an organi-
The operating system software and an addi- zational framework for cooperative nonpro-
tional communications (terminal) program prietary development of voluntary industrial
push the bits of the image to the outside standards and codes. NEMA provides meeting
world. The real challenge of image communi- rooms, administrative staff, and publications
cations lies not in the sending of data, but in support to achieve this goal. It is through the
making sense of the “foreign” bits streaming MED-PACS subdivision of the diagnostic imag-
in from another computer. The receiving ing and therapy systems division that NEMA
computer must have a template so that it can has worked jointly with the ACR to develop
decode the incoming bursts of ones and zeros the ACR-NEMA Digital Imaging and Communi-
into intelligible units of information. Given cations Standard (Table 1).
the right set of clues, the computer is able to
reconstruct an exact copy of the original im- U COMPONENTS OF THE ACR-NEMA
age and store it in its memory (Fig 2). STANDARD
b.
Part 1: Introduction and Overview William C. Bennett Introduction, history, and future
directions; goals, rationale, and
technical description of the parts
of the standard
Part 2: Conformance William C. Bennett Requirements for functional, mes-
saging, encoding, and network
conformance; structure of a con-
fonmance claim
Pant 3: Information Objects James E. Steinke The set of information objects refer-
enced in service class specifica-
iions, attribute list, and semantics
of definitions
Part 4: Service Classes William C. Bennett Semantics ofa command as applied
to a data set in a given context,
definitions of associated set of
object attributes
Part 5: Data Interchange Formats Dwight Simon Details ofdata structure and seman-
tics, syntax, usage, compounding
of data sets, and basic and ad-
vanced functions
Part 6: Data Dictionary Steven C. Honii Attributes of information objects
classified by group and element
number, name, and parameters;
description of permitted values
Pant 7: Message Exchange Protocol James E. Steinke Examples ofcommand exchanges in
both point-to-point and ISO con-
texts, protocol for command en-
coding and status indication
Pant 8: Network Interface Specifica- Charles Parisot Definition of a generic upper-layer
iions service common to both OSI and
TCP-IP environments, supporting
standard networks
Part 9: Point-to-Point Interface Spec- Wayne DeJarnette Definition of 50-pin interface, physi-
ifications cal protocol, data link frame pro-
tocol, virtual channels, and ses-
sion layer services
Note.-OSI = open systems interconne ction, TCP-IP = transmissi on control protocol-internet protocol.
As it appears in a message, each individual ofversion 1.0 (Fig 3). In both versions, a type
data element consists of its group-element designation indicates the priority of each ele-
tag, its length, and its value. The length of ev- ment.
ery element and group is rounded to an even Group 0000H is the command group. Most
number to facilitate automatic error checking. of its elements are type 1 (required). The pni-
An odd length detected at the receiving end is ority designation of elements in the command
evidence of damage to the data set. When this group varies in a defined way, according to
occurs, the sending device is instructed to the type of command, since each command
repeat the transmission. performs a different function. ACR-NEMA yen-
From the user’s point of view, the element sion 2.0 commands are linked with three
values are the most essential part of the mes- classes of data sets: image, text, and graphics.
sage. Entries representing data values must be The standard defines the set of information
coded into proper syntax (ASCII text, ASCII elements that make up each class.
numerals, or binary). The version 2.0 data ForanMRimage(512 X 512 matrix, two
dictionary syntax rules are identical to those 8-bit bytes per pixel), the ratio of header in-
formation to image data is less than 1:1,000.
However, the proportion jumps to oyer 30%
when the same header is used for nuclear
Level 7 APPLICATION Contains both the user interface software and the
President input/output routines of the generic communications
software. Establishes associations with peer application Figure 6. Seven-layer refer-
processes. Preserves the relationships between ence model for computer
Information units.
communications developed
Level 6 PRESENTATION Translates information units from the syntax of the
Sales manager Application layer to the transfer syntax negotiated with a by the ISO. Each layer re-
peer Presentation layer across the network. The size of ceives services from the layer
transferred information units is not constrained by the
Internal details of network function. immediately below it and pro-
vides services to the layer
DATA HANDLING LAYERS above it. The “job descnip-
tions’ ‘ in the middle column
Level 5 SESSION Establishes and controls connections. Segments the
are provided for clari&ation
Department head information units (of arbitrary size) provided by the
Presentation layer Into manageable dialogue units of data, only; they are not official ISO
the size of which is constrained only by the capabilities labels. Note the separation of
of the Transport service.
Provides reliable end-to-end transfer of Session dialogue the information-handling up-
Level 4 TRANSPORT
Supervisor units regardless of the type of Network employed. per layers and the data-han-
Ensures that speed, accuracy. and reliability meet levels dling lower layers. Although
specified by the Session layer.
Level 3 NEThOl< Routes and relays data units. Assigns virtual channels. functional flow here is de
Dispatcher Encapsulates data into packets and adds addresses and scribed only from the top
sequence numbers to each. Negotiates handoffs between
intermediate relay points to support the Transport layer.
down, the reciprocal occurs
Level 2 DATA LINK Frames each packet between a control word and a frame when data are received by the
Traffx cop check word. Facilitates error correction. Sends frames physical layer for delivery to
to the hardware of the Physical layer only upon receipt of the top. Each layer also open-
the proper status Indication.
Level 1 PHYSICAL Transmits frames created by the Data Unk layer by ates in tandem with its peer
Truck driver generating electrical or optical impulses, or other across the network (ie, appli-
signals, according to the timing. duration, and amplitude
protocols demanded by the type of network employed.
cation with application, pre-
sentation with presentation).
medicine dynamic images with a matrix size of of a vendor’s conformance clijpn. Conform-
32 x 32. This is an unacceptable amount of ance claims must be express#{235}tl in terms of
overhead, since version 2.0 requires a full specifically defined service classes, the func-
header to be sent with each image. tional units ofwhich are precisely described
with predefined terms. Vendors are free to
I Version 30: DICOM Standard implement any function in their software;
The incorporation of an object-oriented data however, if they claim to conform to the
model and the addition of support for ISO DICOM standard, they must state precisely
standard communications substantially which services are and which services are not
broaden the scope ofversion 3.0 ofthe ACR- supported by their product,
NEMA standard, DICOM. The draft document
of the standard is composed of nine parts. ISO Reference Model.-The DICOM stan-
Parts 1, 8, and 9 of the DICOM standard have dard conforms fully tothe ISO reference
been prepared for balloting in March 1992. model for netwoij communications (ISORM)
Parts 2-7 will be circulated for comment later (4, pp 13-129). Protocols based on the
in 1992. The modular design ofversion 3.0 ISORM control the process of information ex-
will facilitate future enhancements of the stan- change among dissimilar computer systems.
dard (Table 3) (3). The ISORM specifies a sequence of protocol
negotiations that mediate the differing abili-
Conformance Levels.-Missing from the ties and requirements of devices and software
early versions of the ACR-NEMA standard is a applications linked remotely by a network
rigorous treatment of the issue of conform- (Fig 6).
ance. Thus, the various interpretations of the ISO publications specify the requirements
earlier versions have been ambiguous. Trou- for conformance to the ISORM. These docu-
blesome incompatibilities have been noted by ments deal with the seemingly mundane but
users, particularly in the areas of unique iden- essential details of the structure of messages,
tification numbers, orientation coordinates of the negotiation of services among remote us-
cross-sectional images, and examination ens, and the resolution of errors and conflicts.
(study, acquisition, series, image) hierarchy.
The DICOM standard specifies levels of con-
formance and explicitly defines the structure
Folders and File Linking.-The Papyrus file standard were based. Tools of object-oriented
format developed at the University Hospital of analysis have been used to refine the standard
Geneva is a method for grouping associated data dictionary developed for versions 1.0
data sets into folders by value (containing ac- and 2.0 and to identify the characteristics of
tual images or other data) and folders by ref- key entities in the domain of medical imaging.
erence (containing only the memory ad- The purposes of an information model are
dresses of the actual data sets) (7). The folder to identify, classify, and abstract essential rela-
concept of Papyrus is blended with the ACR- tionships and to organize information into a
NEMA message structure by way of a user- formal structure. Similar ‘things, or instances,
‘
defined group 0041H, which contains the ad- are identified and abstracted as objects; char-
dresses of the related data sets. Future acteristics of these instances are abstracted as
versions of the DICOM standard will support attributes; and reliable associations between
ISO protocols for hierarchical directory struc- the instances are abstracted as relationships”
ture, remote use of storage resources, and (9).
selection of multiple files by logical “filters” Information modeling reduces redundancy
(4, pp 205-221; 8). and ambiguity by requiring that information
Version 3.0 of the DICOM standard will in- objects be defined only in terms of their most
corporate a mechanism for linking related fundamental and unchanging qualities or val-
images to a single identification header dur- ues-that is, their lowest common denomina-
ing transport. Working group 6 of the ACR- tors. Related but not identical types of entities
NEMA committee is considering proposals for are grouped into information object classes.
methods to eliminate repetition of identical Within an information object class, each mdi-
data elements. The reduction of redundancy vidual member is known as an instance of the
will be significant, particularly in nuclear class type. Properties of inheritance and hier-
medicine. archy determine the attributes of objects,
their superclasses, and subclasses.
U INFORMATION MODELING There is no overlap on duplication of at-
tributes among the superclass of normalized
. Object-oriented Analysis information object classes (Fig 9). However,
In the process of developing the DICOM stan- another superclass of composite information
dard, the ACR and NEMA have jointly taken objects is permitted to share some attributes
the difficult first steps toward the complete that may have identical group-element tags.
reorganization of the information model on
which versions 1.0 and 2.0 ofthe ACR-NEMA