43 votes: 

Word has dark mode, Excel has dark mode, Notepad++ has dark mode, many IDEs (most of them) have dark mode. Please, please, would you consider to add an official dark mode for Healthshare.

Thank you @Jenna Makin for your kind reply.

I will share why none of the options mentioned can be used by me:

Option 1 — Browser Extensions (Desktop Chrome / Edge / Firefox)

We (my team and I) work inside a Virtual Box with a VPN without Internet access (the VPN blocks it all), so there is no way to install browser extensions where we use Healthshare.

Option 2, 3, 4

I (we) don't have iOS. Also CSS Override does not seem like a good solution.

This is why a dark theme is really needed for people like me. 🙏🙂😎🙏

The idea has already 42 votes:

https://ideas.intersystems.com/ideas/DPI-I-768

How many votes would be needed to be this need implemented? Because it is more than an idea, it is just a real huge deep true need. 

Thank you so much @Robbie Luman for your helpful article. We had trouble understanding how to convert a String to JSON without structuring it into an Ens.Response message. Thank you so much. It helped us a lot Robert Luman!

For example, we have created an user "Reader" 

Who has the custom role "rol_Reader" 

Whose privileges are:

    %DB_%DEFAULT     RW
    %DB_ESBSSCC     R
    %Ens_Portal     R
    %Ens_ProductionConfig     R


    
    
But it can not even activate the Interoperability button:

Why?

How could we solve this?

Thank you for your help!

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? 😯🤔🤯

Hello @Luis Angel Pérez Ramos 🙂🙂🙂, yes it is the Command Set:

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):

Command Set

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. 🙂🙏🙂

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.