I have encountered some issues with character sets, although not to the
extent Tom is dealing with.
Rahul's comment about the character sets at each end is something I
have encountered, and I will add that on the UNIX platforms I have dealt
with, the base character set is NOT configured to UTF-8, which adds
another layer at which there can be differing interpretations.
My experience has made me cautious, particularly where Microsoft based
systems send to a UNIX based system which transforms and sends on to
another Microsoft system. Since the base character set interpretation
effectively changes at each boundary, loss of 'special' characters is
likely. Many a time I have seen the ?, and seldom have I been able to
prevent it's appearance. Pasting reports from MS-Word is particularly
fraught.
During my search I found several Wiki's and sites discussing the
history of character sets and the growth of UTF-xx. What a revelation
that is!
Thanks for the example message, and the advice about MSH-18. I will be
saving that away for further use.
Ian
>>> Rahul Somasunderam <r...@certifydatasystems.com> 15/01/14 5:53 >>>
That is a sign of not having the same charset on both ends.
In the MSH segment, I recall there are some restrictions that require
you to stay within ASCII 7 bit. The other segments can be any charset
you choose.
On Jan 14, 2014, at 11:27 AM, Tom Wilson <twil...@sujansky.com> wrote:
After some research, I have answered my own question. If no character
set is defined in MSH-18, then the default is single byte printable
ASCII (decimal 32-127).
If anyone is interested, I am attaching a test ORU file which includes
a full set of UTF-8 characters, above and beyond what is supported. You
can trim it to use this in your tests, or test a more extensive UTF-8
support if you like.
-tom
From: Tom Wilson [mailto:twil...@sujansky.com]
Sent: Tuesday, January 14, 2014 10:27 AM
To: hl7api-devel@lists.sourceforge.net
Subject: [HAPI-devel] UTF-8 support, how to define and test?
Hi.
I’m in the final testing phase of a HAPI-based application, and I want
to define precisely what character encoding it can support. I know the
HL7v2 spec defines UTF-8 as the supported character set. However, it
looks like it is only supporting a subset of UTF-8. I am testing by
ingesting an HL7v2 message in a unit test and serializing to XML. For
example, it looks like Simplified Chinese, Vietnamese, Cyrillic, are not
supported.
Sending this in an NTE segment:
我能吞下玻璃而不伤身体
Produces this on the other end:
???????????
So, exactly what UTF-8 characters can I expect to work? I also want to
create a unit test with a full range of the supported characters.
It might be nice to support other languages, but I don’t know if I can
expect to receive them from EMR systems.
Thanks in advance,
-tom
<complete-utf8-set.oru>------------------------------------------------------------------------------
CenturyLink Cloud: The Leader in Enterprise Cloud Services.
Learn Why More Businesses Are Choosing CenturyLink Cloud For
Critical Workloads, Development Environments & Everything In Between.
Get a Quote or Start a Free Trial Today.
http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk_______________________________________________
Hl7api-devel mailing list
Hl7api-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/hl7api-devel
********************************************************************************
This email, including any attachments sent with it, is confidential and for the
sole use of the intended recipient(s). This confidentiality is not waived or
lost, if you receive it and you are not the intended recipient(s), or if it is
transmitted/received in error.
Any unauthorised use, alteration, disclosure, distribution or review of this
email is strictly prohibited. The information contained in this email,
including any attachment sent with it, may be subject to a statutory duty of
confidentiality if it relates to health service matters.
If you are not the intended recipient(s), or if you have received this email in
error, you are asked to immediately notify the sender by telephone collect on
Australia +61 1800 198 175 or by return email. You should also delete this
email, and any copies, from your computer system network and destroy any hard
copies produced.
If not an intended recipient of this email, you must not copy, distribute or
take any action(s) that relies on it; any form of disclosure, modification,
distribution and/or publication of this email is also prohibited.
Although Queensland Health takes all reasonable steps to ensure this email does
not contain malicious software, Queensland Health does not accept
responsibility for the consequences if any person's computer inadvertently
suffers any disruption to services, loss of information, harm or is infected
with a virus, other malicious computer programme or code that may occur as a
consequence of receiving this email.
Unless stated otherwise, this email represents only the views of the sender and
not the views of the Queensland Government.
**********************************************************************************
------------------------------------------------------------------------------
CenturyLink Cloud: The Leader in Enterprise Cloud Services.
Learn Why More Businesses Are Choosing CenturyLink Cloud For
Critical Workloads, Development Environments & Everything In Between.
Get a Quote or Start a Free Trial Today.
http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk
_______________________________________________
Hl7api-devel mailing list
Hl7api-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/hl7api-devel
