your assumption is true for Enterprise Archive as XDS Repository but not for all 3rd party Repositories. This request came from Heidelberg based on ICW/XT Repository, they use what the source is sending.
The product and engineering team is not able to understand the reason that XDS Document Source should fill in ‘repositoryUniqueId’ in the ITI-41/RAD-68 PnRDocSet request.
Whatever the XDS Document Source would place in there would be replaced by XDS Repository with its configured value for ‘repositoryUniqueId’ when doing RegDocSet ITI-42 request to the XDS Registry.
Hi Ralf, this looks like an IHE violation in the X-Tention XDS repository. Can you open a support case with X-Tention?
your assumption is true for Enterprise Archive as XDS Repository but not for all 3rd party Repositories. This request came from Heidelberg based on ICW/XT Repository, they use what the source is sending.
The product and engineering team is not able to understand the reason that XDS Document Source should fill in ‘repositoryUniqueId’ in the ITI-41/RAD-68 PnRDocSet request.
Whatever the XDS Document Source would place in there would be replaced by XDS Repository with its configured value for ‘repositoryUniqueId’ when doing RegDocSet ITI-42 request to the XDS Registry.