Difference between revisions of "The DICOM Service Configurator"
| Line 1: | Line 1: | ||
The DICOM Service Configurator provides a user interface for setting the parameters in the <b>trial.xml</b> file. It also provides access to the DICOM Anonymizer Configurator. The DICOM Service Configurator is accessed by clicking the <b>Update Configuration</b> button in the <b>DICOM Service</b> column on the storage service's admin page. | The DICOM Service Configurator provides a user interface for setting the parameters in the <b>trial.xml</b> file. It also provides access to the DICOM Anonymizer Configurator. The DICOM Service Configurator is accessed by clicking the <b>Update Configuration</b> button in the <b>DICOM Service</b> column on the storage service's admin page. | ||
| − | ==Top-level | + | ==Top-level Parameters== |
[[Image:DicomConfig1.JPG|frame|]] | [[Image:DicomConfig1.JPG|frame|]] | ||
At the top of the DICOM Service Configurator window is a small table containing parameters that are apply to all the components of the DICOM Service. | At the top of the DICOM Service Configurator window is a small table containing parameters that are apply to all the components of the DICOM Service. | ||
| Line 7: | Line 7: | ||
If you want the DICOM Service to start automatically whenever the MIRC site is started, set the <b>Autostart</b> value to <b>yes</b>. | If you want the DICOM Service to start automatically whenever the MIRC site is started, set the <b>Autostart</b> value to <b>yes</b>. | ||
| − | If you | + | If you want all transmissions to be logged in the <b>trial/logs</b> directory under the root of the storage service, set the <b>Log</b> value to <b>yes</b>. Some trials require logs of all transmissions, so carefully consider this choice. The log is a comma-separated values file which can be opened with a spreadsheet program. If you are operating this DICOM service as an automatic teaching file generator, you probably should set this parameter to <b>no</b>. |
If you want duplicate images (images with the same SOP Instance UIDs) to update previous versions, making the last image received the only one stored and referenced in the MIRCdocument, set the <b>Allow overwrite</b> value to <b>yes</b>. This is the way most trials are operated. If you want all images, even ones with duplicate SOP Instance UIDs, to be saved and referenced, set the value to <b>no</b>. | If you want duplicate images (images with the same SOP Instance UIDs) to update previous versions, making the last image received the only one stored and referenced in the MIRCdocument, set the <b>Allow overwrite</b> value to <b>yes</b>. This is the way most trials are operated. If you want all images, even ones with duplicate SOP Instance UIDs, to be saved and referenced, set the value to <b>no</b>. | ||
| − | ==Central Remapper | + | ==Central Remapper== |
[[Image:DicomConfig2.JPG|frame|]] | [[Image:DicomConfig2.JPG|frame|]] | ||
| + | In trials which use the central remapping feature of the DICOM Service and the FieldCenter application, the parameters are configured in the second table on the page. The remapper, whether local or central, uses a cipher to encrypt the PHI which is stored in its database. The remapper has a default encryption key which is normally used when the network on which the MIRC site is run is secure. This only provides security against casual access to the data. To use the default key, blank the <b>External key file</b> field. To specify a separate key and secure it against access, the absolute path (e.g., <b>X:\keyfile.storage</b>) to a key file is inserted in the field as described in [[The Remapper Key]]. | ||
| − | ==DICOM Import Service | + | The <b>UID root</b> field specifies the UID root to be assigned to all remapped UIDs by the <b>uid</b> anonymizer function of the FieldCenter application that calls the central remapper. |
| + | |||
| + | The <b>Base date</b> field specifies the base date to be used in the <b>offsetdate</b> function. | ||
| + | |||
| + | The last four parameters of the table specify the parameters to be used in the <b?ptid</b> function. | ||
| + | |||
| + | ==DICOM Import Service== | ||
[[Image:DicomConfig3.JPG|frame|]] | [[Image:DicomConfig3.JPG|frame|]] | ||
| − | ==Dicom Export Service | + | ==Dicom Export Service== |
[[Image:DicomConfig4.JPG|frame|]] | [[Image:DicomConfig4.JPG|frame|]] | ||
| − | ==HTTP Import Service | + | ==HTTP Import Service== |
[[Image:DicomConfig5.JPG|frame|]] | [[Image:DicomConfig5.JPG|frame|]] | ||
| − | ==HTTP Export Service | + | ==HTTP Export Service== |
[[Image:DicomConfig6.JPG|frame|]] | [[Image:DicomConfig6.JPG|frame|]] | ||
| − | ==Database Export Service | + | ==Database Export Service== |
[[Image:DicomConfig7.JPG|frame|]] | [[Image:DicomConfig7.JPG|frame|]] | ||
Revision as of 19:19, 30 August 2006
The DICOM Service Configurator provides a user interface for setting the parameters in the trial.xml file. It also provides access to the DICOM Anonymizer Configurator. The DICOM Service Configurator is accessed by clicking the Update Configuration button in the DICOM Service column on the storage service's admin page.
1 Top-level Parameters
At the top of the DICOM Service Configurator window is a small table containing parameters that are apply to all the components of the DICOM Service.
If you want the DICOM Service to start automatically whenever the MIRC site is started, set the Autostart value to yes.
If you want all transmissions to be logged in the trial/logs directory under the root of the storage service, set the Log value to yes. Some trials require logs of all transmissions, so carefully consider this choice. The log is a comma-separated values file which can be opened with a spreadsheet program. If you are operating this DICOM service as an automatic teaching file generator, you probably should set this parameter to no.
If you want duplicate images (images with the same SOP Instance UIDs) to update previous versions, making the last image received the only one stored and referenced in the MIRCdocument, set the Allow overwrite value to yes. This is the way most trials are operated. If you want all images, even ones with duplicate SOP Instance UIDs, to be saved and referenced, set the value to no.
2 Central Remapper
In trials which use the central remapping feature of the DICOM Service and the FieldCenter application, the parameters are configured in the second table on the page. The remapper, whether local or central, uses a cipher to encrypt the PHI which is stored in its database. The remapper has a default encryption key which is normally used when the network on which the MIRC site is run is secure. This only provides security against casual access to the data. To use the default key, blank the External key file field. To specify a separate key and secure it against access, the absolute path (e.g., X:\keyfile.storage) to a key file is inserted in the field as described in The Remapper Key.
The UID root field specifies the UID root to be assigned to all remapped UIDs by the uid anonymizer function of the FieldCenter application that calls the central remapper.
The Base date field specifies the base date to be used in the offsetdate function.
The last four parameters of the table specify the parameters to be used in the <b?ptid function.