Thank you, it is an awesome explanation @Laura Blázquez García
- Log in to post comments
Thank you, it is an awesome explanation @Laura Blázquez García
Thank you @Alessandra Carena 🔎🙂🙏
Thank you @Kurro Lopez , it is very deep and easy to read. Have you ever had a real use case to use Machine Learning in your daily work? I just ask due to me curiosity.
Thank you @Kurro Lopez
It is truly fascinating. I am thankful for the way that you explained it clearly, and even with visual captures, and a video. Thanks a lot.
Hello @Luis Angel Pérez Ramos 🙂🙂🙂, yes it is the Command Set:
| Tag | Name | Contents |
|---|---|---|
| (0000,0002) | AffectedSOPClassUID | 1.2.840.10008.5.1.4.1.1.4 |
| (0000,0100) | CommandField | 1 |
| (0000,1000) | AffectedSOPInstanceUID | 1.3.46.670589.11.34110.5.0.8212.2025052007473768693 |
It said:
| ERROR <EnsDICOM>NoCompatibleTransferSyntaxFound: No negotiated transfer syntax for SOP class '1.2.840.10008.5.1.4.1.1.4' is compatible with document transfer syntax '1.2.840.10008.1.2.4.70' |
...
...
But on date: "2025-06-05 12:32:05.765", we received a similar DICOM, with a more complete Command Set, and it also failed saying the same exception error (we configured the syntaxes before they sent this DICOM):
| Tag | Name | Contents |
|---|---|---|
| (0000,0000) | CommandGroupLength | 124 |
| (0000,0002) | AffectedSOPClassUID | 1.2.840.10008.5.1.4.1.1.4 |
| (0000,0100) | CommandField | 1 |
| (0000,0110) | MessageID | 1 |
| (0000,0800) | CommandDataSetType | 65278 |
| (0000,1000) | AffectedSOPInstanceUID | 1.3.46.670589.11.34110.5.0.8212.2025052007473768693 |
It said:
| ERROR <EnsDICOM>NoCompatibleTransferSyntaxFound: No negotiated transfer syntax for SOP class '1.2.840.10008.5.1.4.1.1.4' is compatible with document transfer syntax '1.2.840.10008.1.2.4.70' |
...
Please, could you help us? Thank you so much. 🙂🙏🙂
Please, does anybody have any ideas that could help us solve this issue?
Thank you so much!
I suppose DICOM is not the most used feature in HealthShare, right? ^^!!
Isn't there a way to find DICOM messages using Message Viewer filters?
To be honest, to look for DICOM messages by using the Accession Number, is a common use case, but we have not found an automatic way to do it. Isn't there any way to filter DICOM messages with a certain criteria using the Message Viewer filters? 😯🤔🤯
For example, we have created an user "Reader"
Who has the custom role "rol_Reader"
.png)
Whose privileges are:
%DB_%DEFAULT RW
%DB_ESBSSCC R
%Ens_Portal R
%Ens_ProductionConfig R
But it can not even activate the Interoperability button:
.png)
Why?
How could we solve this?
Thank you for your help!
Fascinating.
Thank you @Guillaume Rongier 🙂😊🙂
Upvoted indeed! 7 votes so far. Thank you @Vishal Pallerla for your kind help!
Thank you!
Thank you Alexander for explaining it!