DICOM Setup Tab
Covered by this topic
Digital Imaging and Communications in Medicine (DICOM) is a standard for handling, storing, printing, and exchanging image information in and between medical imaging software.
DICOM Setup Tab
Access to the Dicom Setup tab requires the DICOM Queue security permission. DICOM Queue security permission allows access to the DICOM Image Queue and all the settings that go with it.
The DICOM Setup tab is both a dashboard with search functionality, as well as a link to add or edit the Application Entities information. There is also a “basic” or “advanced” search capability at the top left corner of this screen to search for DICOM routes in the categories of the dashboard.
Application Entities Editor
Access to view and manage Application Entities requires the Application Entities Editor security permission. The Application Entities Editor security permission allows access to add, edit, or delete DICOM Application Entities, however this editor is mainly for MIE programming staff.
To view application entities, simply click the View Application Entities hyperlink in the DICOM Setup tab found within the Control Panel sidemenu.
To add an Application Entity, once in the Application Entities, simply select the Add Entity link.
The following information is displayed on the application entities screen:
- Title: Commonly referred to as “AE Title” or “Application Entity Title” - this is given to a superuser by the client or technical engineer who services the imaging device. This is a name assigned to that device and will be given to a superuser to input in this box. The AE title is required in order for a remote device to send images to the Enterprise Health application.
- Node: Commonly referred to as “IP Address” - this number sequence given to the superuser by the client or technical engineer who services the imaging device. This is a number assigned to an imaging device and the superuser will input this number in this box. The IP address is required in order for a remote device to send images to the Enterprise Health application.
- Port: This number will be either added by MIE or given to the superuser to complete this field from MIE. Port 104 is the standard port for DICOM communications. (Clients may need administrator access to use port 104.) This port field is required for configuration in order for successful transmission of images into
Enterprise Health
. Additional port number detail is listed below:
- 104 port for DICOM over TCP or UDP. Since 104 is in the reserved subset, many operating systems require special privileges to use it.
- 2761 registered port for DICOM using Integrated Secure Communication Layer (ISCL) over TCP or UDP.
- 2762 registered port for DICOM using Transport Layer Security (TLS) over TCP or UDP.
- 11112 registered port for DICOM using standard, open communication over TCP or UDP.
- Location Code: Select the appropriate location from where the device is located. A new location code may need to be set up in the Locations Manager chart tab.
- Patient Partition: If Enterprise Health is partitioned by location/group, then select the appropriate partition from where the imaging device is located. If there is only one partition (e.g., MR), then use this partition.
- Document Type: By default, incoming studies will be stored with a Document Type determined by that modality (i.e., an Ultrasound Device would have a document type of “US”). This setting allows you to override that document type.
- Route Level: MIE or the Superuser will select the type of routing level they want to transmit the images to the
Enterprise Health
system.
- None (N)
- Study (S)
- Series (E)
- Image (I)
- Max Connections: Sets the maximum number of threads 0 how many studies can be pushed at once.
- Comment: This is a freetext field where you can identify in simplistic terms what the device is.
- AE Ability: Push or Print are the options. You would only use “Print” if the device is a DICOM printer. If Push is selected, additional fields will branch open to program, if needed:
- Reconcile Patient Data on Push: Overwrites the DICOM elements of the demographics to match Enterprise Health . This is the opposite of Update DB from DICOM data. You can choose to do with just the MR only or NAME and MR.
- Reconcile Accession Number on Push: Uses the encounter ID or document ID - overwrites accession number.
- Priority: Depending on how quickly you want to push, you can bump a study to the top. If there are 50 studies in the queue, assign a higher level here to move study up to be read sooner.
- Compression: Three choices–None, Lossless (compress as much as possible without losing data), and Lossy + # (will lose data). Example: Lossy 90 means “only lose 10% of the quality”. This is an Image Quality setting. (Comparison to when you use a slider in JPG images for quality.) Compression affects the size of the file.
- Update DB from DICOM data: Takes DICOM data and updates the patient info demographics info. MR#
- Allow MWL Query: Check this box if the Modality Worklist integration is being set up between Enterprise Health and the device.
Enterprise Health Documentation
Last Updated:
Last Build:
Mon, 07 Oct 2024 21:17:39 UTC
WikiGDrive Version: 2aacb51f060d0354a678419290943a99bd16aad1