Dne 17.2.2010 21:16, webtier_at_javadesktop.org napsal(a):
> Hi Martin,
>
>> IMHO this very bad idea (especialy for HL7).
> In my experience typical company implemented very limited subset of HL7 standard.
You are right. We only need Order and Patient (update,merge) related
messages.
> Beside in many cases their implementation doesn't strictly follow letter of the standard.
> So in many cases it makes sense to create customized version that applied only to particular company.
So look at Terser class - with this I am able easily create and parse
messages based on my rules...
> Our implementation of HL7 messages divided in two parts.
> First part used to generate HL7 messages in XML based format(see example below) and other part contains converter that just transform XML to HL7 EDI format.
> There is a chance in future everybody will be used HL7 interchange based on XML. In this case we will get rid from convert part of our implementation.
> Using HL7 XML Schema as validation tools and EL as way to easy get data we have very simple and powerful way to produce HL messages. Also it's working very fast at least if compare it with XLST as template engine.
>
>> If you can, use HAPI.
> Thank you for referring I found their site. I definitely will take a look on it.
I am using this lib since 2006 without problems...
--
Martin Beránek
mailto:martin.beranek_at_i.cz
http://www.i.cz