RE: [HAPI-devel] TXA segment in ORU message

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

Hi Matthew, 

There are a couple of ways to do this, but the simplest is to use
Group.addNonstandardSegment(String name).  For example: 

ORU_R01 r01 = new ORU_R01; 
r01.addNonstandardSegment("TXA");
//then access it like this ... 
TXA txa = (TXA) ro1.get("TXA");

Another option is to create a custom message class, but that is more
involved.  If you would like details let me know.  

Best, 
Bryan 

-----Original Message-----
From: mg...@mc...
To: hl7...@li...
Sent: 09/05/2004 3:44 PM
Subject: [HAPI-devel] TXA segment in ORU message

Folks,

I need to send pathology reports to an application which unfortunately
expects them in a rather peculiar format. The message is supposed to
include a TXA segment (followed by multiple OBX segments of type TX, one
for each paragraph in the report; sheesh). Anyhow, I am new to HAPI and
would appreciate some guidance as to how to include the TXA segment in
the
ORU message. I can see that there is a TXA class, but it is apparently
not
possible to obtain an instance of this class by calling any of the
ORU_R01
class' get... methods.

Thanks very much!

Matthew Fleming, MD
Laboratory of Dermatopathology
Dept. of Dermatology
Medical College of Wisconsin
Milwaukee, WI
mg...@mc...


-------------------------------------------------------
This SF.Net email is sponsored by Sleepycat Software
Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to 
deliver higher performing products faster, at low TCO.
http://www.sleepycat.com/telcomwpreg.php?From=osdnemail3
_______________________________________________
Hl7api-devel mailing list
Hl7...@li...
https://lists.sourceforge.net/lists/listinfo/hl7api-devel


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.