GreenVulcano Wiki - User contributions [en]

Store

2015-07-15T15:07:07Z

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

==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.

=={{GVESB}} Configuration==
The dicom-store-call Element is used by [[Channel]] and [[routed-call]]. It has the attributes:
{|class="gvtable"
! 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]]

Store

2015-07-15T15:03:55Z

M.sutera:

==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.

=={{GVESB}} Configuration==
The dicom-store-call Element is used by [[Channel]] and [[routed-call]]. It has the attributes:
{|class="gvtable"
! 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]]

File:Example dicom file.zip

2015-07-15T15:03:37Z

M.sutera: uploaded a new version of "File:Example dicom file.zip": Example of DICOM file. Example of XML file with data file which represent the DICOM file.

Example of DICOM file.
Example of XML file with data file which represent the DICOM file.

File:Example dicom file.zip

2015-07-15T14:16:00Z

M.sutera: Example of DICOM file. Example of XML file with data file which represent the DICOM file.

Example of DICOM file.
Example of XML file with data file which represent the DICOM file.

Store

2015-07-15T13:22:08Z

M.sutera:

DICOM

2015-07-15T10:36:10Z

M.sutera:

==Overview==
[http://dicom.nema.org/ DICOM] - Digital Imaging and Communications in Medicine - is the international standard for medical images and related information (ISO 12052). It defines the formats for medical images that can be exchanged with the data and quality necessary for clinical use. DICOM is implemented in almost every radiology, cardiology imaging, and radiotherapy device (X-ray, CT, MRI, ultrasound, etc.), and increasingly in devices in other medical domains such as ophthalmology and dentistry. From the emergency department, to cardiac stress testing, to breast cancer detection, DICOM is the standard that makes medical imaging work — for doctors and for patients.

==Data Format==
DICOM differs from some, but not all, data formats in that it groups information into data sets. That means that a file of a chest x-ray image, for example, actually contains the patient ID within the file, so that the image can never be separated from this information by mistake. This is similar to the way that image formats such as JPEG can also have embedded tags to identify and otherwise describe the image.

A DICOM data object consists of a number of attributes, including items such as name, ID, etc., and also one special attribute containing the image pixel data (i.e. logically, the main object has no "header" as such: merely a list of attributes, including the pixel data). A single DICOM object can have only one attribute containing pixel data. For many modalities, this corresponds to a single image. But note that the attribute may contain multiple "frames", allowing storage of cine loops or other multi-frame data.

DICOM uses three different Data Element encoding schemes. With Explicit Value Representation (VR) Data Elements, for VRs that are not OB, OW, OF, SQ, UT, or UN, the format for each Data Element is: GROUP (2 bytes) ELEMENT (2 bytes) VR (2 bytes) LengthInByte (2 bytes) Data (variable length).

==DICOM Connector==
The {{GVESB}} DICOM connector enables the operations that can be performed on a DICOM object.
The use of the connector joint with the peculiarities of the {{GVESB}} [[Virtual Layer]] allows the management of DICOM applications in a simple and efficient way, separating the logic of the process implementation from the specific management of the messages and their structure, independently from the DICOM standard used.
Basically the connector allows the virtualization of the input/output operations to a DICOM application, making available to the service definition process the interfaces able to hide all the technical details related to DICOM standard.

The Outbound DICOM Connector allows association verification and research,acquisition and storage of DICOM objects on PACS systems in the network.

The Inbound DICOM Connector allows to choose which services accept , provides answers about the status of the association between the system and the system questioner and retrieval of images between them.

== Outbound DICOM Connector==
It is necessary to set up one or more [[Association]] to connect to external PACS.
The DICOM services implemented by the outbound connector are :
* [[Echo]]
* [[Find]]
* [[Move]]
* [[Store]]

== Inbound DICOM Connector==
It is necessary to set up one or more [[DICOM Listener]] to accept requests from various external PACS.
The DICOM services implemented by the inbound connector are :
* [[Echo]]
* Find
* Move
* [[Store]]

DICOM

2015-07-15T10:35:24Z

M.sutera: /* Inbound DICOM Connector */

DICOM

2015-07-15T10:28:33Z

M.sutera:

DICOM Listener

2015-07-15T10:06:32Z

M.sutera:

==Description==
The DICOM Listener is able to accept the demands posed by external PACS and redirects them to the appropriate service able to handle the request.

==DICOM Listener Configuration==
The following table shows the element's attributes. It is configured in '''GVAdapters''' in the Local element.
{|class="gvtable"
! Attribute !! Type !! Description
|-
| applicationEntity || required || Local Application Entity name.
|-
| listenerPort || required || Local Association Acceptor port.
|-
| dicomStoreDirectory || required || DICOM local file store.
|}

DICOM Listener

2015-07-15T10:05:41Z

M.sutera:

==Description==
The dicom listener is able to accept the demands posed by external PACS and redirects them to the appropriate service able to handle the request.

==DICOM Listener Configuration==
The following table shows the element's attributes. It is configured in '''GVAdapters''' in the Local element.
{|class="gvtable"
! Attribute !! Type !! Description
|-
| applicationEntity || required || Local Application Entity name.
|-
| listenerPort || required || Local Association Acceptor port.
|-
| dicomStoreDirectory || required || DICOM local file store.
|}

DICOM Listener

2015-07-15T10:05:23Z

M.sutera: Created page with "==Description== The dicom listener is able to accept the demands posed by external PACS and redirects them to the appropriate service able to handle the request. ==DICOM Listene..."

==Description==
The dicom listener is able to accept the demands posed by external PACS and redirects them to the appropriate service able to handle the request.

==DICOM Listener Configuration==
The following table shows the element's attributes. It is configured in '''GVAdapters'''in the Local element.
{|class="gvtable"
! Attribute !! Type !! Description
|-
| applicationEntity || required || Local Application Entity name.
|-
| listenerPort || required || Local Association Acceptor port.
|-
| dicomStoreDirectory || required || DICOM local file store.
|}

Association

2015-07-15T09:54:46Z

M.sutera: /* Association Configuration */

==Description==
The association contains all the information to make a direct connection with an external PACS.
==Association Configuration==
The following table shows the element's attributes. It is configured in '''GVAdapters''' in the Association element.
{|class="gvtable"
! Attribute !! Type !! Description
|-
| name || required || Association name.
|-
| host || required || Association host.
|-
| port || required || Association port.
|}

Association

2015-07-15T09:53:50Z

M.sutera:

==Description==
The association contains all the information to make a direct connection with an external PACS.
==Association Configuration==
The following table shows the element's attributes. It is configured in '''GVAdapters''' on element Association.
{|class="gvtable"
! Attribute !! Type !! Description
|-
| name || required || Association name.
|-
| host || required || Association host.
|-
| port || required || Association port.
|}

Association

2015-07-15T09:49:45Z

M.sutera:

==Description==
The association contains all the information to make a direct connection with an external PACS.
==Association Configuration==
The following table shows the element's attributes. It is configured in '''GVAdapters'''.
{|class="gvtable"
! Attribute !! Type !! Description
|-
| name || required || Association name.
|-
| host || required || Association host.
|-
| port || required || Association port.
|}

Association

2015-07-15T09:40:21Z

M.sutera:

==Description==
The association contains all the information to make a direct connection with an external PACS. It is configured in '''GVAdapters'''.

==Association Configuration==
{|class="gvtable"
! Attribute !! Type !! Description
|-
| name || required || Association name.
|-
| host || required || Association host.
|-
| port || required || Association port.
|}

DICOM

2015-07-15T09:37:48Z

M.sutera: /* Inbound DICOM Connector */

Association

2015-07-15T09:27:41Z

M.sutera: Created page with "==Description== The association contains all the information to make a direct connection with an external PACS. It is configured in '''GVAdapters'''. =={{GVESB}} Configuration==..."

==Description==
The association contains all the information to make a direct connection with an external PACS. It is configured in '''GVAdapters'''.

=={{GVESB}} Configuration==
{|class="gvtable"
! Attribute !! Type !! Description
|-
| name || required || Association name.
|-
| host || required || Association host.
|-
| port || required || Association port.
|}

DICOM

2015-07-15T09:13:33Z

M.sutera:

==Overview==
[http://dicom.nema.org/ DICOM] - Digital Imaging and Communications in Medicine - is the international standard for medical images and related information (ISO 12052). It defines the formats for medical images that can be exchanged with the data and quality necessary for clinical use. DICOM is implemented in almost every radiology, cardiology imaging, and radiotherapy device (X-ray, CT, MRI, ultrasound, etc.), and increasingly in devices in other medical domains such as ophthalmology and dentistry. From the emergency department, to cardiac stress testing, to breast cancer detection, DICOM is the standard that makes medical imaging work — for doctors and for patients.

==Data Format==
DICOM differs from some, but not all, data formats in that it groups information into data sets. That means that a file of a chest x-ray image, for example, actually contains the patient ID within the file, so that the image can never be separated from this information by mistake. This is similar to the way that image formats such as JPEG can also have embedded tags to identify and otherwise describe the image.

A DICOM data object consists of a number of attributes, including items such as name, ID, etc., and also one special attribute containing the image pixel data (i.e. logically, the main object has no "header" as such: merely a list of attributes, including the pixel data). A single DICOM object can have only one attribute containing pixel data. For many modalities, this corresponds to a single image. But note that the attribute may contain multiple "frames", allowing storage of cine loops or other multi-frame data.

DICOM uses three different Data Element encoding schemes. With Explicit Value Representation (VR) Data Elements, for VRs that are not OB, OW, OF, SQ, UT, or UN, the format for each Data Element is: GROUP (2 bytes) ELEMENT (2 bytes) VR (2 bytes) LengthInByte (2 bytes) Data (variable length).

==DICOM Connector==
The {{GVESB}} DICOM connector enables the operations that can be performed on a DICOM object.
The use of the connector joint with the peculiarities of the {{GVESB}} [[Virtual Layer]] allows the management of DICOM applications in a simple and efficient way, separating the logic of the process implementation from the specific management of the messages and their structure, independently from the DICOM standard used.
Basically the connector allows the virtualization of the input/output operations to a DICOM application, making available to the service definition process the interfaces able to hide all the technical details related to DICOM standard.

The Outbound DICOM Connector allows association verification and research,acquisition and storage of DICOM objects on PACS systems in the network.

The Inbound DICOM Connector allows to choose which services accept , provides answers about the status of the association between the system and the system questioner and retrieval of images between them.

== Outbound DICOM Connector==
It is necessary to set up one or more [[Association]] to connect to external PACS.
The DICOM services implemented by the outbound connector are :
* [[Echo]]
* [[Find]]
* [[Move]]
* [[Store]]

== Inbound DICOM Connector==
The DICOM services implemented by the inbound connector are :
* [[Echo]]
* [[Store]]

Find

2015-07-15T08:58:58Z

M.sutera:

==Description==
Find service establishes an association between the client that invoked it and the provider to which the call is intended; the service requires the provider to make a match with all specified keys in the identifier of request; the provider generates a response Find for each match and displays all key fields and attributes known required. When the process is completed response is generated and sent a reply Find with a state of success ( Success). Refusal or failure to reply indicates that the provider is unable to process the request.

=={{GVESB}} Configuration==
The dicom-find-call Element is used by [[Channel]] and [[routed-call]]. It has the attributes:
{|class="gvtable"
! 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.DicomFindCallOperation'''.
|-
| 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.
|-
| queryLevel || optional || The Information Entity level. Is overwritten by the value of the GVBuffer property "DICOM_QUERY_LEVEL".
Admitted values:
- PATIENT
- STUDY
- SERIES
- INSTANCE
|-
| patientID || optional || The ID of the patient. Is overwritten by the value of the GVBuffer property "DICOM_PATIENT_ID".
|-
| patientName || optional || The Name of the patient. Is overwritten by the value of the GVBuffer property "DICOM_PATIENT_NAME".
|-
| patientSex || optional || The Sex of the patient. Is overwritten by the value of the GVBuffer property "DICOM_PATIENT_SEX".
|-
| 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
- Study Root Query/Retrieve Information Model - FIND 1.2.840.10008.5.1.4.1.2.2.1
- Modality Worklist Information Model - FIND 1.2.840.10008.5.1.4.31
- Patient/Study Only Query/Retrieve Information Model - FIND 1.2.840.10008.5.1.4.1.2.3.1
|-
| sopInstanceUID || optional || The Unique Identifier of instance. Is overwritten by the value of the GVBuffer property "DICOM_SOP_INSTANCE_UID".
|-
| studyInstanceUID || optional || The Unique Identifier of the study. Is overwritten by the value of the GVBuffer property "DICOM_STUDY_INSTANCE_UID".
|-
| seriesInstanceUID || optional || The Unique Identifier of the series. Is overwritten by the value of the GVBuffer property "DICOM_SERIES_INSTANCE_UID".
|-
| affectedSopClassUID || optional || This parameter may be included in the response/confirmation. Is overwritten by the value of the GVBuffer property "DICOM_AFFECTED_SOP_CLASS_UID".
|-
| affectedSopInstanceUID || optional || This parameter specifies the SOP Instance on which the action is to be performed. Is overwritten by the value of the GVBuffer property "DICOM_AFFECTED_SOP_INSTANCE_UID".
|-
| modalityStudy || optional || Filter using supplied single value and return studies which contain one or more series with that modality. Is overwritten by the value of the GVBuffer property "DICOM_MODALITY_STUDY".
|}

Store

2015-07-15T08:58:37Z

M.sutera:

Move

2015-07-15T08:56:46Z

M.sutera:

==Description==
Move service is the operation for the transfer of a DICOM object. The service establishes an association between the client that invoked it and the provider to which the call is intended; the service provides unique key values to identify the object to be transferred; the provider generates the sub-operations [[Store]] for each identified object to be transferred; when the number of sub- operations [[Store]] reaches zero the provider generate and send a state response of success ( Success). The sub-operations [[Store]] occur on a different association than that of the Move .

=={{GVESB}} Configuration==
The dicom-move-call Element is used by [[Channel]] and [[routed-call]]. It has the attributes:
{|class="gvtable"
! 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.DicomMoveCallOperation'''.
|-
| 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.
|-
| queryLevel || optional || The Information Entity level. Is overwritten by the value of the GVBuffer property "DICOM_QUERY_LEVEL".
Admitted values:
- PATIENT
- STUDY
- SERIES
- INSTANCE
|-
| patientID || optional || The ID of the patient. Is overwritten by the value of the GVBuffer property "DICOM_PATIENT_ID".
|-
| patientName || optional || The Name of the patient. Is overwritten by the value of the GVBuffer property "DICOM_PATIENT_NAME".
|-
| 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 - MOVE 1.2.840.10008.5.1.4.1.2.1.2
- Study Root Query/Retrieve Information Model - MOVE 1.2.840.10008.5.1.4.1.2.2.2
- Patient/Study Only Query/Retrieve Information Model - MOVE 1.2.840.10008.5.1.4.1.2.3.2
|-
| sopClassUID || optional || The Service-Object Pair (SOP) Unique Identifier. Is overwritten by the value of the GVBuffer property "DICOM_SOP_CLASS_UID".
|-
| studyInstanceUID || optional || The Unique Identifier of the study. Is overwritten by the value of the GVBuffer property "DICOM_STUDY_INSTANCE_UID".
|-
| seriesInstanceUID || optional || The Unique Identifier of the series. Is overwritten by the value of the GVBuffer property "DICOM_SERIES_INSTANCE_UID".
|}

Find

2015-07-15T08:49:10Z

M.sutera: /* {{GVESB}} Configuration */

==Description==
Find service establishes an association between the client that invoked it and the provider to which the call is intended; the service requires the provider to make a match with all specified keys in the identifier of request; the provider generates a response Find for each match and displays all key fields and attributes known required. When the process is completed response is generated and sent a reply Find with a state of success ( Success). Refusal or failure to reply indicates that the provider is unable to process the request.

=={{GVESB}} Configuration==
The dicom-find-call Element is used by [[Channel]] and [[routed-call]]. It has the attributes:
{|class="gvtable"
! 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.DicomFindCallOperation'''.
|-
| 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.
|-
| queryLevel || optional || The Information Entity level. Is overwritten by the value of the GVBuffer property "DICOM_QUERY_LEVEL".
Admitted values:
- PATIENT
- STUDY
- SERIES
- INSTANCE
|-
| patientID || optional || The ID of the patient. Is overwritten by the value of the GVBuffer property "DICOM_PATIENT_ID".
|-
| patientName || optional || The Name of the patient. Is overwritten by the value of the GVBuffer property "DICOM_PATIENT_NAME".
|-
| patientSex || optional || The Sex of the patient. Is overwritten by the value of the GVBuffer property "DICOM_PATIENT_SEX".
|-
| 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
- Study Root Query/Retrieve Information Model - FIND 1.2.840.10008.5.1.4.1.2.2.1
- Modality Worklist Information Model - FIND 1.2.840.10008.5.1.4.31
- Patient/Study Only Query/Retrieve Information Model - FIND 1.2.840.10008.5.1.4.1.2.3.1
|-
| sopInstanceUID || optional || The Unique Identifier of Instance. Is overwritten by the value of the GVBuffer property "DICOM_SOP_INSTANCE_UID".
|-
| studyInstanceUID || optional || The Unique Identifier of the study. Is overwritten by the value of the GVBuffer property "DICOM_STUDY_INSTANCE_UID".
|-
| seriesInstanceUID || optional || The Unique Identifier of the series. Is overwritten by the value of the GVBuffer property "DICOM_SERIES_INSTANCE_UID".
|-
| affectedSopClassUID || optional || This parameter may be included in the response/confirmation. Is overwritten by the value of the GVBuffer property "DICOM_AFFECTED_SOP_CLASS_UID".
|-
| affectedSopInstanceUID || optional || This parameter specifies the SOP Instance on which the action is to be performed. Is overwritten by the value of the GVBuffer property "DICOM_AFFECTED_SOP_INSTANCE_UID".
|-
| modalityStudy || optional || Filter using supplied single value and return studies which contain one or more series with that modality. Is overwritten by the value of the GVBuffer property "DICOM_MODALITY_STUDY".
|}

Move

2015-07-14T14:41:44Z

M.sutera:

==Description==
Move service is the operation for the transfer of a DICOM object. The service establishes an association between the client that invoked it and the provider to which the call is intended; the service provides unique key values to identify the object to be transferred; the provider generates the sub-operations [[Store]] for each identified object to be transferred; when the number of sub- operations [[Store]] reaches zero the provider generate and send a state response of success ( Success). The sub-operations [[Store]] occur on a different association than that of the Move .

=={{GVESB}} Configuration==
The dicom-move-call Element is used by [[Channel]] and [[routed-call]]. It has the attributes:
{|class="gvtable"
! 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.DicomMoveCallOperation'''.
|-
| 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.
|-
| queryLevel || optional || The Information Entity level. Is overwritten by the value of the GVBuffer property "DICOM_QUERY_LEVEL".
Admitted values:
- PATIENT
- STUDY
- SERIES
- INSTANCE
|-
| patientID || optional || The ID of the patient. Is overwritten by the value of the GVBuffer property "DICOM_PATIENT_ID".
|-
| patientName || optional || The Name of the patient. Is overwritten by the value of the GVBuffer property "DICOM_PATIENT_NAME".
|-
| 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 - MOVE 1.2.840.10008.5.1.4.1.2.1.2
- Study Root Query/Retrieve Information Model - MOVE 1.2.840.10008.5.1.4.1.2.2.2
- Patient/Study Only Query/Retrieve Information Model - MOVE 1.2.840.10008.5.1.4.1.2.3.2
|-
| sopClassUID || optional || Is overwritten by the value of the GVBuffer property "DICOM_SOP_CLASS_UID".
|-
| studyInstanceUID || optional || Is overwritten by the value of the GVBuffer property "DICOM_STUDY_INSTANCE_UID".
|-
| seriesInstanceUID || optional || Is overwritten by the value of the GVBuffer property "DICOM_SERIES_INSTANCE_UID".
|}

Store

2015-07-14T14:21:14Z

M.sutera:

Find

2015-07-14T14:18:50Z

M.sutera:

==Description==
Find service establishes an association between the client that invoked it and the provider to which the call is intended; the service requires the provider to make a match with all specified keys in the identifier of request; the provider generates a response Find for each match and displays all key fields and attributes known required. When the process is completed response is generated and sent a reply Find with a state of success ( Success). Refusal or failure to reply indicates that the provider is unable to process the request.

=={{GVESB}} Configuration==
The dicom-find-call Element is used by [[Channel]] and [[routed-call]]. It has the attributes:
{|class="gvtable"
! 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.DicomFindCallOperation'''.
|-
| 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.
|-
| queryLevel || optional || The Information Entity level. Is overwritten by the value of the GVBuffer property "DICOM_QUERY_LEVEL".
Admitted values:
- PATIENT
- STUDY
- SERIES
- INSTANCE
|-
| patientID || optional || The ID of the patient. Is overwritten by the value of the GVBuffer property "DICOM_PATIENT_ID".
|-
| patientName || optional || The Name of the patient. Is overwritten by the value of the GVBuffer property "DICOM_PATIENT_NAME".
|-
| patientSex || optional || The Sex of the patient. Is overwritten by the value of the GVBuffer property "DICOM_PATIENT_SEX".
|-
| 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
- Study Root Query/Retrieve Information Model - FIND 1.2.840.10008.5.1.4.1.2.2.1
- Modality Worklist Information Model - FIND 1.2.840.10008.5.1.4.31
- Patient/Study Only Query/Retrieve Information Model - FIND 1.2.840.10008.5.1.4.1.2.3.1
|-
| sopInstanceUID || optional || Is overwritten by the value of the GVBuffer property "DICOM_SOP_INSTANCE_UID".
|-
| studyInstanceUID || optional || Is overwritten by the value of the GVBuffer property "DICOM_STUDY_INSTANCE_UID".
|-
| seriesInstanceUID || optional || Is overwritten by the value of the GVBuffer property "DICOM_SERIES_INSTANCE_UID".
|-
| affectedSopClassUID || optional || Is overwritten by the value of the GVBuffer property "DICOM_AFFECTED_SOP_CLASS_UID".
|-
| affectedSopInstanceUID || optional || Is overwritten by the value of the GVBuffer property "DICOM_AFFECTED_SOP_INSTANCE_UID".
|-
| modalityStudy || optional || Is overwritten by the value of the GVBuffer property "DICOM_MODALITY_STUDY".
|}

Move

2015-07-14T14:10:01Z

M.sutera:

==Description==
Move service is the operation for the transfer of a DICOM object. The service establishes an association between the client that invoked it and the provider to which the call is intended; the service provides unique key values to identify the object to be transferred; the provider generates the sub-operations [[Store]] for each identified object to be transferred; when the number of sub- operations [[Store]] reaches zero the provider generate and send a state response of success ( Success). The sub-operations [[Store]] occur on a different association than that of the Move .

=={{GVESB}} Configuration==
The dicom-move-call Element is used by [[Channel]] and [[routed-call]]. It has the attributes:
{|class="gvtable"
! 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.DicomMoveCallOperation'''.
|-
| 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.
|-
| queryLevel || optional || The Information Entity level. Is overwritten by the value of the GVBuffer property "DICOM_QUERY_LEVEL".
Admitted values:
- PATIENT
- STUDY
- SERIES
- INSTANCE
|-
| patientID || optional || The ID of the patient. Is overwritten by the value of the GVBuffer property "DICOM_PATIENT_ID".
|-
| patientName || optional || The Name of the patient. Is overwritten by the value of the GVBuffer property "DICOM_PATIENT_NAME".
|-
| 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
- Study Root Query/Retrieve Information Model - FIND 1.2.840.10008.5.1.4.1.2.2.1
- Modality Worklist Information Model - FIND 1.2.840.10008.5.1.4.31
- Patient/Study Only Query/Retrieve Information Model - FIND 1.2.840.10008.5.1.4.1.2.3.1
|-
| sopClassUID || optional ||
|-
| studyInstanceUID || optional ||
|-
| seriesInstanceUID || optional ||
|}

Store

2015-07-14T14:09:57Z

M.sutera:

Store

2015-07-14T14:08:51Z

M.sutera:

Move

2015-07-14T14:08:47Z

M.sutera:

==Description==
Move service is the operation for the transfer of a DICOM object. The service establishes an association between the client that invoked it and the provider to which the call is intended; the service provides unique key values to identify the object to be transferred; the provider generates the sub-operations [[Store]] for each identified object to be transferred; when the number of sub- operations [[Store]] reaches zero the provider generate and send a state response of success ( Success). The sub-operations [[Store]] occur on a different association than that of the Move .

=={{GVESB}} Configuration==
The dicom-move-call Element is used by [[Channel]] and [[routed-call]]. It has the attributes:
{|class="gvtable"
! 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.DicomMoveCallOperation'''.
|-
| 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.
|-
| queryLevel || optional || The Information Entity level. Is overwritten by the value of the GVBuffer property "DICOM_QUERY_LEVEL".
Admitted values:
- PATIENT
- STUDY
- SERIES
- INSTANCE
|-
| patientID || optional || The ID of the patient. Is overwritten by the value of the GVBuffer property "DICOM_PATIENT_ID".
|-
| patientName || optional || The Name of the patient. Is overwritten by the value of the GVBuffer property "DICOM_PATIENT_NAME".
|-
| sopClass || optional ||
|-
| sopClassUID || optional ||
|-
| studyInstanceUID || optional ||
|-
| seriesInstanceUID || optional ||
|}

Find

2015-07-14T14:08:43Z

M.sutera:

==Description==
Find service establishes an association between the client that invoked it and the provider to which the call is intended; the service requires the provider to make a match with all specified keys in the identifier of request; the provider generates a response Find for each match and displays all key fields and attributes known required. When the process is completed response is generated and sent a reply Find with a state of success ( Success). Refusal or failure to reply indicates that the provider is unable to process the request.

=={{GVESB}} Configuration==
The dicom-find-call Element is used by [[Channel]] and [[routed-call]]. It has the attributes:
{|class="gvtable"
! 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.DicomFindCallOperation'''.
|-
| 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.
|-
| queryLevel || optional || The Information Entity level. Is overwritten by the value of the GVBuffer property "DICOM_QUERY_LEVEL".
Admitted values:
- PATIENT
- STUDY
- SERIES
- INSTANCE
|-
| patientID || optional || The ID of the patient. Is overwritten by the value of the GVBuffer property "DICOM_PATIENT_ID".
|-
| patientName || optional || The Name of the patient. Is overwritten by the value of the GVBuffer property "DICOM_PATIENT_NAME".
|-
| patientSex || optional || The Sex of the patient. Is overwritten by the value of the GVBuffer property "DICOM_PATIENT_SEX".
|-
| 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
- Study Root Query/Retrieve Information Model - FIND 1.2.840.10008.5.1.4.1.2.2.1
- Modality Worklist Information Model - FIND 1.2.840.10008.5.1.4.31
- Patient/Study Only Query/Retrieve Information Model - FIND 1.2.840.10008.5.1.4.1.2.3.1
|-
| sopInstanceUID || optional ||
|-
| studyInstanceUID || optional ||
|-
| seriesInstanceUID || optional ||
|-
| affectedSopClassUID || optional ||
|-
| affectedSopInstanceUID || optional ||
|-
| modalityStudy || optional ||
|}

Echo

2015-07-14T13:26:21Z

M.sutera:

==Description==
Echo service establishes an association between the client that invoked it and the provider that the call is intended. Its function is to verify the success or failure of the association by means of messages ( success or failure ) sent from the provider to the client.

=={{GVESB}} Configuration==
The dicom-echo-call Element is used by [[Channel]] and [[routed-call]]. It has the attributes:
{|class="gvtable"
! 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.DicomEchoCallOperation'''.
|-
| 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.
|}

Store

2015-07-14T13:16:45Z

M.sutera:

Find

2015-07-14T13:16:07Z

M.sutera:

Move

2015-07-14T13:13:58Z

M.sutera:

Move

2015-07-14T12:53:23Z

M.sutera:

Store

2015-07-14T10:39:39Z

M.sutera:

Echo

2015-07-14T10:23:00Z

M.sutera: /* Description */

==Description==
Echo service establishes an association between the client that invoked it and the provider that the call is intended. Its function is to verify the success or failure of the association by means of messages ( success or failure ) sent from the provider to the client.

=={{GVESB}} Configuration==
The dicom-echo-call Element is used by [[Channel]] and [[routed-call]]. It has the attributes:
{|class="gvtable"
! 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.DicomEchoCallOperation'''.
|-
| 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.
|}

Find

2015-07-14T10:22:41Z

M.sutera: /* Description */

Find

2015-07-14T10:21:00Z

M.sutera: /* {{GVESB}} Configuration */

==Description==
Service Find establishes an association between the client that invoked it and the provider to which the call is intended; the service requires the provider to make a match with all specified keys in the identifier of request; the provider generates a response Find for each match and displays all key fields and attributes known required. When the process is completed response is generated and sent a reply Find with a state of success ( Success). Refusal or failure to reply indicates that the provider is unable to process the request.

=={{GVESB}} Configuration==
The dicom-find-call Element is used by [[Channel]] and [[routed-call]]. It has the attributes:
{|class="gvtable"
! 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.DicomFindCallOperation'''.
|-
| 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.
|-
| queryLevel || implied ||
|-
| patientID || implied ||
|-
| patientName || implied ||
|-
| patientSex || implied ||
|-
| sopClass || implied ||
|-
| sopInstanceUID || implied ||
|-
| studyInstanceUID || implied ||
|-
| seriesInstanceUID || implied ||
|-
| affectedSopClassUID || implied ||
|-
| affectedSopInstanceUID || implied ||
|-
| modalityStudy || implied ||
|}

Find

2015-07-14T10:03:08Z

M.sutera:

==Description==
Service Find establishes an association between the client that invoked it and the provider to which the call is intended; the service requires the provider to make a match with all specified keys in the identifier of request; the provider generates a response Find for each match and displays all key fields and attributes known required. When the process is completed response is generated and sent a reply Find with a state of success ( Success). Refusal or failure to reply indicates that the provider is unable to process the request.

=={{GVESB}} Configuration==
The dicom-find-call Element is used by [[Channel]] and [[routed-call]]. It has the attributes:
{|class="gvtable"
! 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.DicomFindCallOperation'''.
|-
| 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.
|-
| queryLevel || optional ||
|-
| patientID || optional ||
|-
| patientName || optional ||
|-
| patientSex || optional ||
|-
| sopClass || optional ||
|-
| sopInstanceUID || optional ||
|-
| studyInstanceUID || optional ||
|-
| seriesInstanceUID || optional ||
|-
| affectedSopClassUID || optional ||
|-
| affectedSopInstanceUID || optional ||
|-
| modalityStudy || optional ||
|}

Echo

2015-07-14T09:20:55Z

M.sutera: /* {{GVESB}} Configuration */

==Description==
Service Echo establishes an association between the client that invoked it and the provider that the call is intended. Its function is to verify the success or failure of the association by means of messages ( success or failure ) sent from the provider to the client.

=={{GVESB}} Configuration==
The dicom-echo-call Element is used by [[Channel]] and [[routed-call]]. It has the attributes:
{|class="gvtable"
! 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.DicomEchoCallOperation'''.
|-
| 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.
|}

Echo

2015-07-14T09:14:11Z

M.sutera:

==Description==
Service Echo establishes an association between the client that invoked it and the provider that the call is intended. Its function is to verify the success or failure of the association by means of messages ( success or failure ) sent from the provider to the client.

=={{GVESB}} Configuration==
The dicom-echo-call Element is used by [[Channel]] and [[routed-call]]. It has the attributes:
{|class="gvtable"
! 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.DicomEchoCallOperation'''.
|-
| 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''' through manual configuration or through the property ''' DICOM_ASSOCIATION '''.
|}

DICOM

2015-07-14T09:08:12Z

M.sutera: /* DICOM Connector */

==Overview==
[http://dicom.nema.org/ DICOM] - Digital Imaging and Communications in Medicine - is the international standard for medical images and related information (ISO 12052). It defines the formats for medical images that can be exchanged with the data and quality necessary for clinical use. DICOM is implemented in almost every radiology, cardiology imaging, and radiotherapy device (X-ray, CT, MRI, ultrasound, etc.), and increasingly in devices in other medical domains such as ophthalmology and dentistry. From the emergency department, to cardiac stress testing, to breast cancer detection, DICOM is the standard that makes medical imaging work — for doctors and for patients.

==Data Format==
DICOM differs from some, but not all, data formats in that it groups information into data sets. That means that a file of a chest x-ray image, for example, actually contains the patient ID within the file, so that the image can never be separated from this information by mistake. This is similar to the way that image formats such as JPEG can also have embedded tags to identify and otherwise describe the image.

A DICOM data object consists of a number of attributes, including items such as name, ID, etc., and also one special attribute containing the image pixel data (i.e. logically, the main object has no "header" as such: merely a list of attributes, including the pixel data). A single DICOM object can have only one attribute containing pixel data. For many modalities, this corresponds to a single image. But note that the attribute may contain multiple "frames", allowing storage of cine loops or other multi-frame data.

DICOM uses three different Data Element encoding schemes. With Explicit Value Representation (VR) Data Elements, for VRs that are not OB, OW, OF, SQ, UT, or UN, the format for each Data Element is: GROUP (2 bytes) ELEMENT (2 bytes) VR (2 bytes) LengthInByte (2 bytes) Data (variable length).

==DICOM Connector==
The {{GVESB}} DICOM connector enables the operations that can be performed on a DICOM object.
The use of the connector joint with the peculiarities of the {{GVESB}} [[Virtual Layer]] allows the management of DICOM applications in a simple and efficient way, separating the logic of the process implementation from the specific management of the messages and their structure, independently from the DICOM standard used.
Basically the connector allows the virtualization of the input/output operations to a DICOM application, making available to the service definition process the interfaces able to hide all the technical details related to DICOM standard.

The Outbound DICOM Connector allows association verification and research,acquisition and storage of DICOM objects on PACS systems in the network.

The Inbound DICOM Connector allows to choose which services accept , provides answers about the status of the association between the system and the system questioner and retrieval of images between them.

== Outbound DICOM Connector==
The DICOM services implemented by the outbound connector are :
* [[Echo]]
* [[Find]]
* [[Move]]
* [[Store]]

== Inbound DICOM Connector==
The DICOM services implemented by the inbound connector are :
* [[Echo]]
* [[Store]]

Move

2015-07-14T09:04:17Z

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

==Description==

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

Store

2015-07-14T09:04:13Z

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

==Description==

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

Find

2015-07-14T09:01:51Z

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

==Description==

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

DICOM

2015-07-14T09:00:10Z

M.sutera:

==Overview==
[http://dicom.nema.org/ DICOM] - Digital Imaging and Communications in Medicine - is the international standard for medical images and related information (ISO 12052). It defines the formats for medical images that can be exchanged with the data and quality necessary for clinical use. DICOM is implemented in almost every radiology, cardiology imaging, and radiotherapy device (X-ray, CT, MRI, ultrasound, etc.), and increasingly in devices in other medical domains such as ophthalmology and dentistry. From the emergency department, to cardiac stress testing, to breast cancer detection, DICOM is the standard that makes medical imaging work — for doctors and for patients.

==Data Format==
DICOM differs from some, but not all, data formats in that it groups information into data sets. That means that a file of a chest x-ray image, for example, actually contains the patient ID within the file, so that the image can never be separated from this information by mistake. This is similar to the way that image formats such as JPEG can also have embedded tags to identify and otherwise describe the image.

A DICOM data object consists of a number of attributes, including items such as name, ID, etc., and also one special attribute containing the image pixel data (i.e. logically, the main object has no "header" as such: merely a list of attributes, including the pixel data). A single DICOM object can have only one attribute containing pixel data. For many modalities, this corresponds to a single image. But note that the attribute may contain multiple "frames", allowing storage of cine loops or other multi-frame data.

DICOM uses three different Data Element encoding schemes. With Explicit Value Representation (VR) Data Elements, for VRs that are not OB, OW, OF, SQ, UT, or UN, the format for each Data Element is: GROUP (2 bytes) ELEMENT (2 bytes) VR (2 bytes) LengthInByte (2 bytes) Data (variable length).

==DICOM Connector==
The {{GVESB}} DICOM connector enables the operations that can be performed on a DICOM object.
The use of the connector joint with the peculiarities of the {{GVESB}} [[Virtual Layer]] allows the management of DICOM applications in a simple and efficient way, separating the logic of the process implementation from the specific management of the messages and their structure, independently from the DICOM standard used.
Basically the connector allows the virtualization of the input/output operations to a DICOM application, making available to the service definition process the interfaces able to hide all the technical details related to DICOM standard.
The Outbound DICOM Connector allows association verification and research,acquisition and storage of DICOM objects on PACS systems in the network.
The Inbound DICOM Connector allows to choose which services accept , provides answers about the status of the association between the system and the system questioner and retrieval of images between them.

== Outbound DICOM Connector==
The DICOM services implemented by the outbound connector are :
* [[Echo]]
* [[Find]]
* [[Move]]
* [[Store]]

== Inbound DICOM Connector==
The DICOM services implemented by the inbound connector are :
* [[Echo]]
* [[Store]]

DICOM

2015-07-13T16:05:40Z

M.sutera:

==Overview==
[http://dicom.nema.org/ DICOM] - Digital Imaging and Communications in Medicine - is the international standard for medical images and related information (ISO 12052). It defines the formats for medical images that can be exchanged with the data and quality necessary for clinical use. DICOM is implemented in almost every radiology, cardiology imaging, and radiotherapy device (X-ray, CT, MRI, ultrasound, etc.), and increasingly in devices in other medical domains such as ophthalmology and dentistry. From the emergency department, to cardiac stress testing, to breast cancer detection, DICOM is the standard that makes medical imaging work — for doctors and for patients.

==Data Format==
DICOM differs from some, but not all, data formats in that it groups information into data sets. That means that a file of a chest x-ray image, for example, actually contains the patient ID within the file, so that the image can never be separated from this information by mistake. This is similar to the way that image formats such as JPEG can also have embedded tags to identify and otherwise describe the image.

A DICOM data object consists of a number of attributes, including items such as name, ID, etc., and also one special attribute containing the image pixel data (i.e. logically, the main object has no "header" as such: merely a list of attributes, including the pixel data). A single DICOM object can have only one attribute containing pixel data. For many modalities, this corresponds to a single image. But note that the attribute may contain multiple "frames", allowing storage of cine loops or other multi-frame data.

DICOM uses three different Data Element encoding schemes. With Explicit Value Representation (VR) Data Elements, for VRs that are not OB, OW, OF, SQ, UT, or UN, the format for each Data Element is: GROUP (2 bytes) ELEMENT (2 bytes) VR (2 bytes) LengthInByte (2 bytes) Data (variable length).

==DICOM Connector==
The {{GVESB}} DICOM connector enables the operations that can be performed on a DICOM object.
The use of the connector joint with the peculiarities of the {{GVESB}} [[Virtual Layer]] allows the management of DICOM applications in a simple and efficient way, separating the logic of the process implementation from the specific management of the messages and their structure, independently from the DICOM standard used.
Basically the connector allows the virtualization of the input/output operations to a DICOM application, making available to the service definition process the interfaces able to hide all the technical details related to DICOM standard.

== Outbound DICOM Connector==
The DICOM services implemented by the outbound connector are :
* [[Echo]]
* Find
* Move
* Store

== Inbound DICOM Connector==
The DICOM services implemented by the inbound connector are :
*[[Echo]]
* Store

DICOM

2015-07-13T15:34:02Z

M.sutera:

==Overview==
[http://dicom.nema.org/ DICOM] - Digital Imaging and Communications in Medicine - is the international standard for medical images and related information (ISO 12052). It defines the formats for medical images that can be exchanged with the data and quality necessary for clinical use. DICOM is implemented in almost every radiology, cardiology imaging, and radiotherapy device (X-ray, CT, MRI, ultrasound, etc.), and increasingly in devices in other medical domains such as ophthalmology and dentistry. From the emergency department, to cardiac stress testing, to breast cancer detection, DICOM is the standard that makes medical imaging work — for doctors and for patients.

==Data Format==
DICOM differs from some, but not all, data formats in that it groups information into data sets. That means that a file of a chest x-ray image, for example, actually contains the patient ID within the file, so that the image can never be separated from this information by mistake. This is similar to the way that image formats such as JPEG can also have embedded tags to identify and otherwise describe the image.

A DICOM data object consists of a number of attributes, including items such as name, ID, etc., and also one special attribute containing the image pixel data (i.e. logically, the main object has no "header" as such: merely a list of attributes, including the pixel data). A single DICOM object can have only one attribute containing pixel data. For many modalities, this corresponds to a single image. But note that the attribute may contain multiple "frames", allowing storage of cine loops or other multi-frame data.

DICOM uses three different Data Element encoding schemes. With Explicit Value Representation (VR) Data Elements, for VRs that are not OB, OW, OF, SQ, UT, or UN, the format for each Data Element is: GROUP (2 bytes) ELEMENT (2 bytes) VR (2 bytes) LengthInByte (2 bytes) Data (variable length).

==DICOM Connector==
The {{GVESB}} DICOM connector enables the operations that can be performed on a DICOM object.
The use of the connector joint with the peculiarities of the {{GVESB}} [[Virtual Layer]] allows the management of DICOM applications in a simple and efficient way, separating the logic of the process implementation from the specific management of the messages and their structure, independently from the DICOM standard used.
Basically the connector allows the virtualization of the input/output operations to a DICOM application, making available to the service definition process the interfaces able to hide all the technical details related to DICOM standard.

== Outbound DICOM Connector==
The DICOM services implemented by the connector are :
* [[Echo]]
* Find
* Move
* Store

== Inbound DICOM Connector==

Echo

2015-07-13T14:54:58Z

M.sutera: Created page with "==Description== Service Echo establishes an association between the client that invoked it and the provider that the call is intended. Its function is to verify the success or fa..."