[HAPI-devel] Inferring .xsd for HAPI generated xml?

[Simon S. <sgs...@ya...>]

Hi;

	We're planning to use HAPI as an adapter to allow us
to wire multiple  systems with slightly different Hl7
protocols in to a Java J2EE Business Processing and
EAI backbone. Internally, the EAI backbone will pass
around XML messages produced by HAPI-based programs
parsing HL7 messages. The J2EE EAI backbone has drag
and drop programming tools that make it relatively
simple to work with XML messages. 

Right now, HAPI Test Panel won’t properly parse the
particular versions of the messages produced by some
of the HL7 systems that we need to pass around the
backbone (A19, Q11, A01, A02, A03, A08, A31, O01,
P03). We'll be performing some custom modifications to
HAPI libraries to allow us to properly parse the
non-conforming messages, but for now, we can't specify
the XML interfaces between the internal components of
the EAI Backbone because we can't generate XML from
HAPI which we can use to infer .xsds.

Is there a way to find or generate HAPI's natural
.xsds for the common messages I have identified? Id
there a "one big generic" HL7 .xsd for HAPI?

Many thanks;
Simon


Find local movie times and trailers on Yahoo! Movies.
http://au.movies.yahoo.com