Our Modality Worklist is now part of HL7Kit 2018. For additional information please visit HL7Kit 2018 website. The DICOM Modality Worklist Service is a fundamental part of the clinical imaging workflow. Modern Imaging Modalities integrate with the department scheduler (or sometime the RIS) to receive the patient and procedure parameters thus enabling a true, digital, paperless workflow. RZDCX [...]
Support for MPEG2 and MPEG4 video is quite new in DICOM. Video encoding was introduced to the DICOM standard using new transfer syntaxes. It is important to note that not all DICOM compliant application support these transfer syntaxes. Don't know how to check if your application supports transfer syntaxes? Contact us and we will be happy to consult. **Not [...]
PDF (Portable Document Format) is widely used for various purposes in the clinical workflow. The DICOM Standard defines a special SOP Class called “Encapsulated PDF Document” (SOP Class UID: 1.2.840.10008.5.1.4.188.8.131.52) It is important to note that not all systems supports the Encapsulated PDF Document SOP Class and we advise you to verify this issue in [...]
DICOMIZER is a powerful DICOM converter with an impressive set of features, designed to provide healthcare imaging personnel with a holistic solution for clinic work. Send and Receive DICOM files using the DICOM Network Protocol, generate reports, capture images and add annotations, convert Images, PDF Document and Videos to DICOM and send them to the PACS. Troubleshoot connectivity issues [...]
Web Access to DICOM Objects. Part 18 of the DICOM standard details an interface to DICOM Objects using HTTP. WADO enables, for example, retrieving DICOM images as JPEG using an HTTP GET request. The importance and acceptance of WADO increased dramatically together with the internet revolution and increasing use of cloud services and PACS [...]
Value Multiplicity. A DICOM Element may have multiple values. String values are separated by \ while the VM of binary values is determined by dividing the element length in bytes by the size of one value. For example the VM of a data element of type US (Unsigned Short) that has a length of 6 [...]
Acronym for “Unique Identifier”. UID’s are widely used in DICOM and are assigned to objects, classes, transfer syntaxes, special services, and specific data elements. NEMA registers DICOM UID’s and every instance of a DICOM application should have a UID prefix that it can use to generate new UID’s from.
A DICOM Service that is used to “pass the ownership” on DICOM Instances from one application to another. It confirms that a DICOM Application stores a set of DICOM Instances in a similar way to the “commit” SQL command. When receiving successful commit result, an application can assume that the instances are safely stored by [...]