RE: [HAPI-devel] ORM 001 and XML

[Tripp, B. <Bry...@uh...>]

Hi Eric,=20

> 3) LAT is not part of the ORM structure, it is an artifact of the
segment being wrapped by the email:

:)=20
=20
> 2) OK. I wanted to use XML to do various transformations with =
XSLT...but
if people don't use the XML much perhaps there is a reason and I should
consider do the transformation in pure Java.

I'm not sure if there is a reason other than tradition.  Although if =
you're
receiving the messages in ER7 you might get better performance without =
XML,
just because you will parse and encode each message once instead of =
twice. =20

> 1) Perhaps I don't know as much as I thought, but how can I specify =
the
message structure more explicitly than have ORM^O01 as MSH-9? And what
is MSH-9-3, I have only seen two subfields in MSH-9, not three. Perhaps
I am misunderstanding.

Come to think of it, MSH-9-3 was introduced in 2.3.1, but you're using =
2.3.
It's an explicit statement of the message structure, whereas MSH-9-1 and
MSH-9-2 give the type and event from which the structure can normally be
derived by lookup (e.g. ADT^A03 uses structure ADT_A01).  It's such a =
handy
field that HAPI recognizes it even if it shows up illegally in earlier
versions.  But maybe changing the default mapping is a better approach =
with
version 2.3. =20
=20
Bryan=20
=20