Store - Revision history

M.sutera: /* Storage of DICOM files */

2015-07-15T15:07:07Z

‎Storage of DICOM files

M.sutera at 15:03, 15 July 2015

2015-07-15T15:03:55Z

M.sutera at 13:22, 15 July 2015

2015-07-15T13:22:08Z

M.sutera at 08:58, 15 July 2015

2015-07-15T08:58:37Z

M.sutera at 14:21, 14 July 2015

2015-07-14T14:21:14Z

M.sutera at 14:09, 14 July 2015

2015-07-14T14:09:57Z

M.sutera at 14:08, 14 July 2015

2015-07-14T14:08:51Z

M.sutera at 13:16, 14 July 2015

2015-07-14T13:16:45Z

M.sutera at 10:39, 14 July 2015

2015-07-14T10:39:39Z

M.sutera: Created page with "==Description== =={{GVESB}} Configuration== The dicom-store-call Element is used by Channel and routed-call. It has the attributes:"

2015-07-14T09:04:13Z

Created page with "==Description== =={{GVESB}} Configuration== The dicom-store-call Element is used by Channel and routed-call. It has the attributes:"

New page

==Description==

=={{GVESB}} Configuration==
The dicom-store-call Element is used by [[Channel]] and [[routed-call]]. It has the attributes:

@@ Line 30: / Line 30: @@
 ==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.

← Older revision		Revision as of 15:03, 15 July 2015
Line 29:		Line 29:

	==Storage of DICOM files==		==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]]

← Older revision		Revision as of 13:22, 15 July 2015
Line 27:		Line 27:
	\| dicomFile \|\| optional \|\| The path of a DICOM File. Is overwritten by the value of the GVBuffer property "DICOM_FILE_PATH".		\| dicomFile \|\| optional \|\| The path of a DICOM File. Is overwritten by the value of the GVBuffer property "DICOM_FILE_PATH".
	\|}		\|}
		+
		+	==Storage of DICOM files==

@@ Line 23: / Line 23: @@
          - Secondary Capture Image Storage - 1.2.840.10008.5.1.4.1.1.7
 |-
-| sopInstanceUID || optional || Is overwritten by the value of the GVBuffer property "DICOM_SOP_INSTANCE_UID".
+| 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".
 |}

@@ Line 17: / Line 17: @@
 | sopClass || optional || The Service-Object Pair (SOP). Is overwritten by the value of the GVBuffer property "DICOM_SOP_CLASS".
      Admitted values:
-         - Patient Root Query/Retrieve Information Model - FIND 1.2.840.10008.5.1.4.1.2.1.1
+         - CT Image Storage - 1.2.840.10008.5.1.4.1.1.2
-         - Study Root Query/Retrieve Information Model - FIND 1.2.840.10008.5.1.4.1.2.2.1
+         - Enhanced CT Image Storage - 1.2.840.10008.5.1.4.1.1.2.1
-         - Modality Worklist Information Model - FIND 1.2.840.10008.5.1.4.31
+         - MR Image Storage - 1.2.840.10008.5.1.4.1.1.4
-         - Patient/Study Only Query/Retrieve Information Model - FIND 1.2.840.10008.5.1.4.1.2.3.1
+         - Enhanced MR Image Storage - 1.2.840.10008.5.1.4.1.1.4.1
 |-
-| sopInstanceUID || optional ||
+| sopInstanceUID || optional || 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".
 |}

@@ Line 13: / Line 13: @@
 | 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 property "DICOM_ASSOCIATION" or manually, choosing a value among those available.
+| 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 ||

@@ Line 1: / Line 1: @@
 ==Description==
 =={{GVESB}} Configuration==
 The dicom-store-call Element is used by [[Channel]] and [[routed-call]]. It has the attributes: