ORM^O01 problem in 5.34.1

[toufic...@gmail.com]

Dears,

I am sending this HL7 format:
MSH|^~\&|Sender_HIS|Client_NAME|RIS|Client_NAME|20251026015800||ORM^O01|d67a3113-387c-4200-8ba3-9d6032a2ebd9|P|2.5.1
PID|1||830108^^^URIS||Sxaaxcdecxcdien^Ayxccbvvcba Akrvccvbvcbam^||20001221|F|||||~^NET^Internet^te...@google.com|||S|
PV1||E||U||||^ER  Physician||0|||||||||EMR77949|||||||||||||||||||||||||20251026033233||||||
ORC|NW|1707306|||SC||^^^20251026035700||20251026035700|||||||||LX16|||||||||||||
OBR||1707306||^^^4201^Neck CT Scan^Local||||||||||||||CT10258|1707306|||||CT|||||||^EFFECTIVE DATE: 2025/10/26 03:57:00 - REMARKS: er - INDICATION: null|||||||||||||4201^Neck CT Scan^Local

it is working normally in 5.31.2, but for 5.34.1 it is creating the Patient, but no MWL procedure is created. It is showing this on the Logs:

2025-10-26 08:10:06,001 INFO  [org.dcm4che3.net.Connection] (EE-ManagedExecutorService-default-Thread-1) Accept connection Socket[addr=/172.19.0.14,port=43138,localport=2575]
2025-10-26 08:10:06,001 INFO  [org.dcm4che3.hl7.MLLPConnection] (EE-ManagedExecutorService-default-Thread-5394) Socket[addr=/172.19.0.14,port=43138,localport=2575] >> MSH|^~\&|RIS|HOSP|DCM4CHEE|ARCHIVE|20251026||ORM^O01|MSG0001|P|2.5
2025-10-26 08:10:06,007 INFO  [org.dcm4chee.arc.patient.impl.PatientServiceEJB] (EE-ManagedExecutorService-default-Thread-5394) Socket[addr=/172.19.0.14,port=43138,localport=2575]: Create Patient[pk=11, id=[123456^^^HOSP], name=Doe^John]
2025-10-26 08:10:06,012 INFO  [org.dcm4chee.arc.patient.impl.PatientServiceEJB] (EE-ManagedExecutorService-default-Thread-5394) No duplicate record with equal Patient ID found Patient[pk=11, id=[123456^^^HOSP], name=Doe^John]
2025-10-26 08:10:06,013 INFO  [org.dcm4chee.arc.hl7.ProcedureUpdateService] (EE-ManagedExecutorService-default-Thread-5394) Update procedure for message type ORM^O01
2025-10-26 08:10:06,013 INFO  [org.dcm4chee.arc.hl7.ProcedureUpdateService] (EE-ManagedExecutorService-default-Thread-5394) StudyInstanceUID missing in HL7 order message ORM^O01

Please let me know what is wrong!

[toufic...@gmail.com]

Dears,

Any feedback on this problem??

[Stephen Douglas Scotti]

Maybe the behavior regarding StudyInstanceUID has changed ?  You are not the only one:  https://groups.google.com/g/dcm4che/c/wvnvUYF9ou8/m/N6uw1OaoAQAJ

Like a ZDS segment ?  ZDS|1|1.2.826.0.1.3680043.10.511.1.20251026035700.1 if you create them ahead of time, or another method to trigger the UID creation in dcm4che, like accession based.

e.g.

MSH|^~\&|Sender_HIS|Client_NAME|RIS|Client_NAME|20251026015800||ORM^O01|d67a3113-387c-4200-8ba3-9d6032a2ebd9|P|2.5.1
PID|1||830108^^^URIS||Sxaaxcdecxcdien^Ayxccbvvcba Akrvccvbvcbam^||20001221|F|||||~^NET^Internet^te...@google.com|||S|
PV1||E||U||||^ER  Physician||0|||||||||EMR77949|||||||||||||||||||||||||20251026033233||||||
ORC|NW|1707306|||SC||^^^20251026035700||20251026035700|||||||||LX16|||||||||||||

OBR||1707306||^^^4201^Neck CT Scan^Local||||||||||||||CT10258|1707306|||||CT|||||||~^^^^CT^^^^^^^^20251026035700||||||||||||^EFFECTIVE DATE: 2025/10/26 03:57:00 - REMARKS: er - INDICATION: null|||||||||||||4201^Neck CT Scan^Local
ZDS|1|StudyUID

Without a ZDS You might have to check hl7OrderMissingStudyIUIDPolicy

Specifies policy for missing Study Instance UID in incoming HL7 Order messages. Overwrites value specified on Device level.

Enumerated values::  REJECT, GENERATE, ACCESSION_BASED

Using Accession_Based might be the best option