Creating Documents from a Federated Search - Medical Imaging Viewer - NilRead - English - Foundation 22.1 - OnBase

The DICOM Processor can create documents for all of the patient's existing studies in the external DICOM repository.

To configure the DICOM Processor to create documents for studies found using a federated search:

Configure the parameters for your DICOM integration under Medical | DICOM | Viewer Integration Settings.
Map the $$DICOMPATIENTID default value to the MPI number in the HL7 message template.
The HL7 DICOM Processor uses the MPI to find all of a patient's studies in the DICOM repository.
To store the study date as a Keyword Value on placeholder documents, do the following:
1. Create a Keyword Type to store study dates.
2. Map the Keyword Type to the DICOM - Study Date chart data field.¹
3. Assign the Keyword Type to the Document Type used to store DICOM study documents.
Configure the options for the DICOM Processor import process:
1. From the Document Type drop-down list, select the Document Type where DICOM study documents should be stored. All studies retrieved by the federated search will be stored under this Document Type.
2. From the DICOM Repository drop-down list, select the medical imaging viewer integration.
3. Select the Execute Federated Search option to use the MPI value in the $$DICOMPATIENTID field to locate and create documents for all of the patient's studies existing in the DICOM repository. This option requires the -HL7DICOMPROCESSOR command line switch.
  You can see which field is configured as the $$DICOMPATIENTID by checking the Message Template field settings | Patient ID field. This field is displayed when you select Execute Federated Search.
Run a client process with the -HL7DICOMPROCESSOR command line switch. This switch is required for performing the federated search and creating the placeholder documents.

¹ The DICOM - Study Date chart data field extracts study dates only from DICOM data retrieved through an HL7 federated search. This field does not extract study dates from HL7 message data, and it cannot be mapped to an HL7 message field.