ConfigurationTopic number: 1673019723589

Improved patient data management with better handling of DICOM values

In the 8.2.1 release, the DICOM values for Patient Size and Patient Weight were, by default, replaced with the order-level values for these fields. However, if the order did not contain this information, the DICOM data was deleted. In 8.2.2, the defaults have been changed so that these DICOM fields are no longer overwritten.

Automatically fix studies using order-based identifiers to accommodate systems that require them

When an incoming study matches on patient ID and accession number, but not on study UID, Enterprise Imaging can now be configured to perform an auto-fix that assigns it the order-based study UID or the modality-based study UID.

Previously, modality-based study UIDs were always used when fixing study data. However, certain HIS/RIS do not support modality-generated study UIDs.

To accommodate these systems, administrators can configure Enterprise Imaging to apply order-based study UIDs instead. To ensure that auto-fixes are not applied too aggressively — for example, to studies still queued when an ORM update arrive — administrators can set whether Enterprise Imaging is allowed to perform automatic QC fixup, and if so, how long to wait before updating the study UID.

Enhanced fixup rules ensure that updated studies are accepted by strictly compliant DICOM systems

When updating study demographics to match procedure information from the RIS, Enterprise Imaging previously retained the study’s existing instance UID. External systems such as VNAs that are strictly compliant with the DICOM standard require that all instance UIDs be unique. They will therefore reject fixed studies with reused instance UIDs.

To better support strictly compliant systems, Enterprise Imaging can be configured to generate new instance UIDs for fixed studies. When so configured, IOCM incorrect modality worklist rejection notes are generated for the original study, rather than IOCM data retention expiry notes. Using these types of rejection notes ensures that DICOM compliant systems reject the original study and replace them with copies that have new instance and series UIDs.

Improved policy management for application FQDN

Enterprise Imaging authentication services can be exposed behind a separate FQDN allowing for a stricter policy towards the exposure of the application FQDN.

Audit Record Reports: Configurable instance level auditing now available in Administrator Desktop

System administrators can now choose to enable or disable instance-level auditing of DICOM object level events (DICOM Ingestion, Transfers, downloads, and so on) by using the Audit object (SOP UID) events checkbox. Disabling instance-level auditing (using only study-level auditing) significantly reduces the overall size of the Audit Record Repository (ARR) and is now the default setting for new installations. Historical data will not be impacted by this setting. You can enable instance-level auditing, if required. Audit Record Repository records can now be compressed to consume less space.

Note: Enabling instance-level auditing does not provide evidence that a user has viewed the instances — only that the instances were downloaded to the Enterprise Imaging desktop client.