Difference between revisions of "Store"
(→Storage of DICOM files) |
|||
| (4 intermediate revisions by the same user not shown) | |||
| Line 17: | Line 17: | ||
| sopClass || optional || The Service-Object Pair (SOP). Is overwritten by the value of the GVBuffer property "DICOM_SOP_CLASS". | | sopClass || optional || The Service-Object Pair (SOP). Is overwritten by the value of the GVBuffer property "DICOM_SOP_CLASS". | ||
Admitted values: | Admitted values: | ||
| − | - | + | - CT Image Storage - 1.2.840.10008.5.1.4.1.1.2 |
| − | - | + | - Enhanced CT Image Storage - 1.2.840.10008.5.1.4.1.1.2.1 |
| − | - | + | - MR Image Storage - 1.2.840.10008.5.1.4.1.1.4 |
| − | - | + | - Enhanced MR Image Storage - 1.2.840.10008.5.1.4.1.1.4.1 |
| + | - Secondary Capture Image Storage - 1.2.840.10008.5.1.4.1.1.7 | ||
|- | |- | ||
| − | | sopInstanceUID || optional || | + | | sopInstanceUID || optional || The Unique Identifier of instance. Is overwritten by the value of the GVBuffer property "DICOM_SOP_INSTANCE_UID". |
|- | |- | ||
| − | | dicomFile || optional || | + | | dicomFile || optional || The path of a DICOM File. Is overwritten by the value of the GVBuffer property "DICOM_FILE_PATH". |
|} | |} | ||
| + | |||
| + | ==Storage of DICOM files== | ||
| + | DICOM files are stored in the file system. The directory of local storage is configured by the [[DICOM Listener]] in '''GVAdapters'''. | ||
| + | |||
| + | The system creates a folder named with the value of PatientID which we want to store DICOM images. In this folder the image is saved in DICOM format (.dcm) and a transformed version divided into two files : a file in XML format (.xml) for image metadata and a file in binary format (.data) containing the pixel data (the image itself). | ||
| + | Image reconstruction is possible by keeping track in the xml file the name of binary file associated. | ||
| + | |||
| + | |||
| + | The following xml code shows an exemple of element in an xml file containing the name of binary file associated: | ||
| + | <entry> | ||
| + | <OtherWordString> | ||
| + | <elementTag> | ||
| + | <fElement>16</fElement> | ||
| + | <fGroup>32736</fGroup> | ||
| + | <fName>Pixel Data</fName> | ||
| + | <fValueRepresentation> | ||
| + | < code>UN< /code> | ||
| + | <name>Unknown</name> | ||
| + | </fValueRepresentation> | ||
| + | </elementTag> | ||
| + | <fValueLength>204800</fValueLength> | ||
| + | <fValueMultiplicity>1</fValueMultiplicity> | ||
| + | <ImageData>1.3.46.670589.5.2.10.2156913941.892665339.718742.data</ImageData> | ||
| + | </OtherWordString> | ||
| + | </entry> | ||
| + | |||
| + | Example of DICOM file stored: [[File:Example dicom file.zip]] | ||
Latest revision as of 15:07, 15 July 2015
Description
Store service is the operation that allows the storage of a DICOM object. It can be invoked by the client to ask the server to store a specific object, or is generated in response to a Move call to provide to trigger the mechanism of delivery of DICOM objects.
GreenVulcano® ESB Configuration
The dicom-store-call Element is used by Channel and routed-call. It has the attributes:
| Attribute | Type | Description |
|---|---|---|
| type | fixed | This attribute must assume the value call. |
| class | fixed | This attribute must assume the value it.greenvulcano.gvesb.virtual.dicom.DicomStoreCallOperation. |
| name | required | Operation name. Used in the Flow section to associate workflow nodes to VCL operations. |
| nameAssociation | required | Association name. It is used for the connection to a host. It is configured in GVAdapters. This value is referenced by a GVBuffer property "DICOM_ASSOCIATION" or manually, choosing a value among those available. The property has priority over the manual configuration. |
| sopClass | optional | The Service-Object Pair (SOP). Is overwritten by the value of the GVBuffer property "DICOM_SOP_CLASS".
Admitted values:
- CT Image Storage - 1.2.840.10008.5.1.4.1.1.2
- Enhanced CT Image Storage - 1.2.840.10008.5.1.4.1.1.2.1
- MR Image Storage - 1.2.840.10008.5.1.4.1.1.4
- Enhanced MR Image Storage - 1.2.840.10008.5.1.4.1.1.4.1
- Secondary Capture Image Storage - 1.2.840.10008.5.1.4.1.1.7
|
| sopInstanceUID | optional | The Unique Identifier of instance. Is overwritten by the value of the GVBuffer property "DICOM_SOP_INSTANCE_UID". |
| dicomFile | optional | The path of a DICOM File. Is overwritten by the value of the GVBuffer property "DICOM_FILE_PATH". |
Storage of DICOM files
DICOM files are stored in the file system. The directory of local storage is configured by the DICOM Listener in GVAdapters.
The system creates a folder named with the value of PatientID which we want to store DICOM images. In this folder the image is saved in DICOM format (.dcm) and a transformed version divided into two files : a file in XML format (.xml) for image metadata and a file in binary format (.data) containing the pixel data (the image itself). Image reconstruction is possible by keeping track in the xml file the name of binary file associated.
The following xml code shows an exemple of element in an xml file containing the name of binary file associated:
<entry>
<OtherWordString>
<elementTag>
<fElement>16</fElement>
<fGroup>32736</fGroup>
<fName>Pixel Data</fName>
<fValueRepresentation>
< code>UN< /code>
<name>Unknown</name>
</fValueRepresentation>
</elementTag>
<fValueLength>204800</fValueLength>
<fValueMultiplicity>1</fValueMultiplicity>
<ImageData>1.3.46.670589.5.2.10.2156913941.892665339.718742.data</ImageData>
</OtherWordString>
</entry>
Example of DICOM file stored: File:Example dicom file.zip
