usage: pdf2dcm [options] <pdf|cda|stl|mtl|obj|genozip|bzip2-file>
<dicom-file>
or pdf2dcm [options] <pdf|cda|stl|mtl|obj|genozip|bzip2-file>...
<dicom-outdir>
or pdf2dcm [options] <pdf|cda|stl|mtl|obj|genozip|bzip2-indir>...
<dicom-outdir>
Encapsulate bulkdata PDF (extension pdf), CDA (extension xml), STL
(extension stl), MTL (extension mtl) or OBJ (extension obj) or GENOZIP
(extension genozip) or VCF Bzip2 (extensions vcf.bz2, vcfbzip2, vcfbz2) or
Document Bzip2 (extensions boz, bz2) file(s) (or present in directories)
into DICOM file(s) (or into DICOM directory). DICOM attributes can be
specified via command line (using -m option) or a XML file (using -f
option). If no option is specified, by default they are generated using
sample metadata file present in the tool. If all the options are
specified, system will generate metadata first from sample metadata file
then from file specified by user and lastly add the attributes specified
individually on command line. The Type 1 and Type 2 attributes, if
missing, will be generated by the system.Supported content types are
application/pdf (for PDF files), text/xml (for CDA files), application/sla
or model/stl or model/x.stl-binary (for STL files), model/mtl (for MTL
files), model/obj (for OBJ files), application/vnd.genozip (for Genozip
compressed genomic files), application/prs.vcfbzip2 (for Bzip2 compressed
genomic data VCF files) and application/x-bzip2 (for Bzip2 compressed
genomic data Document files).
-
Options:
--contentType <contentType> Specify MIME type of bulkdata file(s).
If specified, content type of individual
file(s) (and/or in directory(-ies))
shall not be probed.
--encapsulatedDocLength If specified, supplement Encapsulated
Document Length (0042,0015) attribute in
metadata.
-f <xml-file> specify included DICOM attributes by XML
presentation in <xml-file>
-h,--help display this help and exit
-s <[seq.]attr=value> specify included DICOM Attribute. attr
can be specified by keyword or tag value
(in hex), e.g. PatientName or 00100010.
Attributes in nested Datasets can be
specified by including the keyword/tag
value of the sequence attribute, e.g.
00400275.00400009 for Scheduled
Procedure Step ID in the Request
Attributes Sequence. Overrides DICOM
attributes specified by -f <xml-file>
-V,--version output version information and exit
-
Example 1: pdf2dcm -f metadata.xml pdfFile.pdf object.dcm
=> Encapsulate PDF document by first generating metadata from
etc/pdf2dcm/encapsulatedPDFMetadata.xml and then adding DICOM attributes
specified in metadata.xml into DICOM Object.
-
Example 2: pdf2dcm -f metadata.xml cdaFile.xml object.dcm
=> Encapsulate CDA file by first generating metadata from
etc/pdf2dcm/encapsulatedCDAMetadata.xml and then adding DICOM attributes
specified in metadata.xml into DICOM Object.
-
Example 3: pdf2dcm -f metadata.xml --contentType model/stl stlFile.stl
stlObject.dcm
=> Encapsulate STL file by first generating metadata from
etc/pdf2dcm/encapsulatedSTLMetadata.xml and then adding DICOM attributes
specified in metadata.xml into DICOM Object. Additionally, content type of
the file returned by system will be ignored and instead specified content
type shall be considered for correctly encapsulating the file.
-
Example 4: pdf2dcm -f metadata.xml --contentType model/mtl mtlFile.mtl
mtlObject.dcm
=> Encapsulate MTL file by first generating metadata from
etc/pdf2dcm/encapsulatedMTLMetadata.xml and then adding DICOM attributes
specified in metadata.xml into DICOM Object. Additionally, content type of
the file returned by system will be ignored and instead specified content
type shall be considered for correctly encapsulating the file.
-
Example 5: pdf2dcm -f metadata.xml --contentType model/obj objFile.obj
objObject.dcm
=> Encapsulate OBJ file by first generating metadata from
etc/pdf2dcm/encapsulatedOBJMetadata.xml and then adding DICOM attributes
specified in metadata.xml into DICOM Object. Additionally, content type of
the file returned by system will be ignored and instead specified content
type shall be considered for correctly encapsulating the file.
-
Example 6: pdf2dcm -f metadata.xml --contentType application/vnd.genozip
genozipFile.genozip genozipObject.dcm
=> Encapsulate Genozip file by first generating metadata from
etc/pdf2dcm/encapsulatedGenozipMetadata.xml and then adding DICOM
attributes specified in metadata.xml into DICOM Object. Additionally,
content type of the file returned by system will be ignored and instead
specified content type shall be considered for correctly encapsulating the
file.
-
Example 7: pdf2dcm -m PatientName=Simson^Homer -m PatientSex=M -- file.pdf
object.dcm
=> Encapsulate PDF document first generating metadata from
etc/pdf2dcm/encapsulatedPDFMetadata.xml and then adding given PatientName
and PatientSex into DICOM Image Object.
-
Example 8: pdf2dcm file.pdf file.stl dicom-dir
=> Encapsulate the specified PDF and STL files to DICOM objects in
dicom-dir.
-
Example 9: pdf2dcm pdf-dir cda-dir stl-dir dicom-object-dir
=> Encapsulate PDF files, CDA files and STL files specified in mentioned
directories to DICOM objects in dicom-object-dir.
-
Example 10: pdf2dcm -f metadata.xml --contentType application/prs.vcfbzip2
prs-vcf-bzip2.vcfbz2 prs-vcf-bzip2.dcm
=> Encapsulate Bzip2 compressed genomic data VCF file by first generating
metadata from etc/pdf2dcm/encapsulatedVCFBzip2Metadata.xml and then adding
DICOM attributes specified in metadata.xml into DICOM Object.
Additionally, content type of the file returned by system will be ignored
and instead specified content type shall be considered for correctly
encapsulating the file.