1dsrdump(1) OFFIS DCMTK dsrdump(1)
2
6 dsrdump - Dump DICOM SR file and data set
7
9 dsrdump [options] dsrfile-in...
10
12 The dsrdump utility dumps the contents of a DICOM Structured Reporting
13 (SR) document (file format or raw data set) to stdout in textual form.
14 The output of the document content follows the format proposed in David
15 Clunie's book 'DICOM Structured Reporting' (PixelMed Publishing, 2000).
16 If dsrdump reads a raw data set (DICOM data without a file format meta-
18 header) it will attempt to guess the transfer syntax by examining the
19 first few bytes of the file. It is not always possible to correctly
20 guess the transfer syntax and it is better to convert a data set to a
21 file format whenever possible (using the dcmconv utility). It is also
22 possible to use the -f and -t[ieb] options to force dsrdump to read a
23 dataset with a particular transfer syntax.
24
26 dsrfile-in DICOM SR input filename to be dumped
27
29 general options
30 -h --help
31 print this help text and exit
32 --version
34 print version information and exit
35 --arguments
37 print expanded command line arguments
38 -q --quiet
40 quiet mode, print no warnings and errors
41 -v --verbose
43 verbose mode, print processing details
44 -d --debug
46 debug mode, print debug information
47 -ll --log-level [l]evel: string constant
49 (fatal, error, warn, info, debug, trace)
50 use level l for the logger
51 -lc --log-config [f]ilename: string
53 use config file f for the logger
54 input options
56 input file format:
57 +f --read-file
59 read file format or data set (default)
60 +fo --read-file-only
62 read file format only
63 -f --read-dataset
65 read data set without file meta information
66 input transfer syntax:
68 -t= --read-xfer-auto
70 use TS recognition (default)
71 -td --read-xfer-detect
73 ignore TS specified in the file meta header
74 -te --read-xfer-little
76 read with explicit VR little endian TS
77 -tb --read-xfer-big
79 read with explicit VR big endian TS
80 -ti --read-xfer-implicit
82 read with implicit VR little endian TS
83 parsing options
85 additional information:
86 -Ip --processing-details
88 show currently processed content item
89 error handling:
91 -Er --unknown-relationship
93 accept unknown/missing relationship type
94 -Ec --ignore-constraints
96 ignore relationship content constraints
97 -Ee --ignore-item-errors
99 do not abort on content item errors, just warn
100 (e.g. missing value type specific attributes)
101 -Ei --skip-invalid-items
103 skip invalid content items (incl. sub-tree)
104 output options
106 printing:
107 +Pf --print-filename
109 print header with filename for each document
110 -Ph --no-document-header
112 do not print general document information
113 +Pn --number-nested-items
115 print position string in front of each line
116 -Pn --indent-nested-items
118 indent nested items by spaces (default)
119 +Pl --print-long-values
121 print long item values completely
122 -Pl --shorten-long-values
124 print long item values shortened (default)
125 +Pu --print-instance-uid
127 print SOP instance UID of referenced objects
128 +Pc --print-all-codes
130 print all codes (incl. concept name codes)
131 +Pt --print-template-id
133 print template identification information
134
136 DICOM Conformance
137 The dsrdump utility supports the following SOP Classes:
138 SpectaclePrescriptionReportStorage 1.2.840.10008.5.1.4.1.1.78.6
140 MacularGridThicknessAndVolumeReportStorage 1.2.840.10008.5.1.4.1.1.79.1
141 BasicTextSRStorage 1.2.840.10008.5.1.4.1.1.88.11
142 EnhancedSRStorage 1.2.840.10008.5.1.4.1.1.88.22
143 ComprehensiveSRStorage 1.2.840.10008.5.1.4.1.1.88.33
144 ProcedureLogStorage 1.2.840.10008.5.1.4.1.1.88.40
145 MammographyCADSRStorage 1.2.840.10008.5.1.4.1.1.88.50
146 KeyObjectSelectionDocumentStorage 1.2.840.10008.5.1.4.1.1.88.59
147 ChestCADSRStorage 1.2.840.10008.5.1.4.1.1.88.65
148 XRayRadiationDoseSRStorage 1.2.840.10008.5.1.4.1.1.88.67
149 ColonCADSRStorage 1.2.840.10008.5.1.4.1.1.88.69
150 ImplantationPlanSRDocumentStorage 1.2.840.10008.5.1.4.1.1.88.70
151
153 The level of logging output of the various command line tools and
154 underlying libraries can be specified by the user. By default, only
155 errors and warnings are written to the standard error stream. Using
156 option --verbose also informational messages like processing details
157 are reported. Option --debug can be used to get more details on the
158 internal activity, e.g. for debugging purposes. Other logging levels
159 can be selected using option --log-level. In --quiet mode only fatal
160 errors are reported. In such very severe error events, the application
161 will usually terminate. For more details on the different logging
162 levels, see documentation of module 'oflog'.
163 In case the logging output should be written to file (optionally with
165 logfile rotation), to syslog (Unix) or the event log (Windows) option
166 --log-config can be used. This configuration file also allows for
167 directing only certain messages to a particular output stream and for
168 filtering certain messages based on the module or application where
169 they are generated. An example configuration file is provided in
170 <etcdir>/logger.cfg).
171
173 All command line tools use the following notation for parameters:
174 square brackets enclose optional values (0-1), three trailing dots
175 indicate that multiple values are allowed (1-n), a combination of both
176 means 0 to n values.
177 Command line options are distinguished from parameters by a leading '+'
179 or '-' sign, respectively. Usually, order and position of command line
180 options are arbitrary (i.e. they can appear anywhere). However, if
181 options are mutually exclusive the rightmost appearance is used. This
182 behaviour conforms to the standard evaluation rules of common Unix
183 shells.
184 In addition, one or more command files can be specified using an '@'
186 sign as a prefix to the filename (e.g. @command.txt). Such a command
187 argument is replaced by the content of the corresponding text file
188 (multiple whitespaces are treated as a single separator unless they
189 appear between two quotation marks) prior to any further evaluation.
190 Please note that a command file cannot contain another command file.
191 This simple but effective approach allows to summarize common
192 combinations of options/parameters and avoids longish and confusing
193 command lines (an example is provided in file <datadir>/dumppat.txt).
194
196 The dsrdump utility will attempt to load DICOM data dictionaries
197 specified in the DCMDICTPATH environment variable. By default, i.e. if
198 the DCMDICTPATH environment variable is not set, the file
199 <datadir>/dicom.dic will be loaded unless the dictionary is built into
200 the application (default for Windows).
201 The default behaviour should be preferred and the DCMDICTPATH
203 environment variable only used when alternative data dictionaries are
204 required. The DCMDICTPATH environment variable has the same format as
205 the Unix shell PATH variable in that a colon (':') separates entries.
206 On Windows systems, a semicolon (';') is used as a separator. The data
207 dictionary code will attempt to load each file specified in the
208 DCMDICTPATH environment variable. It is an error if no data dictionary
209 can be loaded.
210
212 dcmconv(1)
213
215 Copyright (C) 2000-2010 by OFFIS e.V., Escherweg 2, 26121 Oldenburg,
216 Germany.
217Version 3.6.0 6 Jan 2011 dsrdump(1)