IMPAX 6.5.1 Server Knowledge Base home > Archive Server home > Configuring a PACS Archive Provider (PAP)

Completing the PAP configuration

Perform this task after configuring a source to send to the PAP components and, if required, configuring remote destinations that send back from multiple AE titles.

Some sites may want to have their studies mirrored at another site through a PACS Archive Provider (PAP) which uses PACS Store and Remember archiving. (When configuring a PACS for mirroring using PACS Store and Remember archiving, each PACS is set up with another local archive besides the PACS Store and Remember archive.) This mirroring protects against loss of data and allows studies at one PACS to be viewed at another. This can be achieved effectively using a PAP.

A PAP can parse the private tags of the incoming DICOM objects to determine the objects’ HIS verification and study status. This eliminates the need to HIS verify a study a second time or to add the incoming study to a radiologist’s worklist. If the status is not part of the private tags (which occurs with older versions of an SCU), the status is set to the configured value; the default is Dictated.

The high-level tasks for completing the PAP configuration are as follows:

  1. Disable HIS verification.

  2. Change the PAP so that it routes incoming studies for all PAPs in the cluster.

  3. Change the study status from the default 'D'.

    Details on how to perform each step follow.

Note:

Note:

As with any database change, signal the process that the database has been updated. In CLUI, type: signal database_updated 0 MVF_PAP. Or, stop and restart the affected process.

By default, the PAP is configured to perform HIS verification.

To disable HIS verification

  1. Launch CLUI.

  2. To update all PAPs in that cluster to disable HIS verification, type

    update mvf_scp_service set verify_incoming_data='F' where service_ref in (select service_ref from map_implements mi , map_process mp where mi.process_ref=mp.process_ref and mp.process_title='MVF_PAP')

    or

    If only certain PAPs need HIS verification disabled, determine the ae_refs of the PAPs to be updated and, for each ae_ref, type

    update mvf_scp_service set verify_incoming_data='F' where service_ref in (select ms.service_ref from map_implements mi , map_process mp, map_service ms where mi.process_ref=mp.process_ref and mp.process_title='MVF_PAP' and ms.service_ref = mi.service_ref and ms.ae_ref = ae_ref )

By default, the PAP is configured to not route incoming studies.

To change the PAP so that it routes incoming studies

  1. Launch CLUI.

  2. To update all PAPs in that cluster to route incoming studies, type

    update mvf_scp_service set route_incoming_data='T' where service_ref in (select service_ref from map_implements mi , map_process mp where mi.process_ref=mp.process_ref and mp.process_title='MVF_PAP')

    or

    If only certain PAPs need to route incoming studies, determine the ae_refs of the PAPs to be updated and, for each ae_ref, type

    update mvf_scp_service set route_incoming_data='T' where service_ref in (select ms.service_ref from map_implements mi , map_process mp, map_service ms where mi.process_ref=mp.process_ref and mp.process_title='MVF_PAP' and ms.service_ref = mi.service_ref and ms.ae_ref = ae_ref )

By default, the PAP is configured to set the study status to 'D' (Dictated) if the incoming DICOM objects do not have the study status as part of the private tags.

To change the study status from the default 'D'

  1. Launch CLUI.

  2. Type

    select * from map_ini where ini_section = 'MVF_PAP'

  3. If the ini_key = 'DEFAULT_STUDY_STATUS' exists, type

    update map_ini set ini_value = 'x' where ini_section = 'MVF_PAP' and ini_key = 'DEFAULT_STUDY_STATUS'

    or

    If the ini_key = 'DEFAULT_STUDY_STATUS' does not exist, type

    insert into map_ini (ini_section, ini_key, ini_value) values ('MVF_PAP', 'DEFAULT_STUDY_STATUS', 'study_status')

    where study_status is the status set for incoming objects without a study status as part of their private tags.


Required permissions


See also


Topic number: 67520

Applies to: IMPAX 6.5.1 Server Knowledge Base