You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a RIS that is sending ORC-1=SC and ORC-5=IP Modality worklist messages. These are not in the default Vendor data wrapping sets, so messages with those elements are getting rejected.
"The values present in ORC fields 1 and 5 decide the Scheduled Procedure Step Status that is applied to the MWL. The enumerated combinations of values in fields 1 and 5 of ORC segment currently supported by the archive are NW_SC, NW_IP, CA_CA, DC_CA, XO_SC, XO_CM where the first two letters eg. “NW” represent value in field 1 and the next letter(s) after the “_” eg. “SC” represent value in field 5. These combinations can be mapped to different Scheduled Procedure Step Status supported by archive : SCHEDULED, ARRIVED, READY, STARTED, DEPARTED, CANCELLED, DISCONTINUED, COMPLETED. One can map multiple combinations of ORC:1_ORC:5 to a scheduled procedure step status."
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hey everyone.
I have a RIS that is sending ORC-1=SC and ORC-5=IP Modality worklist messages. These are not in the default Vendor data wrapping sets, so messages with those elements are getting rejected.
I have done a lot of searching, finding the page that specifies the hl7 wrapping can be modified at the vendor data file: h17-order2dcm from this page: https://dcm4chee-arc-hl7cs.readthedocs.io/en/latest/orm/inbound.html#note9
"The values present in ORC fields 1 and 5 decide the Scheduled Procedure Step Status that is applied to the MWL. The enumerated combinations of values in fields 1 and 5 of ORC segment currently supported by the archive are NW_SC, NW_IP, CA_CA, DC_CA, XO_SC, XO_CM where the first two letters eg. “NW” represent value in field 1 and the next letter(s) after the “_” eg. “SC” represent value in field 5. These combinations can be mapped to different Scheduled Procedure Step Status supported by archive : SCHEDULED, ARRIVED, READY, STARTED, DEPARTED, CANCELLED, DISCONTINUED, COMPLETED. One can map multiple combinations of ORC:1_ORC:5 to a scheduled procedure step status."
This says it can be done but does not further point to more resources on how to do it. Looking at the vendor data file I cannot understand what is actually being done. I have read most of this page and Im still not getting it. https://dicom.nema.org/medical/dicom/current/output/html/part19.html#table_A.1.5-1
Would someone be willing to explain how to do this to me please?
Here is the error as written in the DCM arc light log file
Beta Was this translation helpful? Give feedback.
All reactions