Skip to main content

Preserve Study Instance UIDs From Trusted DICOM Sources

You can mark a DICOM station as a trusted, or authoritative, source of study identity. When a study receives images from an authoritative station, that station's Study Instance UID (Unique Identifier), DICOM tag (0020,000D), becomes the study's official identifier. It replaces the placeholder UID that OmegaAI created. OmegaAI keeps the replaced UIDs, so the study can still be found by them.

This matters most when you send annotations or reports back to the source system, because the source can then recognize the study.

Before You Begin​

  • Station type: The Authoritative setting is available on DICOM Station devices only. It isn't available on OmegaAI Link or API devices.
  • Default: The setting is off for every station, including new stations. Upgrading doesn't change any behavior.
  • Permission: No separate permission is needed. Anyone who can edit the station's other DICOM Station Features can change this setting. It's read-only until you click Edit.
  • Validate the source first: Turn on Authoritative only for sources you've tested and confirmed have stable, reliable UIDs.

What Problem This Solves​

When an HL7 (Health Level Seven) order arrives before the images, OmegaAI creates the study with a placeholder Study Instance UID. Later, the imaging source sends its images with its own UID. OmegaAI matches the images to the study by accession number, and stores them under the placeholder UID. Without the Authoritative setting, the source's UID is discarded silently.

As a result, annotations and reports sent back to the source carry a UID it doesn't recognize, so it can't match them.

Example: A source PACS (Picture Archiving and Communication System) sends UID 1.2.826.0.1.3680043..., but OmegaAI stores the study as 1.2.124.113540.... Annotations sent back to the source don't reconcile.

How The Setting Changes What Happens​

In both cases, the HL7 order creates the study with a placeholder UID, the imaging source sends objects with its own UID, and OmegaAI matches them by accession number. What happens next depends on the setting:

Authoritative off (default)Authoritative on
Source UIDDiscarded silently, with no warning.Adopted as the study's official identifier.
Placeholder UIDKept as the study's UID.Recorded in the merged-UID reference table.
SenderNo warning.Receives a C-STORE Warning (0xB000).
Object recordNo change.Records an Original Attributes Sequence (0400,0561) with the original UID, the modification date and time, the modifying system, and the COERCE reason code.
Finding the studyBy the placeholder UID.By any historical UID, in DICOMweb searches and retrievals (QIDO-RS and WADO-RS) and in DICOM queries and retrievals (C-FIND and C-MOVE).

Note: The setting takes effect only when a study was created by an HL7 order (with a placeholder UID) and a DICOM object then matches it by accession number. If the DICOM object itself creates the study, the setting never applies.

Turn On The Authoritative Setting​

  1. In the left navigation bar, click Organization.

  2. Select your organization, and then click Details.

  3. In the settings menu, click Device.

  4. In the Devices list, select the OmegaAI Link that the station is connected to. Its stations appear in the Stations list.

  5. In the Stations list, select the DICOM station.

  6. At the top right of the Device page, click Edit.

  7. In DICOM Station Features, turn on Authoritative.

    Tip: To see a short description of the setting, point to Authoritative. The tooltip explains what happens when it's on and off.

  8. At the top right of the page, click Save.

Expected result: From now on, when a study created by an HL7 order receives images from this station, the station's UID becomes the study's official identifier.

Note: This is a DICOM station setting, not a connection setting. OmegaAI identifies the receiving station by its AE (Application Entity) Title, so you turn on the setting for each station separately.

Note: A change can take up to 5 minutes to apply to newly received images.

Set It Through The FHIR Device API​

You can also read and set the setting through the FHIR (Fast Healthcare Interoperability Resources) Device API, at device.extension[where(url='authoritative')].valueBoolean.

Important: Hiding or locking the toggle in OmegaAI doesn't protect the setting. A FHIR PUT /Device request changes the value whether or not the toggle is visible.

When To Turn It On​

Turn it on forLeave it off for
DICOM gateways and enterprise PACS with stable UIDsSources with unstable or ad hoc identifiers
Bidirectional workflows, where annotations or reports are sent backSources with UIDs that aren't globally unique (reusing one UID across different studies misidentifies studies)
Sources with reliable UIDs that are never regenerated

You don't need the setting for one-way workflows, where studies only flow into OmegaAI. There's no risk in turning it on, but there's also no benefit.

Examples​

  • Enterprise PACS (bidirectional): Turn on Authoritative. The PACS UIDs become the official identifiers, and annotations sent back carry the original UID.
  • Ultrasound modality (one-way): Leave Authoritative off. OmegaAI uses the UID created from the order, and re-sends don't cause conflicts.

Benefits​

  • Bidirectional reconciliation: Annotations match at the source automatically.
  • No information loss: All replaced UIDs can still be found.
  • Transparency and auditability: The C-STORE Warning and the Original Attributes Sequence record every change.
  • Per station: One gateway can be authoritative without affecting other stations.
  • Safe by default: The setting is off by default, so upgrading doesn't change behavior.

DICOM Compliance​

  • C-STORE Warning (0xB000): Returned when the Study Instance UID is coerced, per DICOM PS3.4 §B.4.
  • Original Attributes Sequence (0400,0561): The object records the original UID, the modification date and time, the modifying system, and the COERCE reason, per DICOM PS3.3 §C.12.1.1.9.

Troubleshooting​

ProblemWhat to check
Annotations don't match at the sourceCheck that Authoritative is turned on for the station. Check the OmegaAI Link logs. Search for the source UID in Global Search.
The C-STORE Warning isn't receivedCheck that Authoritative is turned on. Check that the source PACS supports warning responses; some older systems suppress them. Look for the warning in the OmegaAI ingestion logs.
Historical UIDs can't be foundCheck that Authoritative is turned on for the station. Search for the historical UID in Global Search. If the problem continues, contact RamSoft Support.