hl7api-devel — developer list

[HAPI-devel] =?ISO-8859-1?Q?Re:_R=E9p._:_[HAPI-devel]_Problem_in_P?= =?ISO-8859-1?Q?arsing_ORM=5FO01_Message_in_HAPI_v2.3.1?=

[Steve H. <ste...@gm...>]

Sorry for my earlier reply.  I didn't see this email with your HL7 message =
text.

An HL7 message generally should have several "segments," each of which
appears on its own "line" (meaning they are separated by "\r").  Some
segments are actually part of a "group" (groups may also be part of
another group).  You have provided only an MSH segment, which is the
message header.  Other segments are, I believe, required for an ORM
O01 message (sorry, I don't have the code with me now).

You may want to download the source code for the HL7 version you want
to use (for example, 2.3.1 is here:=20
http://prdownloads.sourceforge.net/hl7api/hapi-0.4.3_source_v231.zip?downlo=
ad).
 Under the "model.message" package (I think), you can find "ORM_O01"
and see what is required for a valid ORM O01 message.  This is defined
when calling field constructors in the message's constructor, if I
remember correctly.

IMO, HL7 is a bit difficult to understand at first, but it should get
easier if you stick to it.  Good luck.


-Steve


On Tue, 22 Mar 2005 02:21:08 -0800 (PST), Praveen Kumar
<pra...@ya...> wrote:
> =20
> =20
>=20
> Hi ALL,=20
>=20
> I am using v2.3.1 .=20
>=20
> Even with the latest version of 0.4.3 I am getting same result as I have
> mentioned earlier.=20
>=20
> Even I tried with ur input string also I am getting the same ouput .=20
>=20
> I am sending the program I used and the output along with it=20
>=20
> Please provide the needful solution for it.=20
>=20
> package org.srit.hl7;=20
>=20
> import ca.uhn.hl7v2.HL7Exception;=20
>=20
> import ca.uhn.hl7v2.model.Message;=20
>=20
> import ca.uhn.hl7v2.parser.EncodingNotSupportedException;=20
>=20
> import ca.uhn.hl7v2.parser.PipeParser;=20
>=20
> =20
>=20
> public class TestORM {=20
>=20
> =20
>=20
> public static void main(String[] args) {=20
>=20
> =20
>=20
> Message msg =3D null;=20
>=20
> PipeParser parser =3D new PipeParser();=20
>=20
> =20
>=20
> // String msgText =3D "MSH|^~\\&|||||||ORM^O01^ORM_O01|00613205|P|2.3.1||=
\r"=20
>=20
> // +"PID|||xxxxx|00000|patienta^one||19230306|M||U||||||||493094";=20
>=20
> String msgText =3D
> "MSH|^~\\&|REQUETE|6^CL|UNILAB||20040305110331||ORM^O01^ORM_O01|XXXX|T|2.=
3.1|||||||";
>=20
> =20
>=20
> =20
>=20
> try {=20
>=20
> msg =3D parser.parse(msgText);=20
>=20
> } catch (EncodingNotSupportedException e) {=20
>=20
> // TODO Auto-generated catch block=20
>=20
> e.printStackTrace();=20
>=20
> } catch (HL7Exception e) {=20
>=20
>  =20
>=20
> e.printStackTrace();=20
>=20
> }=20
>=20
> =20
>=20
> System.out.println("Message is : " +msg.getName());=20
>=20
> =20
>=20
> }=20
>=20
> }=20
>=20
> OUTPUT=20
>=20
> Message is : RDO_O01
>=20
> Aris JAVIER RAMOS <Ari...@hc...> wrote:=20
> What version of HAPI are you using ??
>=20
> have you tryed with the last version of HAPI (version 0.4.3) ?
>=20
> have you specifiyed the message structure to use in the MSH-9-3=20
>=20
> like this :
> MSH|^~\&|REQUETE|6^CL|UNILAB||20040305110331||ORM^O01^ORM_O01|XXXX|T|2.3.=
1|||||||
>=20
>=20
>=20
> Aris Javier Ramos
> Analyste-Developpeur
> H=F4pital Cantonal Universitaire de Gen=E8ve
> Rue Micheli-du-Crest 24
> 1211 Gen=E8ve
>=20
> >>> Praveen Kumar 03/22 7:11 >>>
> Hi All,
> I am a new member to this group.My Name is Praveen.=20
>=20
> I have one doubt.
>=20
> I am parsing a ORM_O01 HL7 Message of HAPI v2.3.1=20
> After parsing of the messag,i am getting RDO_O01 Message Object.
>=20
> this is wrong because after parsing ORM_O01 Message I need to get ORM_O01
> Message Object itself .
>=20
> But My question is why I am geeting RDO_O01 Object af ter parsing ORM_O01
> Message??????
>=20
> The same persists for v2.3 also
>=20
> For other versions of HAPI namely v2.2 and v2.4 I am getting the correct
> result.ie I am getting ORM_O01 Object after parsing ORM_O01=20
>=20
>=20
> Is there any solution for this problem???
>=20
>=20
> Its bit urgent.
>=20
> Hoping for eary reply for this message
>=20
> Rgds
> Praveen Kumar.A
>=20
>=20
>=20
>=20
>=20
> ---------------------------------
> Do you Yahoo!?
> Yahoo! Small Business - Try our new resources site!=20
>=20
>=20
>=20
> **********************************************************************
> This email and any files transmitted with it are confidential and
> intended solely for the use of the individual or entity to whom they
> are addressed. If you have received this email in error please notify
> the system manager.
>=20
> **********************************************************************
>=20
>=20
>=20
> __________________________________________________
> D o You Yahoo!?
> Tired of spam? Yahoo! Mail has the best spam protection around=20
> http://mail.yahoo.com

Re: [HAPI-devel] Problem in Parsing ORM_O01 Message in HAPI v2.3.1

[Steve H. <ste...@gm...>]

Praveen,

Can you post the content of your HL7 message?  It may be hard for
people here to help without it.

Thanks.


-Steve


On Mon, 21 Mar 2005 22:11:28 -0800 (PST), Praveen Kumar
<pra...@ya...> wrote:
> Hi All, 
>            I am a new member to this group.My Name is Praveen. 
>   
>   I have one doubt. 
>   
>    I am  parsing  a ORM_O01 HL7 Message of HAPI v2.3.1 
>    After parsing of the messag,i  am getting RDO_O01 Message Object. 
>    
>    this is wrong because after parsing ORM_O01 Message I need to get ORM_O01
> Message   Object   itself . 
>   
>  But My question is why I am geeting RDO_O01 Object after parsing ORM_O01
> Message?????? 
>   
> The same persists for v2.3 also 
>   
> For other versions of HAPI namely v2.2 and v2.4 I am getting the correct
> result.ie I am getting ORM_O01 Object after parsing ORM_O01 
>   
>   
> Is there any solution for this problem??? 
>   
>   
> Its bit urgent. 
>   
> Hoping for eary reply for this message 
>   
> Rgds 
> Praveen Kumar.A 
>   
>   
>  
> 
>  ________________________________
> Do you Yahoo!?
>  Yahoo! Small Business - Try our new resources site! 
> 
>

Re: Rép. : [HAPI-devel] Problem in Parsing ORM_O01 Message in HAPI v2.3.1

[Praveen K. <pra...@ya...>]

Hi ALL,

I am using v2.3.1 .

Even with the latest version of 0.4.3 I am getting same result as I have mentioned earlier.

Even I tried with ur input string also I am getting the same ouput .

I am sending the program I used and the output along with it

Please provide the needful solution for it.

package org.srit.hl7;

import ca.uhn.hl7v2.HL7Exception;

import ca.uhn.hl7v2.model.Message;

import ca.uhn.hl7v2.parser.EncodingNotSupportedException;

import ca.uhn.hl7v2.parser.PipeParser;



public class TestORM {


public static void main(String[] args) {



Message msg = null;

PipeParser parser = new PipeParser();



// String msgText = "MSH|^~\\&|||||||ORM^O01^ORM_O01|00613205|P|2.3.1||\r"

// +"PID|||xxxxx|00000|patienta^one||19230306|M||U||||||||493094";

String msgText = "MSH|^~\\&|REQUETE|6^CL|UNILAB||20040305110331||ORM^O01^ORM_O01|XXXX|T|2.3.1|||||||";





try {

msg = parser.parse(msgText);

} catch (EncodingNotSupportedException e) {

// TODO Auto-generated catch block

e.printStackTrace();

} catch (HL7Exception e) {

 

e.printStackTrace();

}



System.out.println("Message is : " +msg.getName());



}

}

OUTPUT

Message is : RDO_O01


Aris JAVIER RAMOS <Ari...@hc...> wrote: What version of HAPI are you using ??

have you tryed with the last version of HAPI (version 0.4.3) ?

have you specifiyed the message structure to use in the MSH-9-3 

like this : MSH|^~\&|REQUETE|6^CL|UNILAB||20040305110331||ORM^O01^ORM_O01|XXXX|T|2.3.1|||||||



Aris Javier Ramos
Analyste-Developpeur
Hôpital Cantonal Universitaire de Genève
Rue Micheli-du-Crest 24
1211 Genève

>>> Praveen Kumar 
03/22 7:11 >>>
Hi All,
I am a new member to this group.My Name is Praveen. 

I have one doubt.

I am parsing a ORM_O01 HL7 Message of HAPI v2.3.1 
After parsing of the messag,i am getting RDO_O01 Message Object.

this is wrong because after parsing ORM_O01 Message I need to get ORM_O01 Message Object itself .

But My question is why I am geeting RDO_O01 Object after parsing ORM_O01 Message??????

The same persists for v2.3 also

For other versions of HAPI namely v2.2 and v2.4 I am getting the correct result.ie I am getting ORM_O01 Object after parsing ORM_O01 


Is there any solution for this problem???


Its bit urgent.

Hoping for eary reply for this message

Rgds
Praveen Kumar.A





---------------------------------
Do you Yahoo!?
Yahoo! Small Business - Try our new resources site! 



**********************************************************************
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the system manager.

**********************************************************************




__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 

[HAPI-devel] =?ISO-8859-1?Q?R=E9p.=20:=20[HAPI-devel]=20Problem=20in=20Parsin?= =?ISO-8859-1?Q?g=20ORM=5FO01=20Message=20in=20HAPI=20=20v2.3.1?=

[Aris J. R. <Ari...@hc...>]

What version of HAPI are you using ??

have you tryed with the last version of HAPI (version 0.4.3) ?

have you specifiyed the message structure to use in the MSH-9-3=20

like this : MSH|^~\&|REQUETE|6^CL|UNILAB||20040305110331||ORM^O01^ORM_O01|X=
XXX|T|2.3.1|||||||



Aris Javier Ramos
Analyste-Developpeur
H=F4pital Cantonal Universitaire de Gen=E8ve
Rue Micheli-du-Crest 24
1211 Gen=E8ve

>>> Praveen Kumar <pra...@ya...> 03/22 7:11  >>>
Hi All,
           I am a new member to this group.My Name is Praveen.=20
=20
  I have one doubt.
=20
   I am  parsing  a ORM_O01 HL7 Message of HAPI v2.3.1=20
   After parsing of the messag,i  am getting RDO_O01 Message Object.
  =20
   this is wrong because after parsing ORM_O01 Message I need to get ORM_O0=
1 Message   Object   itself .
=20
 But My question is why I am geeting RDO_O01 Object after parsing ORM_O01 M=
essage??????
=20
The same persists for v2.3 also
=20
For other versions of HAPI namely v2.2 and v2.4 I am getting the correct re=
sult.ie I am getting ORM_O01 Object after parsing ORM_O01=20
=20
=20
Is there any solution for this problem???
=20
=20
Its bit urgent.
=20
Hoping for eary reply for this message
=20
Rgds
Praveen Kumar.A
=20
=20
=20

	=09
---------------------------------
Do you Yahoo!?
 Yahoo! Small Business - Try our new resources site!=20



**********************************************************************
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the system manager.

**********************************************************************

[HAPI-devel] Problem in Parsing ORM_O01 Message in HAPI v2.3.1

[Praveen K. <pra...@ya...>]

Hi All,
           I am a new member to this group.My Name is Praveen. 
 
  I have one doubt.
 
   I am  parsing  a ORM_O01 HL7 Message of HAPI v2.3.1 
   After parsing of the messag,i  am getting RDO_O01 Message Object.
   
   this is wrong because after parsing ORM_O01 Message I need to get ORM_O01 Message   Object   itself .
 
 But My question is why I am geeting RDO_O01 Object after parsing ORM_O01 Message??????
 
The same persists for v2.3 also
 
For other versions of HAPI namely v2.2 and v2.4 I am getting the correct result.ie I am getting ORM_O01 Object after parsing ORM_O01 
 
 
Is there any solution for this problem???
 
 
Its bit urgent.
 
Hoping for eary reply for this message
 
Rgds
Praveen Kumar.A
 
 
 

		
---------------------------------
Do you Yahoo!?
 Yahoo! Small Business - Try our new resources site! 

[HAPI-devel] HAPI 0.4.3 and more

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

HAPI 0.4.3 is available for download here:
http://sourceforge.net/project/showfiles.php?group_id=3D38899&package_id=3D=
31129
&release_id=3D309465

This is intended as the last maintenance release before 0.5.  HL7 2.5
support is not included, but it is available on request and will be =
included
in 0.5.  All reported non-2.5 bugs have been fixed.=20

There are also some new conformance tools that HAPI users may be =
interested
in.  Please see links here:
http://hl7api.sourceforge.net/conf/conformance.html.  For your =
convenience,
here are the descriptions:=20

HAPI Class Transform: An XSL tool by Darius Kemeklis that transforms a
profile, which may include Z-segments, into custom message classes for =
HAPI.
It's integrated into the Messaging Workbench.  =20

Message Maker: This tool by Rob Snelick and colleagues (NIST) generates =
test
messages from a conformance profile. =20

All the best,=20
Bryan=20

Re: [HAPI-devel] ORM 001 and XML

[Eric F. <ef...@ne...>]

No error, just no change: it continued to use RDO. In fact, if I change 
the version number to 2.3.1, it still uses RDO (but perhaps there are 
other parts of the message that are not 2.3.1. kosher).

That is the right form, no? ORM^O01^ORM_O01

Eric

Tripp, Bryan wrote:
> Strange, I tried it too, and it worked for me.  Was there an error message
> or did it just continue to use RDO? 
> 
> Bryan 
> 
> -----Original Message-----
> From: Eric Freed [mailto:ef...@ne...]
> Sent: Thu 2/24/2005 2:39 PM
> To: Tripp, Bryan
> Cc: hl7...@li...
> Subject: Re: [HAPI-devel] ORM 001 and XML
>  
> Thanks,
> 
> I changed the default mapping for version 2.3 and it worked, so that is 
> good.
> 
> But I also tried to add the MSH-9-3 field (illegally) to the v2.3 
> message but had no luck. Out of curiosity, what would MSH-9 look like if 
> I waned to use the ORM_O01 structure? I tried:
> 
> ORM^O01^ORM_O01
> 
> but it did not work.
> 
> 
> 
> Tripp, Bryan wrote:
> 
> 
>>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.  
>> 
>>Bryan 
>> 
> 
> 

-- 
Eric Freed
IT Manager
New Rochelle Radiology
914-633-7700 x339

Re: [HAPI-devel] ORM 001 and XML

[Eric F. <ef...@ne...>]

Thanks,

I changed the default mapping for version 2.3 and it worked, so that is 
good.

But I also tried to add the MSH-9-3 field (illegally) to the v2.3 
message but had no luck. Out of curiosity, what would MSH-9 look like if 
I waned to use the ORM_O01 structure? I tried:

ORM^O01^ORM_O01

but it did not work.



Tripp, Bryan wrote:

> 
> 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.  
>  
> Bryan 
>  

-- 
Eric Freed
IT Manager
New Rochelle Radiology
914-633-7700 x339

Re: [HAPI-devel] ORM 001 and XML

[Archie C. <ar...@de...>]

Tripp, Bryan wrote:
>>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.

By the way.. for what it's worth, we are using the XML form and it is
integral to the way our product works. HAPI inputs HL7 which we convert
to XML and then run XSLT to convert that "raw" input into a form our
product understands. The whole process works very nicely...

-Archie

__________________________________________________________________________
Archie Cobbs      *        CTO, Awarix        *      http://www.awarix.com

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

Re: [HAPI-devel] ORM 001 and XML

[Eric F. <ef...@ne...>]

In reverse order:

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

OBR||LL02-194182|(963)232-25AF|71020^CHEST PA 
LAT||20020920||||||||||455^JONES^JOHN|(914)632-9422

is one line with "|71020^CHEST PA LAT|" being field 5

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.

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.

Many Thanks




Tripp, Bryan wrote:
> Hi Eric, 
>  
> There are a few things here: 1) The O01 event has a number of alternative
> structures associated with it, which makes it impossible to choose the
> "right" message structure based on the event alone (I'm not aware of any
> other events like this).  HAPI defaults to RDO.  There are two ways you can
> deal with this. If possible, specify the message structure in MSH-9-3 as
> ORM_O01.  The other way is to change the default mapping in parser.event_map
> from the RDO to the ORM structure.  
>  
> 2) HAPI's XML support doesn't handle unexpected segments.  (This is on the
> list of things to do but hasn't been a priority, because few people seem to
> use XML.)  If the RDO structure is used, your OBR segment looks like an
> unexpected one, and the XML parser ignores it.  
>  
> 3) I don't have the specs with me (I'm not at work today), but is LAT part
> of the ORM structure?  If not it will be seen as unexpected in any case, and
> will be ignored by the XML parser.  To address this you would have to
> customize the ORM_O01 class (not difficult ... just one line of code added
> to the constructor).  
>  
> Bryan 
> 
> ________________________________
> 
> From: hl7...@li... on behalf of Eric Freed
> Sent: Wed 23/02/2005 3:28 PM
> To: hl7...@li...
> Subject: [HAPI-devel] ORM 001 and XML
> 
> 
> 
> Hi,
> 
> I am having a problem that I think is related to a problem that has been
> brought up here a few times, but I am not sure of the answer.
> 
> In the course of testing I tried to have a message go from regular
> encoding, to XML and then back. However, the final message is not the
> same as the first one:
> 
> First message:
> 
> ----------------------------------------------------------
> MSH|^~\&|ADS|LL|PSCRIBE||200209181134||ORM^O01|2|P|2.3
> PID|||263334||SMITH^JOHN||19471112|M|||ADDRESS^^CITY^ST||(914)633-7700|||||2
> 63334|123-45-6789
> ORC|NW|LL02-194182||||||||||455^JONES^JOHN
> OBR||LL02-194182|(963)232-25AF|71020^CHEST PA
> LAT||20020920||||||||||455^JONES^JOHN|(914)632-9422
> ----------------------------------------------------------
> 
> returned message:
> 
> ----------------------------------------------------------
> MSH|^~\&|ADS|LL|PSCRIBE||200209181134||ORM^O01|2|P|2.3
> PID|||263334||SMITH^JOHN||19471112|M|||ADDRESS^^CITY^ST||(914)633-7700|||||2
> 63334|123-45-6789
> ORC|NW|LL02-194182||||||||||455^JONES^JOHN
> ------------------------------------------------------------
> 
> 
> The OBR segment is missing. When I look at the XML, it starts with <RDO_O01>
> 
> I know the RDO^O01 and ORM^O01 issue has been brought up here, but I
> didn't see a solution and don't know if it would cause the problem above.
> 
> Any advice?
> 
> Thanks,
> 
> 
> --
> Eric Freed
> IT Manager
> New Rochelle Radiology
> 914-633-7700 x339
> 
> 
> 
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real users.
> Discover which products truly live up to the hype. Start reading now.
> http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
> _______________________________________________
> Hl7api-devel mailing list
> Hl7...@li...
> https://lists.sourceforge.net/lists/listinfo/hl7api-devel
> 
> 
> 
> 
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real users.
> Discover which products truly live up to the hype. Start reading now.
> http://ads.osdn.com/?ad_ide95&alloc_id396&op=click
> _______________________________________________
> Hl7api-devel mailing list
> Hl7...@li...
> https://lists.sourceforge.net/lists/listinfo/hl7api-devel

-- 
Eric Freed
IT Manager
New Rochelle Radiology
914-633-7700 x339

RE: [HAPI-devel] ORM 001 and XML

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

Hi Eric,=20
=20
There are a few things here: 1) The O01 event has a number of =
alternative
structures associated with it, which makes it impossible to choose the
"right" message structure based on the event alone (I'm not aware of any
other events like this).  HAPI defaults to RDO.  There are two ways you =
can
deal with this. If possible, specify the message structure in MSH-9-3 as
ORM_O01.  The other way is to change the default mapping in =
parser.event_map
from the RDO to the ORM structure. =20
=20
2) HAPI's XML support doesn't handle unexpected segments.  (This is on =
the
list of things to do but hasn't been a priority, because few people seem =
to
use XML.)  If the RDO structure is used, your OBR segment looks like an
unexpected one, and the XML parser ignores it. =20
=20
3) I don't have the specs with me (I'm not at work today), but is LAT =
part
of the ORM structure?  If not it will be seen as unexpected in any case, =
and
will be ignored by the XML parser.  To address this you would have to
customize the ORM_O01 class (not difficult ... just one line of code =
added
to the constructor). =20
=20
Bryan=20

________________________________

From: hl7...@li... on behalf of Eric Freed
Sent: Wed 23/02/2005 3:28 PM
To: hl7...@li...
Subject: [HAPI-devel] ORM 001 and XML



Hi,

I am having a problem that I think is related to a problem that has been
brought up here a few times, but I am not sure of the answer.

In the course of testing I tried to have a message go from regular
encoding, to XML and then back. However, the final message is not the
same as the first one:

First message:

----------------------------------------------------------
MSH|^~\&|ADS|LL|PSCRIBE||200209181134||ORM^O01|2|P|2.3
PID|||263334||SMITH^JOHN||19471112|M|||ADDRESS^^CITY^ST||(914)633-7700|||=
||2
63334|123-45-6789
ORC|NW|LL02-194182||||||||||455^JONES^JOHN
OBR||LL02-194182|(963)232-25AF|71020^CHEST PA
LAT||20020920||||||||||455^JONES^JOHN|(914)632-9422
----------------------------------------------------------

returned message:

----------------------------------------------------------
MSH|^~\&|ADS|LL|PSCRIBE||200209181134||ORM^O01|2|P|2.3
PID|||263334||SMITH^JOHN||19471112|M|||ADDRESS^^CITY^ST||(914)633-7700|||=
||2
63334|123-45-6789
ORC|NW|LL02-194182||||||||||455^JONES^JOHN
------------------------------------------------------------


The OBR segment is missing. When I look at the XML, it starts with =
<RDO_O01>

I know the RDO^O01 and ORM^O01 issue has been brought up here, but I
didn't see a solution and don't know if it would cause the problem =
above.

Any advice?

Thanks,


--
Eric Freed
IT Manager
New Rochelle Radiology
914-633-7700 x339



-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=3D6595&alloc_id=3D14396&op=3Dclick
_______________________________________________
Hl7api-devel mailing list
Hl7...@li...
https://lists.sourceforge.net/lists/listinfo/hl7api-devel

RE: [HAPI-devel] ORM 001 and XML

[Shrock, C. <Sh...@in...>]

I see v2.3--good, I was seeing messages that said they were v2.2 but had
some v2.3 components.  I ended up having to extend the v2.2 model to include
this "new" functionality.  Off the top of my head, I would start looking at
model/v23/message/ORM_O01 and model/v23/message/RDO_O01 classes and verify
that the segments/groups that those classes load can match the message
structure that you are receiving.  Have you verified that is not related to
the XML encoding by testing the messages with the included app/TestPanel
class (it is the default class when you execute the hapi jar file)?

-----Original Message-----
From: Eric Freed [mailto:ef...@ne...] 
Sent: Wednesday, February 23, 2005 12:28 PM
To: hl7...@li...
Subject: [HAPI-devel] ORM 001 and XML


Hi,

I am having a problem that I think is related to a problem that has been 
brought up here a few times, but I am not sure of the answer.

In the course of testing I tried to have a message go from regular 
encoding, to XML and then back. However, the final message is not the 
same as the first one:

First message:

----------------------------------------------------------
MSH|^~\&|ADS|LL|PSCRIBE||200209181134||ORM^O01|2|P|2.3
PID|||263334||SMITH^JOHN||19471112|M|||ADDRESS^^CITY^ST||(914)633-7700||
PID|||263334|||||263334|123-45-6789
ORC|NW|LL02-194182||||||||||455^JONES^JOHN
OBR||LL02-194182|(963)232-25AF|71020^CHEST PA
LAT||20020920||||||||||455^JONES^JOHN|(914)632-9422
----------------------------------------------------------

returned message:

----------------------------------------------------------
MSH|^~\&|ADS|LL|PSCRIBE||200209181134||ORM^O01|2|P|2.3
PID|||263334||SMITH^JOHN||19471112|M|||ADDRESS^^CITY^ST||(914)633-7700||
PID|||263334|||||263334|123-45-6789
ORC|NW|LL02-194182||||||||||455^JONES^JOHN
------------------------------------------------------------


The OBR segment is missing. When I look at the XML, it starts with <RDO_O01>

I know the RDO^O01 and ORM^O01 issue has been brought up here, but I 
didn't see a solution and don't know if it would cause the problem above.

Any advice?

Thanks,


-- 
Eric Freed
IT Manager
New Rochelle Radiology
914-633-7700 x339



-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Hl7api-devel mailing list
Hl7...@li...
https://lists.sourceforge.net/lists/listinfo/hl7api-devel

[HAPI-devel] ORM 001 and XML

[Eric F. <ef...@ne...>]

Hi,

I am having a problem that I think is related to a problem that has been 
brought up here a few times, but I am not sure of the answer.

In the course of testing I tried to have a message go from regular 
encoding, to XML and then back. However, the final message is not the 
same as the first one:

First message:

----------------------------------------------------------
MSH|^~\&|ADS|LL|PSCRIBE||200209181134||ORM^O01|2|P|2.3
PID|||263334||SMITH^JOHN||19471112|M|||ADDRESS^^CITY^ST||(914)633-7700|||||263334|123-45-6789
ORC|NW|LL02-194182||||||||||455^JONES^JOHN
OBR||LL02-194182|(963)232-25AF|71020^CHEST PA 
LAT||20020920||||||||||455^JONES^JOHN|(914)632-9422
----------------------------------------------------------

returned message:

----------------------------------------------------------
MSH|^~\&|ADS|LL|PSCRIBE||200209181134||ORM^O01|2|P|2.3
PID|||263334||SMITH^JOHN||19471112|M|||ADDRESS^^CITY^ST||(914)633-7700|||||263334|123-45-6789
ORC|NW|LL02-194182||||||||||455^JONES^JOHN
------------------------------------------------------------


The OBR segment is missing. When I look at the XML, it starts with <RDO_O01>

I know the RDO^O01 and ORM^O01 issue has been brought up here, but I 
didn't see a solution and don't know if it would cause the problem above.

Any advice?

Thanks,


-- 
Eric Freed
IT Manager
New Rochelle Radiology
914-633-7700 x339

[HAPI-devel] a semantic cache that works with HAPI

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

This is a little off-topic, but roughly the same people who brought you =
HAPI
have released a semantic cache for Java.  It works with HAPI of course =
...
in fact we are using it to cache HL7 query results, although it will run
against any Java method that encapsulates a conjunctive query.=20

For those interested, here is the site: =
http://chisel-cache.sourceforge.net/

Bryan=20

Re: [HAPI-devel] Building message

[Steve H. <ste...@gm...>]

Sarah,

Yes, you can build HL7 messages.  You need to first decide which HL7
version you want to use and then instantiate a "message" object.  If
you selected 2.4, for example, you would then create an instance of a
class under the package "ca.uhn.hl7v2.model.v24.message".

Basically, you can only set values for individual fields, the
lowest-level parts of a message.  To get there, you have to step
through a message to a group (see the "group" package), then to a
segment.  (In fact, you may need to traverse through multiple groups
before reaching a segment.)  You can set values of fields within a
segment.


-Steve


On Tue, 22 Feb 2005 06:47:08 +0000, fan yue <fan...@ho...> wrote:
> Hi,
> 
> I just started using HAPI and am not very farmiliar with it.  My question
> is, except for parsing an HL7 message, can we also build or construct an
> HL7 message using HAPI? Which package should I look into?
> 
> Thank you very much,
> 
> Sarah
> 
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real users.
> Discover which products truly live up to the hype. Start reading now.
> http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
> _______________________________________________
> Hl7api-devel mailing list
> Hl7...@li...
> https://lists.sourceforge.net/lists/listinfo/hl7api-devel
>

RE: [HAPI-devel] Building message

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

Hi Sarah,=20

Yes, like this ...=20

//1. create a Message object with the structure you need, e.g. ADT_A01
ADT_A01 message =3D new ADT_A01();=20

//2. Set its values using getters/setters
message.getMSH().getSendingApplication().getNamespaceID().setValue("my
app");=20

// ... or using Terser ...=20
Terser terser =3D new Terser(message);
terser.set("/MSH-3-1", "my app");

//3. Encode the message using a Parser
PipeParser parser =3D new PipeParser();
String encodedMessage =3D parser.encode(message);

//4. Then you can send it somewhere=20
Connection conn =3D new Connection(parser, new MinLowerLayerProtocol(), =
new
Socket(host, port));
Message response =3D conn.getInitiator().sendAndReceive(message);

Bryan=20

-----Original Message-----
From: hl7...@li... on behalf of fan yue
Sent: Tue 2/22/2005 1:47 AM
To: hl7...@li...
Subject: [HAPI-devel] Building message
=20
Hi,

I just started using HAPI and am not very farmiliar with it.  My =
question=20
is, except for parsing an HL7 message, can we also build or construct an =

HL7 message using HAPI? Which package should I look into?

Thank you very much,

Sarah




-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=3D6595&alloc_id=3D14396&op=3Dclick
_______________________________________________
Hl7api-devel mailing list
Hl7...@li...
https://lists.sourceforge.net/lists/listinfo/hl7api-devel

[HAPI-devel] Building message

[fan y. <fan...@ho...>]

Hi,

I just started using HAPI and am not very farmiliar with it.  My question 
is, except for parsing an HL7 message, can we also build or construct an 
HL7 message using HAPI? Which package should I look into?

Thank you very much,

Sarah

RE: [HAPI-devel] TN datatype error during parse

[Shrock, C. <Sh...@in...>]

Many thanks, Martin!

-----Original Message-----
From: Martin Fleurke [mailto:mar...@po...] 
Sent: Tuesday, January 18, 2005 1:31 AM
To: hl7...@li...
Subject: Re: [HAPI-devel] TN datatype error during parse


Shrock, Court wrote:

>On a side note, I have noticed that the connection cleaner defined in 
>HL7Service doesn't seem to be doing it's job.  I haven't looked 
>further, so I am mainly curious if anyone else has noticed similar 
>things.
>  
>
I have reported some bugs regarding the connection cleaner in may last 
year. I have described how to fix it. You can find the bug reports on 
sourceforge.

I wonder if and when these fixes are added to the HAPI.... Bryan?

Regards,

Martin Fleurke


-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE
limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE --
well, almost....http://www.thinkgeek.com/sfshirt
_______________________________________________
Hl7api-devel mailing list
Hl7...@li...
https://lists.sourceforge.net/lists/listinfo/hl7api-devel

RE: [HAPI-devel] TN datatype error during parse

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

Hi Martin,=20

Thank you, they are very nice bug reports!  But no, I haven't made the
fixes.  We are long overdue for a bug fix release.  I have been tied up =
with
other committments for several months actually.  However, I'm happy to =
say
that I will have some time in the immediate future to devote to HAPI
maintenance.  Thank you for your patience, and I'm sorry about the long
delay. =20

Bryan=20

-----Original Message-----
From: hl7...@li... on behalf of Martin =
Fleurke
Sent: Tue 1/18/2005 4:30 AM
To: hl7...@li...
Subject: Re: [HAPI-devel] TN datatype error during parse
=20
Shrock, Court wrote:

>On a side note, I have noticed that the connection cleaner defined in
>HL7Service doesn't seem to be doing it's job.  I haven't looked =
further, so
>I am mainly curious if anyone else has noticed similar things.
> =20
>
I have reported some bugs regarding the connection cleaner in may last=20
year. I have described how to fix it. You can find the bug reports on=20
sourceforge.

I wonder if and when these fixes are added to the HAPI.... Bryan?

Regards,

Martin Fleurke


-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
_______________________________________________
Hl7api-devel mailing list
Hl7...@li...
https://lists.sourceforge.net/lists/listinfo/hl7api-devel

Re: [HAPI-devel] TN datatype error during parse

[Martin F. <mar...@po...>]

Shrock, Court wrote:

>On a side note, I have noticed that the connection cleaner defined in
>HL7Service doesn't seem to be doing it's job.  I haven't looked further, so
>I am mainly curious if anyone else has noticed similar things.
>  
>
I have reported some bugs regarding the connection cleaner in may last 
year. I have described how to fix it. You can find the bug reports on 
sourceforge.

I wonder if and when these fixes are added to the HAPI.... Bryan?

Regards,

Martin Fleurke

Re: [HAPI-devel] TN datatype error during parse

[Archie C. <ar...@de...>]

Shrock, Court wrote:
> On a side note, I have noticed that the connection cleaner defined in
> HL7Service doesn't seem to be doing it's job.  I haven't looked further, so
> I am mainly curious if anyone else has noticed similar things.

What symptom are you seeing that causes you to say this?

Thanks,
-Archie

__________________________________________________________________________
Archie Cobbs      *        CTO, Awarix        *      http://www.awarix.com

[HAPI-devel] TN datatype error during parse

[Shrock, C. <Sh...@in...>]

ca.uhn.hl7v2.model.DataTypeException: The value of the TN datatype does not
conform to an allowable format. Format should conform to [NNN]
[(999)]999-9999[X99999][B99999][C any text]: Segment: PID (rep 0) Field #13
	at
ca.uhn.hl7v2.model.primitive.CommonTN.setValidValue(CommonTN.java:242)
	at ca.uhn.hl7v2.model.primitive.CommonTN.setValue(CommonTN.java:114)
	at ca.uhn.hl7v2.model.v23.datatype.TN.setValue(TN.java:77)
	at ca.uhn.hl7v2.parser.PipeParser.parse(PipeParser.java:363)
	at ca.uhn.hl7v2.parser.PipeParser.parse(PipeParser.java:312)
	at ca.uhn.hl7v2.parser.PipeParser.parse(PipeParser.java:264)
	at ca.uhn.hl7v2.app.Responder.processMessage(Responder.java:139)
	at ca.uhn.hl7v2.app.Receiver$Grunt.run(Receiver.java:120)

The cause was PID-13 of "509 555-1212 CELL" instead of the expected format
of "509 555-1212C CELL".  Simple problem, but a pain because the exception
that is generated kills the responder, which kills the receiver, which kills
the connection.

On a side note, I have noticed that the connection cleaner defined in
HL7Service doesn't seem to be doing it's job.  I haven't looked further, so
I am mainly curious if anyone else has noticed similar things.

Sorry for the dupe, Bryan; I realized that I emailed you directly instead of
the list.

-Court

RE: [HAPI-devel] HAPI 0.42

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

Hi Ed,=20

Apologies ... HAPI doesn't support HL7 version 2.1 very well.  If you =
change
the version to 2.2 it will parse.  If this doesn't work for you, let me =
know
and I'll see what I can do. =20

Bryan=20


-----Original Message-----
From: hl7...@li... on behalf of Ed
Sent: Wed 1/12/2005 1:07 PM
To: hl7...@li...
Subject: [HAPI-devel] HAPI 0.42
=20
When trying to Parse a file using HAPI 0.4.2 Test Panel, I receive the
following:

Java.lang.ClassCastExcxeption trying to set data type of OBX-5.

Here is the file:
MSH|^~\&|COSTELLO|ORCHARD
SOFTWARE|MEGAREG|UABHOSPC|20040221112417||ORU^R01|325|P|2.1
PID|1|3566|3566||SUNLIGHT^CREE||19790701|F|||14987 Pixie Pt
Cir^^Naperville^IL^00000||||||||
OBR|1|27102|58|CMETABOLIC^CMetabol|R||20040221112415|||^Bahamonde^Toodie
||||200402211124||D1^Welby^Marcus||||||200402211124|||F||||||||||
OBX|1|NM|2823-3^K+||3.3|MMOL/L|3.5-5.5||||F

As you can see, OBX-2 states that it is a Numeric data type.  OBX-5 is
3.3, which is a Numeric data type.
Can you tell me what is wrong?

Ed Salvador Jr.
WD Net, Inc.

RE: [HAPI-devel] Z-segments

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

Another comment ... the parser will add the segment itself, but has to =
guess
where to put it.    It puts it at the end of the message branch it's on =
when
the Z-segment is encountered.  For this message, it goes under
ADR_A19_PR1ROL.  You can see this by displaying the message in =
TestPanel.=20

Bryan=20


-----Original Message-----
From: hl7...@li... on behalf of Shrock, =
Court
Sent: Sat 1/15/2005 4:45 PM
To: 'Daniel Nebot'; hl7...@li...
Subject: RE: [HAPI-devel] Z-segments
=20
You will find the start of the trail in the model/v24/message/ADR_A19 =
class
constructor.  Notice how segments and groups are added by calling
this.add(MSH.class, b_required, b_repeating)?  Either add a line that =
adds
your custom Z segment to the base message or to whichever group it =
belongs.
If you want to add to the base message, add something like the following
just under the this.add(DSC.class) line:

this.add(Z.class, true, false);


Hope this helps....I actually just ran into a system (Meditech) that =
says it
is outputting hl7v2.2, but contains an RDE message type in MSH9 with no
event trigger value which isn't in v.2.2 and isn't valid anyway in v2.3
because of the missing event trigger component.  I ended up creating my =
own
AbstractMessage extended class to handle this message type.

-----Original Message-----
From: Daniel Nebot [mailto:dan...@ya...]=20
Sent: Thursday, January 13, 2005 7:38 AM
To: hl7...@li...
Subject: [HAPI-devel] Z-segments


I am new to HAPI and am trying to parse an incoming pipe-formatted =
ADR_A19
response which includes an extra custom Z segment. Unfortunatelly, as =
far as
I see the PipeParser seems to ignore the Z segment and I cannot find it =
on
the resulting Message object.

I would be very grateful if somebody could post an example of how to =
manage
Z-messages and additional Z-segments in messages with HAPI.

Thanks
Dani

MSH|^~\&|sendApp|sendingFacility|rcvIngApp|rcvingFacility|200501101922||
MSH|^^ADR_A19|FAKEMSGID|P|2.4
PID|||||GRIJANDER^DANIEL|GARCIA||M|||&Sol i
Padris,120^^SABADELL^^08205^^CALLE||||||||||||BARCELONA
PD1|||||||||||E|Y
PV1||N
ZNB|DIA1^DOSIS1|DIA2^DOSIS2|DIA3^DOSIS3



-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE
limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and =
FREE --
well, almost....http://www.thinkgeek.com/sfshirt
_______________________________________________
Hl7api-devel mailing list
Hl7...@li...
https://lists.sourceforge.net/lists/listinfo/hl7api-devel


-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
_______________________________________________
Hl7api-devel mailing list
Hl7...@li...
https://lists.sourceforge.net/lists/listinfo/hl7api-devel