1dsrdump(1) OFFIS DCMTK dsrdump(1)
2
3
4
6 dsrdump - Dump DICOM SR file and data set
7
8
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
18 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
34 --version
35 print version information and exit
36
37 --arguments
38 print expanded command line arguments
39
40 -q --quiet
41 quiet mode, print no warnings and errors
42
43 -v --verbose
44 verbose mode, print processing details
45
46 -d --debug
47 debug mode, print debug information
48
49 -ll --log-level [l]evel: string constant
50 (fatal, error, warn, info, debug, trace)
51 use level l for the logger
52
53 -lc --log-config [f]ilename: string
54 use config file f for the logger
55
56 input options
57 input file format:
58
59 +f --read-file
60 read file format or data set (default)
61
62 +fo --read-file-only
63 read file format only
64
65 -f --read-dataset
66 read data set without file meta information
67
68 input transfer syntax:
69
70 -t= --read-xfer-auto
71 use TS recognition (default)
72
73 -td --read-xfer-detect
74 ignore TS specified in the file meta header
75
76 -te --read-xfer-little
77 read with explicit VR little endian TS
78
79 -tb --read-xfer-big
80 read with explicit VR big endian TS
81
82 -ti --read-xfer-implicit
83 read with implicit VR little endian TS
84
85 processing options
86 additional information:
87
88 -Ip --processing-details
89 show currently processed content item
90
91 error handling:
92
93 -Er --unknown-relationship
94 accept unknown/missing relationship type
95
96 -Ev --invalid-item-value
97 accept invalid content item value
98 (e.g. violation of VR or VM definition)
99
100 -Ec --ignore-constraints
101 ignore relationship content constraints
102
103 -Ee --ignore-item-errors
104 do not abort on content item errors, just warn
105 (e.g. missing value type specific attributes)
106
107 -Ei --skip-invalid-items
108 skip invalid content items (including sub-tree)
109
110 -Dv --disable-vr-checker
111 disable check for VR-conformant string values
112
113 specific character set:
114
115 +U8 --convert-to-utf8
116 convert all element values that are affected
117 by Specific Character Set (0008,0005) to UTF-8
118
119 # requires support from an underlying character encoding library
120 # (see output of --version on which one is available)
121
122 output options
123 general printing:
124
125 +Pf --print-filename
126 print header with filename for each document
127
128 -Ph --no-document-header
129 do not print general document information
130
131 +Pn --number-nested-items
132 print position string in front of each line
133
134 -Pn --indent-nested-items
135 indent nested items by spaces (default)
136
137 printing values:
138
139 +Pl --print-long-values
140 print long item values completely
141
142 -Pl --shorten-long-values
143 print long item values shortened (default)
144
145 +Pu --print-instance-uid
146 print SOP instance UID of referenced objects
147
148 -Ps --print-sopclass-short
149 print short SOP class name of referenced image objects,
150 e.g. "CT image" (default)
151
152 +Ps --print-sopclass-long
153 print long SOP class name of referenced objects
154
155 +Psu --print-sopclass-uid
156 print SOP class UID of referenced objects
157
158 +Pc --print-all-codes
159 print all codes (including concept name codes)
160
161 +Pi --print-invalid-codes
162 print invalid codes (for debugging purposes)
163
164 -Pi --no-invalid-codes
165 print text "invalid code" instead (default)
166
167 +Pt --print-template-id
168 print template identification information
169
170 enhanced encoding mode:
171
172 +Pe --indicate-enhanced
173 indicate that enhanced mode is used for codes
174
175 -Pe --no-enhanced-mode
176 do not indicate enhanced mode (default)
177
178 color:
179
180 +C --print-color
181 use ANSI escape codes for colored output
182
183 # not available on Windows systems
184
185 -C --no-color
186 do not use any ANSI escape codes (default)
187
188 # not available on Windows systems
189
191 DICOM Conformance
192 The dsrdump utility supports the following SOP Classes:
193
194 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 PlannedImagingAgentAdministrationSRStorage 1.2.840.10008.5.1.4.1.1.88.74
212 PerformedImagingAgentAdministrationSRStorage 1.2.840.10008.5.1.4.1.1.88.75
213
215 The level of logging output of the various command line tools and
216 underlying libraries can be specified by the user. By default, only
217 errors and warnings are written to the standard error stream. Using
218 option --verbose also informational messages like processing details
219 are reported. Option --debug can be used to get more details on the
220 internal activity, e.g. for debugging purposes. Other logging levels
221 can be selected using option --log-level. In --quiet mode only fatal
222 errors are reported. In such very severe error events, the application
223 will usually terminate. For more details on the different logging
224 levels, see documentation of module 'oflog'.
225
226 In case the logging output should be written to file (optionally with
227 logfile rotation), to syslog (Unix) or the event log (Windows) option
228 --log-config can be used. This configuration file also allows for
229 directing only certain messages to a particular output stream and for
230 filtering certain messages based on the module or application where
231 they are generated. An example configuration file is provided in
232 <etcdir>/logger.cfg.
233
235 All command line tools use the following notation for parameters:
236 square brackets enclose optional values (0-1), three trailing dots
237 indicate that multiple values are allowed (1-n), a combination of both
238 means 0 to n values.
239
240 Command line options are distinguished from parameters by a leading '+'
241 or '-' sign, respectively. Usually, order and position of command line
242 options are arbitrary (i.e. they can appear anywhere). However, if
243 options are mutually exclusive the rightmost appearance is used. This
244 behavior conforms to the standard evaluation rules of common Unix
245 shells.
246
247 In addition, one or more command files can be specified using an '@'
248 sign as a prefix to the filename (e.g. @command.txt). Such a command
249 argument is replaced by the content of the corresponding text file
250 (multiple whitespaces are treated as a single separator unless they
251 appear between two quotation marks) prior to any further evaluation.
252 Please note that a command file cannot contain another command file.
253 This simple but effective approach allows one to summarize common
254 combinations of options/parameters and avoids longish and confusing
255 command lines (an example is provided in file <datadir>/dumppat.txt).
256
258 The dsrdump utility will attempt to load DICOM data dictionaries
259 specified in the DCMDICTPATH environment variable. By default, i.e. if
260 the DCMDICTPATH environment variable is not set, the file
261 <datadir>/dicom.dic will be loaded unless the dictionary is built into
262 the application (default for Windows).
263
264 The default behavior should be preferred and the DCMDICTPATH
265 environment variable only used when alternative data dictionaries are
266 required. The DCMDICTPATH environment variable has the same format as
267 the Unix shell PATH variable in that a colon (':') separates entries.
268 On Windows systems, a semicolon (';') is used as a separator. The data
269 dictionary code will attempt to load each file specified in the
270 DCMDICTPATH environment variable. It is an error if no data dictionary
271 can be loaded.
272
274 dcmconv(1)
275
277 Copyright (C) 2000-2022 by OFFIS e.V., Escherweg 2, 26121 Oldenburg,
278 Germany.
279
280
281
282Version 3.6.7 Fri Apr 22 2022 dsrdump(1)