1dsrdump(1) OFFIS DCMTK dsrdump(1)
2
6 dsrdump - Dump DICOM SR file and data set
7
10 dsrdump [options] dsrfile-in...
11
13 The dsrdump utility dumps the contents of a DICOM Structured Reporting
14 (SR) document (file format or raw data set) to stdout in textual form.
15 The output of the document content follows the format proposed in David
16 Clunie's book 'DICOM Structured Reporting' (PixelMed Publishing, 2000).
17 If dsrdump reads a raw data set (DICOM data without a file format meta-
19 header) it will attempt to guess the transfer syntax by examining the
20 first few bytes of the file. It is not always possible to correctly
21 guess the transfer syntax and it is better to convert a data set to a
22 file format whenever possible (using the dcmconv utility). It is also
23 possible to use the -f and -t[ieb] options to force dsrdump to read a
24 dataset with a particular transfer syntax.
25
27 dsrfile-in DICOM SR input filename to be dumped
28
30 general options
31 -h --help
32 print this help text and exit
33 --version
35 print version information and exit
36 --arguments
38 print expanded command line arguments
39 -q --quiet
41 quiet mode, print no warnings and errors
42 -v --verbose
44 verbose mode, print processing details
45 -d --debug
47 debug mode, print debug information
48 -ll --log-level [l]evel: string constant
50 (fatal, error, warn, info, debug, trace)
51 use level l for the logger
52 -lc --log-config [f]ilename: string
54 use config file f for the logger
55 input options
57 input file format:
58 +f --read-file
60 read file format or data set (default)
61 +fo --read-file-only
63 read file format only
64 -f --read-dataset
66 read data set without file meta information
67 input transfer syntax:
69 -t= --read-xfer-auto
71 use TS recognition (default)
72 -td --read-xfer-detect
74 ignore TS specified in the file meta header
75 -te --read-xfer-little
77 read with explicit VR little endian TS
78 -tb --read-xfer-big
80 read with explicit VR big endian TS
81 -ti --read-xfer-implicit
83 read with implicit VR little endian TS
84 processing options
86 additional information:
87 -Ip --processing-details
89 show currently processed content item
90 error handling:
92 -Er --unknown-relationship
94 accept unknown/missing relationship type
95 -Ev --invalid-item-value
97 accept invalid content item value
98 (e.g. violation of VR or VM definition)
99 -Ec --ignore-constraints
101 ignore relationship content constraints
102 -Ee --ignore-item-errors
104 do not abort on content item errors, just warn
105 (e.g. missing value type specific attributes)
106 -Ei --skip-invalid-items
108 skip invalid content items (including sub-tree)
109 -Dv --disable-vr-checker
111 disable check for VR-conformant string values
112 specific character set:
114 +U8 --convert-to-utf8
116 convert all element values that are affected
117 by Specific Character Set (0008,0005) to UTF-8
118 # requires support from an underlying character encoding library
120 # (see output of --version on which one is available)
121 output options
123 general printing:
124 +Pf --print-filename
126 print header with filename for each document
127 -Ph --no-document-header
129 do not print general document information
130 +Pn --number-nested-items
132 print position string in front of each line
133 -Pn --indent-nested-items
135 indent nested items by spaces (default)
136 printing values:
138 +Pl --print-long-values
140 print long item values completely
141 -Pl --shorten-long-values
143 print long item values shortened (default)
144 +Pu --print-instance-uid
146 print SOP instance UID of referenced objects
147 -Ps --print-sopclass-short
149 print short SOP class name of referenced image objects,
150 e.g. "CT image" (default)
151 +Ps --print-sopclass-long
153 print long SOP class name of referenced objects
154 +Psu --print-sopclass-uid
156 print SOP class UID of referenced objects
157 +Pc --print-all-codes
159 print all codes (including concept name codes)
160 +Pi --print-invalid-codes
162 print invalid codes (for debugging purposes)
163 -Pi --no-invalid-codes
165 print text "invalid code" instead (default)
166 +Pt --print-template-id
168 print template identification information
169 enhanced encoding mode:
171 +Pe --indicate-enhanced
173 indicate that enhanced mode is used for codes
174 -Pe --no-enhanced-mode
176 do not indicate enhanced mode (default)
177 color:
179 +C --print-color
181 use ANSI escape codes for colored output
182 # not available on Windows systems
184 -C --no-color
186 do not use any ANSI escape codes (default)
187 # not available on Windows systems
189
191 DICOM Conformance
192 The dsrdump utility supports the following SOP Classes:
193 SpectaclePrescriptionReportStorage 1.2.840.10008.5.1.4.1.1.78.6
195 MacularGridThicknessAndVolumeReportStorage 1.2.840.10008.5.1.4.1.1.79.1
196 BasicTextSRStorage 1.2.840.10008.5.1.4.1.1.88.11
197 EnhancedSRStorage 1.2.840.10008.5.1.4.1.1.88.22
198 ComprehensiveSRStorage 1.2.840.10008.5.1.4.1.1.88.33
199 Comprehensive3DSRStorage 1.2.840.10008.5.1.4.1.1.88.34
200 ProcedureLogStorage 1.2.840.10008.5.1.4.1.1.88.40
201 MammographyCADSRStorage 1.2.840.10008.5.1.4.1.1.88.50
202 KeyObjectSelectionDocumentStorage 1.2.840.10008.5.1.4.1.1.88.59
203 ChestCADSRStorage 1.2.840.10008.5.1.4.1.1.88.65
204 XRayRadiationDoseSRStorage 1.2.840.10008.5.1.4.1.1.88.67
205 RadiopharmaceuticalRadiationDoseSRStorage 1.2.840.10008.5.1.4.1.1.88.68
206 ColonCADSRStorage 1.2.840.10008.5.1.4.1.1.88.69
207 ImplantationPlanSRDocumentStorage 1.2.840.10008.5.1.4.1.1.88.70
208 AcquisitionContextSRStorage 1.2.840.10008.5.1.4.1.1.88.71
209 SimplifiedAdultEchoSRStorage 1.2.840.10008.5.1.4.1.1.88.72
210 PatientRadiationDoseSRStorage 1.2.840.10008.5.1.4.1.1.88.73
211
213 The level of logging output of the various command line tools and
214 underlying libraries can be specified by the user. By default, only
215 errors and warnings are written to the standard error stream. Using
216 option --verbose also informational messages like processing details
217 are reported. Option --debug can be used to get more details on the
218 internal activity, e.g. for debugging purposes. Other logging levels
219 can be selected using option --log-level. In --quiet mode only fatal
220 errors are reported. In such very severe error events, the application
221 will usually terminate. For more details on the different logging
222 levels, see documentation of module 'oflog'.
223 In case the logging output should be written to file (optionally with
225 logfile rotation), to syslog (Unix) or the event log (Windows) option
226 --log-config can be used. This configuration file also allows for
227 directing only certain messages to a particular output stream and for
228 filtering certain messages based on the module or application where
229 they are generated. An example configuration file is provided in
230 <etcdir>/logger.cfg.
231
233 All command line tools use the following notation for parameters:
234 square brackets enclose optional values (0-1), three trailing dots
235 indicate that multiple values are allowed (1-n), a combination of both
236 means 0 to n values.
237 Command line options are distinguished from parameters by a leading '+'
239 or '-' sign, respectively. Usually, order and position of command line
240 options are arbitrary (i.e. they can appear anywhere). However, if
241 options are mutually exclusive the rightmost appearance is used. This
242 behavior conforms to the standard evaluation rules of common Unix
243 shells.
244 In addition, one or more command files can be specified using an '@'
246 sign as a prefix to the filename (e.g. @command.txt). Such a command
247 argument is replaced by the content of the corresponding text file
248 (multiple whitespaces are treated as a single separator unless they
249 appear between two quotation marks) prior to any further evaluation.
250 Please note that a command file cannot contain another command file.
251 This simple but effective approach allows one to summarize common
252 combinations of options/parameters and avoids longish and confusing
253 command lines (an example is provided in file <datadir>/dumppat.txt).
254
256 The dsrdump utility will attempt to load DICOM data dictionaries
257 specified in the DCMDICTPATH environment variable. By default, i.e. if
258 the DCMDICTPATH environment variable is not set, the file
259 <datadir>/dicom.dic will be loaded unless the dictionary is built into
260 the application (default for Windows).
261 The default behavior should be preferred and the DCMDICTPATH
263 environment variable only used when alternative data dictionaries are
264 required. The DCMDICTPATH environment variable has the same format as
265 the Unix shell PATH variable in that a colon (':') separates entries.
266 On Windows systems, a semicolon (';') is used as a separator. The data
267 dictionary code will attempt to load each file specified in the
268 DCMDICTPATH environment variable. It is an error if no data dictionary
269 can be loaded.
270
272 dcmconv(1)
273
275 Copyright (C) 2000-2018 by OFFIS e.V., Escherweg 2, 26121 Oldenburg,
276 Germany.
277Version 3.6.4 Thu Nov 29 2018 dsrdump(1)