Product Update: Preserve Study Instance UIDs from Trusted DICOM Sources

Overview

OmegaAI now enables DICOM Stations to be marked as authoritative sources of study identity. When enabled, a study created from an HL7 order that receives images from an authoritative station will use the station's Study Instance UID (0020,000D) as the canonical identifier, replacing OmegaAI's placeholder UID. This resolves bidirectional workflow issues where annotations and reports sent back to source systems could not be matched due to UID mismatches.

What's New

1. Authoritative DICOM Station Setting

What changed:

• New toggle added to DICOM Station device configuration (Organization > Device > DICOM Station Features > Authoritative). Defaults to OFF for all new stations.

Benefit:

• Administrators can explicitly trust specific PACS and gateways as authoritative sources of study identity, enabling automatic reconciliation of annotations and reports sent back to the source system.

2. Study Instance UID Preservation and Coercion Warnings

What changed:

• When Authoritative is enabled and a source UID differs from OmegaAI's order-generated placeholder, the source UID becomes canonical. The placeholder UID is retained in a merged-UID reference table. A C-STORE Warning (0xB000) is returned to the sending system, and the object records an Original Attributes Sequence (0400,0561) with the original UID, modification datetime, modifying system, and COERCE reason code.

Benefit:

• UID changes are now transparent and auditable. All previous UIDs remain discoverable through QIDO-RS, WADO-RS, C-FIND, and C-MOVE. Existing external references (worklist IDs, prior queries, links in reports) that stored the old UID continue to work.

3. Per-Station Trust Configuration

What changed:

• Authoritative setting is configured per DICOM Station device, not globally. Each station is independently marked as trusted or untrusted.

Benefit:

• A single well-behaved gateway can be marked as authoritative without changing how any other station is treated. Gives administrators fine-grained control over which sources are trusted.

Important Notes

• Default Behavior: Authoritative is OFF by default for all DICOM Station devices, including newly created ones. No existing configurations change behavior on upgrade.

• When This Setting Takes Effect: The setting only takes effect when a study was created by an HL7 order (placeholder UID) and the DICOM object then matches it by accession. Where studies are created by the DICOM object itself, it never comes into play.

• Bidirectional Workflows Only: Enable Authoritative only for sources where you expect to send annotations, reports, or other derived content back to the source system and require automatic UID-based matching.

• DICOM Station vs Connection Setting: This is a DICOM Station setting, not a connection setting. Ingest reads the receiving station by AE Title, so each station is ticked separately.

• UI Is Not a Safety Boundary: A FHIR PUT /Device sets the value whether or not the toggle switch is visible in the UI.

• Supported Workflows: Re-sending the same study under a different UID is supported. Every superseded UID is kept as an alias, allowing external systems holding an older UID to resolve via the alias.

• Not Recommended For:

  • Sources with UIDs that aren't globally unique (reusing one UID across different studies mis-identifies studies)
  • Unidirectional workflows where there's no risk, just no benefit

• Testing Required: Before enabling Authoritative for a production PACS or gateway, test the bidirectional workflow (send and return annotations) in a non-production environment to verify correct reconciliation at the source.

• Configuration Examples:

  • CSH Compass PACS (Bidirectional Workflow): Navigate to Organization > Device > CSH Compass PACS > DICOM Station Features > Toggle Authoritative ON. Compass UIDs are now canonical; returned annotations carry the original UID and match automatically at CSH.

  • Ultrasound Modality (Unidirectional Workflow): Leave Authoritative OFF. OmegaAI uses the order-generated UID. If the ultrasound re-sends the same exam with a different UID, both sets of objects are stored under the order UID with no UID conflicts.

• DICOM Compliance:

  • C-STORE Warning (0xB000): Returned when Study Instance UID is coerced (per DICOM PS3.4 §B.4)

  • Original Attributes Sequence (0400,0561): Object records original UID, modification datetime, modifying system, and COERCE reason (per DICOM PS3.3 §C.12.1.1.9)

  • Benefits

    1. Bidirectional Reconciliation — Annotations and reports match at the source system without manual intervention or worklist reconciliation.

    2. No Data Loss — All superseded UIDs are retained in the merged-UID reference table and remain queryable and accessible through QIDO-RS, WADO-RS, C-FIND, and C-MOVE.

    3. Transparency and Auditability — C-STORE Warning (0xB000) is returned to the sending system and Original Attributes Sequence (0400,0561) records the original UID and reason code.

    4. Per-Station Configuration — Each DICOM Station is independently marked as trusted or untrusted. One gateway can be authoritative without affecting others.

    5. Safe by Default — OFF by default for all stations. No existing configurations change behavior on upgrade.

Where to Find It

Location in OmegaAI:

Organization
  └─ Device
      └─ [Select DICOM Station Device]
          └─ Device Details Form
              └─ DICOM Station Features
                  └─ Authoritative ← Toggle is here (last item)

Available On: DICOM Station devices only (not on OmegaAI Link or API devices)

Permission: Read-only when the Device form is in view mode; editable in edit mode, the same as every other field in the DICOM Station Features group. No separate permission applies to this field.

Programmatic access: Can be queried and set through the FHIR Device API (device.extension[where(url='authoritative')].valueBoolean)

Updated Help Articles

Preserve Study Instance UIDs from Trusted DICOM Sources