RE: [HAPI-devel] Missing SIU messages in v231

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

Hi Fr=E9d=E9ric,=20

In 2.3.1 all the SIU events use the SIU_S12 message structure.  MSH-9-3
should be valued SIU_S12 for these messages, in which case HAPI should =
parse
them properly. =20

One of the small changes between HAPI 0.4 beta and 0.4 is that if =
MSH-9-3 is
missing, HAPI will look up the correct message structure based on the =
event.


By the way, my apologies for the delay in getting the final 0.4 version =
out.
The team at UHN has been wrapped up in another project.  The good part =
of
this is that the other project uses HAPI 0.4, and a few bugs have been =
found
as a result.  I'm planning to release 0.4 tomorrow. =20

Bryan=20

> -----Original Message-----
> From: Fr=E9d=E9ric Dubru [mailto:Fre...@cl...]
> Sent: November 3, 2003 8:30 AM
> To: hl7...@li...
> Subject: [HAPI-devel] Missing SIU messages in v231
>=20
>=20
> Hi,
>=20
> There are several SIU messages in package v23 (SIU_S12, SIU_S14,=20
> SIU_S15, etc.) but only one in package v231 (SIU_S12). I've=20
> checked in=20
> hapi_0.4beta_source_v231.zip.
>=20
> Is it normal or is it a bug? Can I generate the missing=20
> messages easily=20
> myself?
>=20
> Thanks,
>=20
> --=20
> Fr=E9d=E9ric Dubru
> Cliniques universitaires Saint-Luc
> 10, avenue Hippocrate
> B-1200 Bruxelles
> +32 2 764 36 43
> http://www.saintluc.be
>=20
>=20
>=20
>=20
> -------------------------------------------------------
> This SF.net email is sponsored by: SF.net Giveback Program.
> Does SourceForge.net help you be more productive?  Does it
> help you create better code?   SHARE THE LOVE, and help us help
> YOU!  Click Here: http://sourceforge.net/donate/
> _______________________________________________
> Hl7api-devel mailing list
> Hl7...@li...
> https://lists.sourceforge.net/lists/listinfo/hl7api-devel
>=20


This e-mail may contain confidential and/or privileged information
for the sole use of the intended recipient. Any review or distribution
by anyone other than the person for whom it was originally intended is
strictly
prohibited. If you have received this e-mail in error, please contact =
the
sender and
delete all copies. Opinions, conclusions or other information contained =
in
this e-mail may not be that of the organization.