How to convert UTF8 special characters to the actual character

Question

Question

#DTL #HL7 #Interoperability #Management Portal #Caché #InterSystems IRIS for Health #Ensemble #Global Masters #Health Connect #InterSystems IRIS

We are receiving the report in text format and it has special characters like ', - like that in the text. Source system is using the UTF8 encoding format hence the text is showing as ' � ' . Is there a way to convert the utf8 to actual character in the DTL.

Thank you,

Product version: IRIS 2022.1

$ZV: IRIS for UNIX (Red Hat Enterprise Linux 7 for x86-64) 2022.1 (Build 209U) Tue May 31 2022 12:13:58 EDT [HealthConnect:3.5.0] [HealthConnect:3.5.0]

Discussion (6)2

Log in or sign up to continue

Enrico Parisi · Mar 29

Character set conversion should be /configured/applied in the receiving service/adapter.

Unfortunately you did not provide any useful details, so it's impossible to help.

0 0

Padmaja Konduru · Mar 29

This is TCP HL7 Service using class 'EnsLib.HL7.Service.TCPService' and adapter is EnsLib.HL7.Adapter.TCPInboundAdapter. while occuring the issue I set Default Char Encoding as "!iso-8859-1" but it is not working as expected. It is converting utf8 charctaer to '?'.

0 0

Enrico Parisi · Mar 30

For the incoming HL7 messages, does the field MSH:CharacterSet (MSH:18) contains a value? Is so, what's the value?

You write that the receiver message is encoded using utf-8, have you tried to configure the "Default Char Encoding" setting in the Business Service to "utf-8"?

If the incoming HL7 message is actually/really encoded using utf-8 and MSH:18 contains a value different than "utf-8", you can enforce conversion configuring the "Default Char Encoding" setting in the Business Service to "!utf-8".

I hope the message is not malformed and contains data/fields with different codes, if so...it can be tricky.

0 0

Padmaja Konduru · Mar 30

Hi Enrico,

Thanks for your response,

The inbound message doesn't have MSH:18 value. I tried using UTF-18 but didn't work. Is there any possibility to resolve the issue to decode the characters correctly?

0 0

Enrico Parisi · Mar 30

First you MUST be positively sure on what the character set is actually used in the incoming HL7 message.

What's the character set of the incoming message?

If it's really utf-8 then setting "Default Char Encoding" to utf-8 should work, if it does not, then evidently the incoming message use a different character set.

Just in case, try setting "Default Char Encoding" to "!utf8"

0 0

Padmaja Konduru · Mar 31

Thank you! I will try this.

0 0