Encoding for Cyrillic characters in lookup table

[Suzy Hoffman]

I’m trying to use a table to lookup a code and output a translated string in Russian (Cyrillic) characters.  (screenshot of sample table attached).

When I use the table in an xlate and pass messages through, the Latin characters are populated to the target fields, and it seems that an attempt was made to write the Russian/Cyrillic characters but where the Cyrillic characters should be there are only spaces or some other non-displayable characters.  (If I copy the message from SMAT and paste it into a HEX editor the non-displayable characters are 1A).  I’m told that the encoding on the threads needs to be set to something other than the standard UTF-8 we normally use so I’ve tried setting the encoding on the threads to Cyrillic, UTF-8, and Windows-1252 but get the same results.  The receiving system uses Windows-1251 but I don’t think that is the issue as I see the “blank” strings in the message output in SMAT, before the message even gets to the EMR.

Below is what the SMAT file looks like in the IDE.  The table Out values are supposed to populate OBX-3.2:

OBX|1|ST|552^                             ||65|BPM|||||C

OBX|2|ST|553^                             ||65|BPM|||||C

OBX|3|ST|554^PR –        ||198|ms|||||C

OBX|4|ST|555^QRS                   ||92|ms|||||C

OBX|5|ST|556^QT –        ||398|ms|||||C

OBX|6|ST|557^                QT –         ||413|ms|||||C

OBX|7|ST|568^    P||70|degrees|||||C

OBX|8|ST|569^    R||25|degrees|||||C

OBX|9|ST|570^    T||28|degrees|||||C

The receiving system (EMR) view is attached.

Any suggestions on what I need to do to get the Cyrillic characters out in the message?  The sending application sends Cyrillic characters in other fields in the message and they process through fine.  

This is Cloverleaf 6.0 on Windows.

Thanks in advance for your help.

Topic

[Jim Kosloskey]

Suzy,

One point to consider is the SMAT message you see is BEFORE encoding on the outbound thread.

If you want to see what the receiving system is likely to see then try using hcitcptest to receive the message and look at that hex dump.

email: jim.kosloskey@jim-kosloskey.com 29+ years Cloverleaf, 59 years IT - old fart.

[Charlie Bursell]

Along with what Jim says remember what you see displayed in the window is always going to be UTF-8.  Try redirecting to a file and look at it using Word or something like that

[Suzy Hoffman]

In the SMAT tool in Cloverleaf 6.0 there is a drop down, “Selected Encode Scheme”.  I guess I thought that by selecting the encoding that I had configured for the threads I would be seeing what the encoded message would look like when it actually leaves the engine.

Maybe I’m not understanding how the encoding should be set up…. the messages that are sent from the sending application pass through two sites (and 2 threads in each site) and then to the receiving application.  The message translation and table lookup are in the first thread of the first site the message hits.  Do I set the encoding on all 4 threads (which is what I did), or do you only set it on the thread where the actual xlate and lookup table are being used?

[Charlie Bursell]

On the IB thread set it to agree with the encoding used by the sender.  On the OB thread set to agree with the encoding wanted by that vendor

[Author]

Replies