Creating Documents for Externally Stored DICOM Studies - Integration for Medical Imaging Viewer (Vital Images) - English - Foundation 22.1 - OnBase - external

Integration for Medical Imaging Viewer (Vital Images)

Integration for Medical Imaging Viewer (Vital Images)
Foundation 22.1

The DICOM Processor creates placeholder documents representing studies stored in an external DICOM repository. Placeholder documents allow OnBase applications, such as the OnBase Patient Window, to display studies stored in external repositories. When a placeholder document is retrieved using the OnBase Patient Window, the associated study is retrieved from the external repository and displayed using the medical imaging viewer. The DICOM Processor requires an HL7 Listener license. It is not available under the Basic HL7 Listener license.

The DICOM Processor is configured in OnBase Configuration under Medical | HL7 | Import Process. For detailed information about configuring an HL7 import process, see the HL7 module reference guide.

To configure the DICOM Processor:

  1. Map the $$DICOMSTUDYID predefined default value to the HL7 message template.

    The DICOM Processor message action determines the uniqueness of a study by its study UID. Messages containing new study UIDs will result in the creation of new placeholder documents.


    The HL7 Listener will not create a placeholder document for a specific study if the study UID is missing.

  2. Configure the HL7 message template to index documents with the patient identification information necessary to attach documents to patient records or charts.
  3. If the message template needs to handle multiple DICOM studies, select the Enable to repeat setting for the message segment containing the studies. This setting is available in HL7 Segment Settings for the message segment.
    When a single HL7 message specifies multiple study UIDs, each study is stored as a separate placeholder document and indexed using the Keyword Values from the message. If each study document should have different Keyword Values, then the sending application needs to send a separate HL7 message for each study.
  4. Configure the following DICOM Processor options:
    • Document Type —Select the Document Type where this import process should store DICOM study documents.

      To archive DICOM studies to different Document Types based on modality, configure a separate DICOM import process and message template for each Document Type. Then, configure each message template to filter on the modality code field.

    • DICOM Repository —Select the server for the medical imaging viewer. Available servers are configured under Medical | DICOM | Viewer Integration Settings.


    The Execute Federated Search option displayed under the DICOM Repository drop-down list is not available for the integration with VitreaView.