xml2dsr(1)

πŸ’œ xml2dsr(1) β€” OFFIS DCMTK πŸ’œ

okay so bestie, welcome to the manual page for xml2dsr, part of OFFIS DCMTK, section 1 of the man pages. it's giving "converter core" and honestly she ate. let's get into it 🫢


✨ NAME ✨

xml2dsr β€” Convert XML document to DICOM SR file πŸ¦‹


✨ SYNOPSIS ✨

xml2dsr [options] xmlfile-in dsrfile-out

✨ DESCRIPTION ✨

okay so xml2dsr takes the contents of an XML (Extensible Markup Language) document and converts it to DICOM Structured Reporting (SR) format β€” either file format or raw data set. literally doing the most and we love her for it πŸ’…

the XML Schema dsr2xml.xsd does not yet follow any standard format. ngl that's just how it is right now. but! the xml2dsr application might be enhanced in this aspect in the future (e. g. by supporting HL7/CDA - Clinical Document Architecture). so like, watch this space ✨

an appropriate XML file can be created using the dsr2xml tool β€” and option +Xn is recommended to add XML namespace declaration to the root element. iykyk πŸŽ€


✨ PARAMETERS ✨

  • xmlfile-in β€” XML input filename to be converted (- for stdin) πŸ“
  • dsrfile-out β€” DICOM SR output filename (- for stdout) πŸ“

✨ OPTIONS ✨

πŸŽ€ general options

  • -h, --help β€” print this help text and exit
  • --version β€” print version information and exit
  • --arguments β€” print expanded command line arguments
  • -q, --quiet β€” quiet mode, print no warnings and errors
  • -v, --verbose β€” verbose mode, print processing details
  • -d, --debug β€” debug mode, print debug information
  • -ll, --log-level [l]evel: string constant β€” (fatal, error, warn, info, debug, trace) use level l for the logger
  • -lc, --log-config [f]ilename: string β€” use config file f for the logger

πŸ¦‹ input options

encoding:

  • +Ee, --template-envelope β€” template element encloses content items

🌸 processing options

validation:

  • +Vs, --validate-schema β€” validate XML document against Schema (not with --template-envelope)
    • this one requires libxml to be compiled with XML Schema support, no cap 😭
  • +Vn, --check-namespace β€” check XML namespace in document root

unique identifiers:

  • +Ug, --generate-new-uids β€” generate new Study/Series/SOP Instance UID
  • -Uo, --dont-overwrite-uids β€” do not overwrite existing UIDs (default)
  • +Uo, --overwrite-uids β€” overwrite existing UIDs

πŸ‘‘ output options

output file format:

  • +F, --write-file β€” write file format (default)
  • -F, --write-dataset β€” write data set without file meta information

output transfer syntax:

  • +t=, --write-xfer-same β€” write with same TS as input (default)
  • +te, --write-xfer-little β€” write with explicit VR little endian TS
  • +tb, --write-xfer-big β€” write with explicit VR big endian TS
  • +ti, --write-xfer-implicit β€” write with implicit VR little endian TS
  • +td, --write-xfer-deflated β€” write with deflated explicit VR little endian TS

post-1993 value representations:

  • +u, --enable-new-vr β€” enable support for new VRs (UN/UT) (default)
  • -u, --disable-new-vr β€” disable support for new VRs, convert to OB

group length encoding:

  • +g=, --group-length-recalc β€” recalculate group lengths if present (default)
  • +g, --group-length-create β€” always write with group length elements
  • -g, --group-length-remove β€” always write without group length elements

length encoding in sequences and items:

  • +e, --length-explicit β€” write with explicit lengths (default)
  • -e, --length-undefined β€” write with undefined lengths

data set trailing padding (not with --write-dataset):

  • -p=, --padding-retain β€” do not change padding (default if not --write-dataset)
  • -p, --padding-off β€” no padding (implicit if --write-dataset)
  • +p, --padding-create [f]ile-pad [i]tem-pad: integer β€” align file on multiple of f bytes and items on multiple of i bytes

deflate compression level (only with --write-xfer-deflated):

  • +cl, --compression-level [l]evel: integer (default: 6) β€” 0=uncompressed, 1=fastest, 9=best compression

✨ NOTES ✨

πŸ’€ DICOM Conformance

the xml2dsr utility supports the following SOP Classes, and yes we're listing every single one because she's thorough πŸ’…

  • SpectaclePrescriptionReportStorage β€” 1.2.840.10008.5.1.4.1.1.78.6
  • MacularGridThicknessAndVolumeReportStorage β€” 1.2.840.10008.5.1.4.1.1.79.1
  • BasicTextSRStorage β€” 1.2.840.10008.5.1.4.1.1.88.11
  • EnhancedSRStorage β€” 1.2.840.10008.5.1.4.1.1.88.22
  • ComprehensiveSRStorage β€” 1.2.840.10008.5.1.4.1.1.88.33
  • Comprehensive3DSRStorage β€” 1.2.840.10008.5.1.4.1.1.88.34
  • ProcedureLogStorage β€” 1.2.840.10008.5.1.4.1.1.88.40
  • MammographyCADSRStorage β€” 1.2.840.10008.5.1.4.1.1.88.50
  • KeyObjectSelectionDocumentStorage β€” 1.2.840.10008.5.1.4.1.1.88.59
  • ChestCADSRStorage β€” 1.2.840.10008.5.1.4.1.1.88.65
  • XRayRadiationDoseSRStorage β€” 1.2.840.10008.5.1.4.1.1.88.67
  • RadiopharmaceuticalRadiationDoseSRStorage β€” 1.2.840.10008.5.1.4.1.1.88.68
  • ColonCADSRStorage β€” 1.2.840.10008.5.1.4.1.1.88.69
  • ImplantationPlanSRStorage β€” 1.2.840.10008.5.1.4.1.1.88.70
  • AcquisitionContextSRStorage β€” 1.2.840.10008.5.1.4.1.1.88.71
  • SimplifiedAdultEchoSRStorage β€” 1.2.840.10008.5.1.4.1.1.88.72
  • PatientRadiationDoseSRStorage β€” 1.2.840.10008.5.1.4.1.1.88.73
  • PlannedImagingAgentAdministrationSRStorage β€” 1.2.840.10008.5.1.4.1.1.88.74
  • PerformedImagingAgentAdministrationSRStorage β€” 1.2.840.10008.5.1.4.1.1.88.75
  • WaveformAnnotationSRStorage β€” 1.2.840.10008.5.1.4.1.1.88.77
  • RenditionSelectionDocumentRealTimeCommunication β€” 1.2.840.10008.10.4 (*)
(*) heads up bestie: this is not a Storage SOP Class, but used for Real-Time Communication. 🫢

please note that currently only mandatory and some optional attributes are supported. so like, not everything, but a lot. ✨

🧚 Character Encoding

the DICOM character encoding is determined automatically from the element with tag "0008,0005" (Specific Character Set) β€” if present. the following character sets are currently supported (requires libxml to include iconv support, see --version output):

  • ASCII β€” (ISO_IR 6) β€” (UTF-8)
  • UTF-8 β€” "ISO_IR 192" β€” (UTF-8)
  • ISO Latin 1 β€” "ISO_IR 100" β€” (ISO-8859-1)
  • ISO Latin 2 β€” "ISO_IR 101" β€” (ISO-8859-2)
  • ISO Latin 3 β€” "ISO_IR 109" β€” (ISO-8859-3)
  • ISO Latin 4 β€” "ISO_IR 110" β€” (ISO-8859-4)
  • ISO Latin 5 β€” "ISO_IR 148" β€” (ISO-8859-9)
  • ISO Latin 9 β€” "ISO_IR 203" β€” (ISO-8859-15)
  • Cyrillic β€” "ISO_IR 144" β€” (ISO-8859-5)
  • Arabic β€” "ISO_IR 127" β€” (ISO-8859-6)
  • Greek β€” "ISO_IR 126" β€” (ISO-8859-7)
  • Hebrew β€” "ISO_IR 138" β€” (ISO-8859-8)
  • Thai β€” "ISO_IR 166" β€” (TIS-620)
  • Japanese β€” "ISO 2022 IR 13\ISO 2022 IR 87" β€” (ISO-2022-JP)
  • Korean β€” "ISO 2022 IR 6\ISO 2022 IR 149" β€” (ISO-2022-KR)
  • Chinese β€” "ISO 2022 IR 6\ISO 2022 IR 58" β€” (ISO-2022-CN)
  • Chinese β€” "GB18030" β€” (GB18030)
  • Chinese β€” "GBK" β€” (GBK)

πŸ“ Compression

if libxml is compiled with zlib support, the input file (xmlfile-in) can also be compressed with ZIP, which usually results in much smaller files. check the output of option --version to see whether zlib support is available. iconic behavior honestly πŸ”₯

😭 Limitations

the XML Schema dsr2xml.xsd does not support all variations of the dsr2xml output format. however, the default output format (plus option --use-xml-namespace) should work. so like, keep it default bestie πŸ’œ

different versions of libxml seem to have different limits for the maximum length of an XML element value. therefore, it should be avoided to use very long element values. a typical limit for libxml version 2.7.3 (and above) is 10 MB for a single element value. no cap, don't push her past that πŸ’€


✨ LOGGING ✨

the level of logging output of the various command line tools and underlying libraries can be specified by the user. by default, only errors and warnings are written to the standard error stream. πŸ¦‹

using option --verbose also informational messages like processing details are reported. option --debug can be used to get more details on the internal activity, e. g. for debugging purposes. other logging levels can be selected using option --log-level. in --quiet mode only fatal errors are reported. in such very severe error events, the application will usually terminate. for more details on the different logging levels, see documentation of module "oflog". πŸ’…

in case the logging output should be written to file (optionally with logfile rotation), to syslog (Unix) or the event log (Windows) option --log-config can be used. this configuration file also allows for directing only certain messages to a particular output stream and for filtering certain messages based on the module or application where they are generated. an example configuration file is provided in <etcdir>/logger.cfg. πŸŽ€


✨ COMMAND LINE ✨

all command line tools use the following notation for parameters: square brackets enclose optional values (0-1), three trailing dots indicate that multiple values are allowed (1-n), a combination of both means 0 to n values. ⭐

command line options are distinguished from parameters by a leading + or - sign, respectively. usually, order and position of command line options are arbitrary (i.e. they can appear anywhere). however, if options are mutually exclusive the rightmost appearance is used. this behavior conforms to the standard evaluation rules of common Unix shells. πŸ’€

in addition, one or more command files can be specified using an @ sign as a prefix to the filename (e. g. @command.txt). such a command argument is replaced by the content of the corresponding text file (multiple whitespaces are treated as a single separator unless they appear between two quotation marks) prior to any further evaluation. please note that a command file cannot contain another command file β€” no inception, bestie πŸ™ˆ. this simple but effective approach allows one to summarize common combinations of options/parameters and avoids longish and confusing command lines (an example is provided in file <datadir>/dumppat.txt). ✨


✨ ENVIRONMENT ✨

the xml2dsr utility will attempt to load DICOM data dictionaries specified in the DCMDICTPATH environment variable. by default, i.e. if the DCMDICTPATH environment variable is not set, the file <datadir>/dicom.dic will be loaded unless the dictionary is built into the application (default for Windows). πŸŽ€

the default behavior should be preferred and the DCMDICTPATH environment variable only used when alternative data dictionaries are required. the DCMDICTPATH environment variable has the same format as the Unix shell PATH variable in that a colon (":") separates entries. on Windows systems, a semicolon (";") is used as a separator. the data dictionary code will attempt to load each file specified in the DCMDICTPATH environment variable. it is an error if no data dictionary can be loaded. 😭


✨ FILES ✨

  • <datadir>/dsr2xml.xsd β€” XML Schema file πŸ¦‹

πŸ’« SEE ALSO πŸ’«

  • dsr2xml(1) β€” the reverse girlypop of this whole operation, bestie. She takes a DSR file and turns it back into XML, so like… the two of them are literally each other's mirror selfie. Obsessed πŸͺžβœ¨

Copyright (C) 2003-2026 by OFFIS e.V., Escherweg 2, 26121 Oldenburg, Germany.

That's the legal queen right there β€” OFFIS e.V., posted up at Escherweg 2, 26121 Oldenburg, Germany, holding it down since 2003 all the way through 2026. Respect the elders fr fr πŸ‘‘πŸ«Ά


okay that's the whole page, bestie!! πŸ’– You made it to the end, and honestly? Iconic behavior. This was Version 3.7.1, dated Sat Oct 17 2026 09:34:01 β€” so go forth, convert those XML files to DSR, and slay βœ¨πŸ¦‹πŸ’… periodt.

πŸ“¦ where this page comes from