hl7api-devel — developer list

[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

RE: [HAPI-devel] hapi 0.4.3 & pid alternate patient id

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

No, the text version of the standard says it should repeat, so I'll =
change
it. =20

Bryan=20

-----Original Message-----
From: hl7...@li... on behalf of Alan Shields
Sent: Wed 3/30/2005 4:00 PM
To: hl7...@li...
Subject: [HAPI-devel] hapi 0.4.3 & pid alternate patient id
=20
Hi

I just downloaded 0.4.3 and I notice that the data model for 2.3=20
defines PID:4 (alternate patient id) as a non repeating field.

Is this correct?

Cheers
Alan Shields
ma...@as...



-------------------------------------------------------
This SF.net email is sponsored by Demarc:
A global provider of Threat Management Solutions.
Download our HomeAdmin security software for free today!
http://www.demarc.com/info/Sentarus/hamr30
_______________________________________________
Hl7api-devel mailing list
Hl7...@li...
https://lists.sourceforge.net/lists/listinfo/hl7api-devel

[HAPI-devel] hapi 0.4.3 & pid alternate patient id

[Alan S. <ma...@as...>]

Hi

I just downloaded 0.4.3 and I notice that the data model for 2.3 
defines PID:4 (alternate patient id) as a non repeating field.

Is this correct?

Cheers
Alan Shields
ma...@as...

Re: [HAPI-devel] HAPI Logging

[Tom Le <to...@te...>]

From the method call and doc, the parameter is a logical name for a log
file.

I think!!!

fan yue wrote:

> Shrock,
>
> Thanks for that. But the following problem is still there,
>
>> Also I notice in the 'sendAndReceive' method, two HapiLog objects are
>> instantiated like this
>>
>> HapiLog rawOutbound =
>> HapiLogFactory.getHapiLog("ca.uhn.hl7v2.raw.outbound");
>> HapiLog rawInbound =
>> HapiLogFactory.getHapiLog("ca.uhn.hl7v2.raw.inbound");
>>
>> But under the installation directory of my HAPI, I could not find 
>
> directory
>
>> 'raw', I wonder what it is used for and whether my copy of HAPI is
>> correct
>> and complete.
>
>
> Does anyone know the answer? I am waiting for it...
>
> Thank you,
>
> Sarah
>
>
>> From: "Shrock, Court" <Sh...@in...>
>> To: 'fan yue' <fan...@ho...>, Bry...@uh..., 
>
> hl7...@li...
>
>> Subject: RE: [HAPI-devel] HAPI Logging
>> Date: Tue, 29 Mar 2005 08:26:11 -0800
>>
>> You need to tell log4j where it's config file is; and that is done when 
>
> you
>
>> start the process:
>> java -Dlog4j.configuration=log4j.xml -jar sendAndReceive.jar
>>
>> -----Original Message-----
>> From: fan yue [mailto:fan...@ho...]
>> Sent: Tuesday, March 29, 2005 12:01 AM
>> To: Bry...@uh...; hl7...@li...
>> Cc: fan...@ho...
>> Subject: [HAPI-devel] HAPI Logging
>>
>> Hello,
>>
>> I have implemented a class in which the method 'sendAndReceive' of 
>
> Initiator
>
>> class is called. I always got a message, in my IDE console, like this,
>>
>> log4j:WARN No appenders could be found for logger
>> (ca.uhn.hl7v2.app.Initiator).
>> log4j:WARN Please initialize the log4j system properly.
>>
>> Do I need to do extra configuration to make log4j work? Because
>> currently
>> the logging system does not work.
>>
>> Also I notice in the 'sendAndReceive' method, two HapiLog objects are
>> instantiated like this
>>
>> HapiLog rawOutbound =
>> HapiLogFactory.getHapiLog("ca.uhn.hl7v2.raw.outbound");
>> HapiLog rawInbound =
>> HapiLogFactory.getHapiLog("ca.uhn.hl7v2.raw.inbound");
>>
>> But under the installation directory of my HAPI, I could not find 
>
> directory
>
>> 'raw', I wonder what it is used for and whether my copy of HAPI is
>> correct
>> and complete.
>>
>> Thank you,
>>
>> Sarah
>>
>> >From: "Tripp, Bryan" <Bry...@uh...>
>> >To: "fan yue"
>> <fan...@ho...>,<hl7...@li...>
>> >Subject: RE: [HAPI-devel] Building message
>> >Date: Tue, 22 Feb 2005 10:47:15 -0500
>> >
>> >Hi Sarah,
>> >
>> >Yes, like this ...
>> >
>> >//1. create a Message object with the structure you need, e.g. ADT_A01
>> >ADT_A01 message = new ADT_A01();
>> >
>> >//2. Set its values using getters/setters
>> >message.getMSH().getSendingApplication().getNamespaceID().setValue("my
>> >app");
>> >
>> >// ... or using Terser ...
>> >Terser terser = new Terser(message);
>> >terser.set("/MSH-3-1", "my app");
>> >
>> >//3. Encode the message using a Parser
>> >PipeParser parser = new PipeParser();
>> >String encodedMessage = parser.encode(message);
>> >
>> >//4. Then you can send it somewhere
>> >Connection conn = new Connection(parser, new MinLowerLayerProtocol(),
>> >new Socket(host, port)); Message response =
>> >conn.getInitiator().sendAndReceive(message);
>> >
>> >Bryan
>> >
>> >-----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
>> >
>> >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
>> >
>>
>>
>>
>>
>> -------------------------------------------------------
>> 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_id=6595&alloc_id=14396&op=click
> _______________________________________________
> Hl7api-devel mailing list
> Hl7...@li...
> https://lists.sourceforge.net/lists/listinfo/hl7api-devel
>

RE: [HAPI-devel] HAPI Logging

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

Shrock,

Thanks for that.  But the following problem is still there,

>Also I notice in the 'sendAndReceive' method, two HapiLog objects are
>instantiated like this
>
>  HapiLog rawOutbound =
>HapiLogFactory.getHapiLog("ca.uhn.hl7v2.raw.outbound");
>  HapiLog rawInbound =
>HapiLogFactory.getHapiLog("ca.uhn.hl7v2.raw.inbound");
>
>But under the installation directory of my HAPI, I could not find 
directory
>'raw', I wonder what it is used for and whether my copy of HAPI is correct
>and complete.

Does anyone know the answer?  I am waiting for it...

Thank you,

Sarah


>From: "Shrock, Court" <Sh...@in...>
>To: 'fan yue' <fan...@ho...>, Bry...@uh..., 
hl7...@li...
>Subject: RE: [HAPI-devel] HAPI Logging
>Date: Tue, 29 Mar 2005 08:26:11 -0800
>
>You need to tell log4j where it's config file is; and that is done when 
you
>start the process:
>java -Dlog4j.configuration=log4j.xml -jar sendAndReceive.jar
>
>-----Original Message-----
>From: fan yue [mailto:fan...@ho...]
>Sent: Tuesday, March 29, 2005 12:01 AM
>To: Bry...@uh...; hl7...@li...
>Cc: fan...@ho...
>Subject: [HAPI-devel] HAPI Logging
>
>Hello,
>
>I have implemented a class in which the method 'sendAndReceive' of 
Initiator
>class is called.  I always got a message, in my IDE console, like this,
>
>log4j:WARN No appenders could be found for logger
>(ca.uhn.hl7v2.app.Initiator).
>log4j:WARN Please initialize the log4j system properly.
>
>Do I need to do extra configuration to make log4j work?  Because currently
>the logging system does not work.
>
>Also I notice in the 'sendAndReceive' method, two HapiLog objects are
>instantiated like this
>
>  HapiLog rawOutbound =
>HapiLogFactory.getHapiLog("ca.uhn.hl7v2.raw.outbound");
>  HapiLog rawInbound =
>HapiLogFactory.getHapiLog("ca.uhn.hl7v2.raw.inbound");
>
>But under the installation directory of my HAPI, I could not find 
directory
>'raw', I wonder what it is used for and whether my copy of HAPI is correct
>and complete.
>
>Thank you,
>
>Sarah
>
> >From: "Tripp, Bryan" <Bry...@uh...>
> >To: "fan yue"
><fan...@ho...>,<hl7...@li...>
> >Subject: RE: [HAPI-devel] Building message
> >Date: Tue, 22 Feb 2005 10:47:15 -0500
> >
> >Hi Sarah,
> >
> >Yes, like this ...
> >
> >//1. create a Message object with the structure you need, e.g. ADT_A01
> >ADT_A01 message = new ADT_A01();
> >
> >//2. Set its values using getters/setters
> >message.getMSH().getSendingApplication().getNamespaceID().setValue("my
> >app");
> >
> >// ... or using Terser ...
> >Terser terser = new Terser(message);
> >terser.set("/MSH-3-1", "my app");
> >
> >//3. Encode the message using a Parser
> >PipeParser parser = new PipeParser();
> >String encodedMessage = parser.encode(message);
> >
> >//4. Then you can send it somewhere
> >Connection conn = new Connection(parser, new MinLowerLayerProtocol(),
> >new Socket(host, port)); Message response =
> >conn.getInitiator().sendAndReceive(message);
> >
> >Bryan
> >
> >-----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
> >
> >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
> >
>
>
>
>
>-------------------------------------------------------
>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] question

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

Thanks Steve.  A few comments further to this ... 1) the method is
Group.addNonStandardSegment(), 2) this doesn't help for incoming =
messages,
however HAPI will automatically parse unexpected segments in incoming
messages into instances of GenericSegment, 3) you can use the code for =
the
standard messages as an example for writing a custom message class; see =
the
ca.uhn.hl7v2.parser.Parser javadocs for instructions on registering your
custom message classes with HAPI.=20

Bryan=20


-----Original Message-----
From: hl7...@li... on behalf of Steve =
Holdener
Sent: Tue 3/29/2005 7:57 PM
To: Alfredo Cancio
Cc: hl7...@li...
Subject: Re: [HAPI-devel] question
=20
Alfredo,

In HL7, segment types beginning with "Z" are reserved for custom
segments, outside the spec.  I believe you need to add a non-standard
segment to your message or group (I think there's a method
specifically for this).

There are a couple other options, as well.  If you're message is
pretty "flat" (no repeating groups), you can probably use the Terser
class to add your Z-segments.

You can also define your own message type, complete with groups, if
you have several of these segments, include repeating groups, or want
some kind of enforcement of required Z-segments.


-Steve


On Thu, 24 Mar 2005 09:24:14 -0300, Alfredo Cancio
<alf...@ho...> wrote:
> =20
> =20
> Dear Bryan,=20
> We are trying to implement your HAPI v2.4 and we need messages Zxx.=20
> Is this possible? How?=20
>  =20
> Thanks you.=20
>  =20
> Alfredo Cancio=20
> Hospital Italiano de Buenos Aires=20
> Argentina


-------------------------------------------------------
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] question

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

Alfredo,

In HL7, segment types beginning with "Z" are reserved for custom
segments, outside the spec.  I believe you need to add a non-standard
segment to your message or group (I think there's a method
specifically for this).

There are a couple other options, as well.  If you're message is
pretty "flat" (no repeating groups), you can probably use the Terser
class to add your Z-segments.

You can also define your own message type, complete with groups, if
you have several of these segments, include repeating groups, or want
some kind of enforcement of required Z-segments.


-Steve


On Thu, 24 Mar 2005 09:24:14 -0300, Alfredo Cancio
<alf...@ho...> wrote:
>  
>  
> Dear Bryan, 
> We are trying to implement your HAPI v2.4 and we need messages Zxx. 
> Is this possible? How? 
>   
> Thanks you. 
>   
> Alfredo Cancio 
> Hospital Italiano de Buenos Aires 
> Argentina

RE: [HAPI-devel] HAPI Logging

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

You need to tell log4j where it's config file is; and that is done when you
start the process:
java -Dlog4j.configuration=log4j.xml -jar sendAndReceive.jar

-----Original Message-----
From: fan yue [mailto:fan...@ho...] 
Sent: Tuesday, March 29, 2005 12:01 AM
To: Bry...@uh...; hl7...@li...
Cc: fan...@ho...
Subject: [HAPI-devel] HAPI Logging

Hello,

I have implemented a class in which the method 'sendAndReceive' of Initiator
class is called.  I always got a message, in my IDE console, like this,

log4j:WARN No appenders could be found for logger
(ca.uhn.hl7v2.app.Initiator).
log4j:WARN Please initialize the log4j system properly.

Do I need to do extra configuration to make log4j work?  Because currently
the logging system does not work.

Also I notice in the 'sendAndReceive' method, two HapiLog objects are
instantiated like this

 HapiLog rawOutbound =
HapiLogFactory.getHapiLog("ca.uhn.hl7v2.raw.outbound");
 HapiLog rawInbound =
HapiLogFactory.getHapiLog("ca.uhn.hl7v2.raw.inbound");

But under the installation directory of my HAPI, I could not find directory
'raw', I wonder what it is used for and whether my copy of HAPI is correct
and complete.

Thank you,

Sarah

>From: "Tripp, Bryan" <Bry...@uh...>
>To: "fan yue" 
<fan...@ho...>,<hl7...@li...>
>Subject: RE: [HAPI-devel] Building message
>Date: Tue, 22 Feb 2005 10:47:15 -0500
>
>Hi Sarah,
>
>Yes, like this ...
>
>//1. create a Message object with the structure you need, e.g. ADT_A01
>ADT_A01 message = new ADT_A01();
>
>//2. Set its values using getters/setters 
>message.getMSH().getSendingApplication().getNamespaceID().setValue("my
>app");
>
>// ... or using Terser ...
>Terser terser = new Terser(message);
>terser.set("/MSH-3-1", "my app");
>
>//3. Encode the message using a Parser
>PipeParser parser = new PipeParser();
>String encodedMessage = parser.encode(message);
>
>//4. Then you can send it somewhere
>Connection conn = new Connection(parser, new MinLowerLayerProtocol(), 
>new Socket(host, port)); Message response = 
>conn.getInitiator().sendAndReceive(message);
>
>Bryan
>
>-----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
>
>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
>




-------------------------------------------------------
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] HAPI Logging

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

Hello,

I have implemented a class in which the method 'sendAndReceive' of 
Initiator class is called.  I always got a message, in my IDE console, like 
this,

log4j:WARN No appenders could be found for logger 
(ca.uhn.hl7v2.app.Initiator).
log4j:WARN Please initialize the log4j system properly.

Do I need to do extra configuration to make log4j work?  Because currently 
the logging system does not work.

Also I notice in the 'sendAndReceive' method, two HapiLog objects are 
instantiated like this

 HapiLog rawOutbound = 
HapiLogFactory.getHapiLog("ca.uhn.hl7v2.raw.outbound");
 HapiLog rawInbound = 
HapiLogFactory.getHapiLog("ca.uhn.hl7v2.raw.inbound");

But under the installation directory of my HAPI, I could not find directory 
'raw', I wonder what it is used for and whether my copy of HAPI is correct 
and complete.

Thank you,

Sarah

>From: "Tripp, Bryan" <Bry...@uh...>
>To: "fan yue" 
<fan...@ho...>,<hl7...@li...>
>Subject: RE: [HAPI-devel] Building message
>Date: Tue, 22 Feb 2005 10:47:15 -0500
>
>Hi Sarah,
>
>Yes, like this ...
>
>//1. create a Message object with the structure you need, e.g. ADT_A01
>ADT_A01 message = new ADT_A01();
>
>//2. Set its values using getters/setters
>message.getMSH().getSendingApplication().getNamespaceID().setValue("my
>app");
>
>// ... or using Terser ...
>Terser terser = new Terser(message);
>terser.set("/MSH-3-1", "my app");
>
>//3. Encode the message using a Parser
>PipeParser parser = new PipeParser();
>String encodedMessage = parser.encode(message);
>
>//4. Then you can send it somewhere
>Connection conn = new Connection(parser, new MinLowerLayerProtocol(), new
>Socket(host, port));
>Message response = conn.getInitiator().sendAndReceive(message);
>
>Bryan
>
>-----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
>
>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
>

[HAPI-devel] HAPI Logging

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

Hi,

I have implemented a class in which the 'sendAndReceive' method of 
'Initiator.java' is called.  And I always got a message in my IDE's console

log4j:WARN No appenders could be found for logger 
(ca.uhn.hl7v2.app.Initiator).
log4j:WARN Please initialize the log4j system properly.

Do I need to do some extra configuration for log4j?  

I also noticed that in the 'sendAndReceive' method, two HapiLog objects are 
instantiated like this,

 HapiLog rawOutbound = 
HapiLogFactory.getHapiLog("ca.uhn.hl7v2.raw.outbound");
 HapiLog rawInbound = 
HapiLogFactory.getHapiLog("ca.uhn.hl7v2.raw.inbound");

but I could not find the directory 'raw' under the directory where HAPI is 
installed.  Does that mean something is missing in my copy of HAPI?

Thanks,

Sarah

[HAPI-devel] Timezone issue in the TM datatype (HAPI 0.4.3)

[Riemer, R. \(GE Healthcare\) <Ric...@me...>]

Hi,

I'm a software engineer with GE Healthcare IT, and am currently using =
HAPI 0.4.3 for an application we're developing.
I stumbled onto an issue with representing timezones in TM datatypes, =
for which I'd like to get some feedback.

I'm using the TM.toHl7TMFormat() method as follows:
java.util.Date date =3D new =
SimpleDateFormat("yyyyMMddHHmmssZ").parse("19740805000000+0000");
GregorianCalender cal =3D new GregorianCalender();
cal.setTime(date);
return DT.toHl7DTFormat(cal) + TM.toHl7TMFormat(cal);

If I run this piece of code in different timezones, different values are =
returned:
*	When run in CET 25-March-2005 (Central European Time, UTC+1): =
19740805010000+0100
This seems to be OK. It is the same time, displayed in the local =
timezone
*	When run in CEST 25-April-2005 (Central European Summer Time, UTC+2): =
19740805010000+0100
Still OK, but the time is displayed as winter time, instead of in =
daylight saving time
*	When run in CST (Central Standard Time, UTC-6): 19740804190000-0600
This seems to be wrong. The timezone -0600 is OK, but the time should be =
180000-0600 here, instead of 190000-0600.
*	When run in CDT (Central Daylight Time, UTC-5): 19740804190000-0600
This seems to be wrong as well. The time should be either 19000000-0500 =
or 180000-0600.

Am I correct in my assumptions that:
*	the time is incorrect for some timezones (CST and CDT)?
*	the timezone should reflect the daylight saving time, so in CST we =
should se 020000+0200 instead of 010000+0100?

Any help would be appreciated. I'd like to know if I should submit bugs =
for any or both of my assumptions.

Thanks,

Rick Riemer
Software Engineer
Core Infrastructure Platforms
GE Healthcare IT

T +31 30 692 6000
F +31 30 692 6010
D *381 6427
E ric...@me...
www.gehealthcare.com

[HAPI-devel] question

[Alfredo C. <alf...@ho...>]

Dear Bryan,
We are trying to implement your HAPI v2.4 and we need messages Zxx.
Is this possible? How?

Thanks you.

Alfredo Cancio=20
Hospital Italiano de Buenos Aires
Argentina

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

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

Thanks Aris,
                       The Problem is resolved.I am getting ORM_O01 after parsing
  
 
Thanks a lot.It's working fine.
Thanks Steven for ur suggestion.
 
The Problem is resolved.I am getting ORM_O01 after parsing
 
If any body has latest source for HAPI hl7 v2.5 pls send it across to me or is there a way to access it.???If so Pls tell me How to do it???
 
Waiting for ur reply
 
Regards
Praveen Kumar.A



Aris JAVIER RAMOS <Ari...@hc...> wrote:yes the archive is hapi-0.4.2.jar

You must uncompress the entire archive before (with winzip letting the option user folder names).
go to the file to modifie. and after modification compress it again, it will create à .zip file, you can change
the .zip in .jar.

have you let the line mapping ORM_O01 ORM_O01 uncommented ?

regards

Aris

>>> Praveen Kumar 
03/22 2:15 >>>
Hi All,
Iin which jar file i need to comment the lines.
is it in hapi-0.4.2.jar????
I have changed 2.3.1 .properties in the jar file.
After I changed the .properties file as per ur instructuions.it gave me that folder will be lost.

After that I ran the same program which I had sent earlier .
It is giving the following error.


log4j:WARN No appenders could be found for logger (ca.uhn.hl7v2.parser.Parser).

log4j:WARN Please initialize the log4j system properly.

ca.uhn.hl7v2.HL7Exception: Couldn't create Message object of type ORM_O01

at ca.uhn.hl7v2.parser.PipeParser.parse(PipeParser.java:218)

at org.srit.hl7.TestORM.main(TestORM.java:34)

Caused by: ca.uhn.hl7v2.HL7Exception: No map found for version 2.3.1

at ca.uhn.hl7v2.parser.Parser.getMessageStructureForEvent(Parser.java:390)

at ca.uhn.hl7v2.parser.Parser.findMessageClass(Parser.java:263)

at ca.uhn.hl7v2.parser.PipeParser.parse(PipeParser.java:205)

... 1 more

java.lang.NullPointerException

at org.srit.hl7.TestORM.main(TestORM.java:43)

Exception in thread "main" 



What is the correct way of modfiying the file.

Please give me the proper steps t make the below changes .

Hoping for a early Reply



Regards

Praveen

Aris JAVIER RAMOS wrote:
Hello,

When I frist came to the Hapi distribution list, I had the same problem than you
I was using the parse HAPI 0.4.2.

To solve my problem I modified the jar archive of api.

In thad jar i found à text file called ca/uhn/hl7v2/parser/eventmap/2.3.properties
(I was using the 2.3 version of the HL7 norm) and i modified this sequence of line :
ORM_O01 ORM_O01
ORM_O01 OMD_O01
ORM_O01 OMN_O01
ORM_O01 OMS_O01
ORM_O01 RDO_O01 <---
like this :
ORM_O01 ORM_O01
#ORM_O01 OMD_O01
#ORM_O01 OMN_O01
#ORM_O01 OMS_O01
#ORM_O01 RDO_O01

and it worked

good look.

Aris

PS if you are using 2.3.1 version, modifie the file "2.3.1.properties" and so on.

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

>>> Praveen Kumar 
03/22 11:21 >>>

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




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


		
---------------------------------
Do you Yahoo!?
 Read only the mail you want - Yahoo! Mail SpamGuard.

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

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

Thanks Aris,
                       The Problem is resolved.I am getting ORM_O01 after parsing
  
 
Thanks a lot.It's working fine.
Thanks Steven for ur suggestion.
 
The Problem is resolved.I am getting ORM_O01 after parsing
 
If any body has latest source for HAPI hl7 v2.5 pls send it across to me or is there a way to access it.???If so Pls tell me How to do it???
 
Waiting for ur reply
 
Regards
Praveen Kumar.A

Aris JAVIER RAMOS <Ari...@hc...> wrote:
yes the archive is hapi-0.4.2.jar

You must uncompress the entire archive before (with winzip letting the option user folder names).
go to the file to modifie. and after modification compress it again, it will create à .zip file, you can change
the .zip in .jar.

have you let the line mapping ORM_O01 ORM_O01 uncommented ?

regards

Aris

>>> Praveen Kumar 
03/22 2:15 >>>
Hi All,
Iin which jar file i need to comment the lines.
is it in hapi-0.4.2.jar????
I have changed 2.3.1 .properties in the jar file.
After I changed the .properties file as per ur instructuions.it gave me that folder will be lost.

After that I ran the same program which I had sent earlier .
It is giving the following error.


log4j:WARN No appenders could be found for logger (ca.uhn.hl7v2.parser.Parser).

log4j:WARN Please initialize the log4j system properly.

ca.uhn.hl7v2.HL7Exception: Couldn't create Message object of type ORM_O01

at ca.uhn.hl7v2.parser.PipeParser.parse(PipeParser.java:218)

at org.srit.hl7.TestORM.main(TestORM.java:34)

Caused by: ca.uhn.hl7v2.HL7Exception: No map found for version 2.3.1

at ca.uhn.hl7v2.parser.Parser.getMessageStructureForEvent(Parser.java:390)

at ca.uhn.hl7v2.parser.Parser.findMessageClass(Parser.java:263)

at ca.uhn.hl7v2.parser.PipeParser.parse(PipeParser.java:205)

... 1 more

java.lang.NullPointerException

at org.srit.hl7.TestORM.main(TestORM.java:43)

Exception in thread "main" 



What is the correct way of modfiying the file.

Please give me the proper steps t make the below changes .

Hoping for a early Reply



Regards

Praveen

Aris JAVIER RAMOS wrote:
Hello,

When I frist came to the Hapi distribution list, I had the same problem than you
I was using the parse HAPI 0.4.2.

To solve my problem I modified the jar archive of api.

In thad jar i found à text file called ca/uhn/hl7v2/parser/eventmap/2.3.properties
(I was using the 2.3 version of the HL7 norm) and i modified this sequence of line :
ORM_O01 ORM_O01
ORM_O01 OMD_O01
ORM_O01 OMN_O01
ORM_O01 OMS_O01
ORM_O01 RDO_O01 <---
like this :
ORM_O01 ORM_O01
#ORM_O01 OMD_O01
#ORM_O01 OMN_O01
#ORM_O01 OMS_O01
#ORM_O01 RDO_O01

and it worked

good look.

Aris

PS if you are using 2.3.1 version, modifie the file "2.3.1.properties" and so on.

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

>>> Praveen Kumar 
03/22 11:21 >>>

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




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



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

Thanks Aris,
                       The Problem is resolved.I am getting ORM_O01 after parsing
  
 
Thanks a lot.It's working fine.
Thanks Steven for ur suggestion.
 
The Problem is resolved.I am getting ORM_O01 after parsing
 
If any body has latest source for HAPI hl7 v2.5 pls send it across to me or is there a way to access it.???If so Pls tell me How to do it???
 
Waiting for ur reply
 
Regards
Praveen Kumar.A

Aris JAVIER RAMOS <Ari...@hc...> wrote:
yes the archive is hapi-0.4.2.jar

You must uncompress the entire archive before (with winzip letting the option user folder names).
go to the file to modifie. and after modification compress it again, it will create à .zip file, you can change
the .zip in .jar.

have you let the line mapping ORM_O01 ORM_O01 uncommented ?

regards

Aris

>>> Praveen Kumar 
03/22 2:15 >>>
Hi All,
Iin which jar file i need to comment the lines.
is it in hapi-0.4.2.jar????
I have changed 2.3.1 .properties in the jar file.
After I changed the .properties file as per ur instructuions.it gave me that folder will be lost.

After that I ran the same program which I had sent earlier .
It is giving the following error.


log4j:WARN No appenders could be found for logger (ca.uhn.hl7v2.parser.Parser).

log4j:WARN Please initialize the log4j system properly.

ca.uhn.hl7v2.HL7Exception: Couldn't create Message object of type ORM_O01

at ca.uhn.hl7v2.parser.PipeParser.parse(PipeParser.java:218)

at org.srit.hl7.TestORM.main(TestORM.java:34)

Caused by: ca.uhn.hl7v2.HL7Exception: No map found for version 2.3.1

at ca.uhn.hl7v2.parser.Parser.getMessageStructureForEvent(Parser.java:390)

at ca.uhn.hl7v2.parser.Parser.findMessageClass(Parser.java:263)

at ca.uhn.hl7v2.parser.PipeParser.parse(PipeParser.java:205)

... 1 more

java.lang.NullPointerException

at org.srit.hl7.TestORM.main(TestORM.java:43)

Exception in thread "main" 



What is the correct way of modfiying the file.

Please give me the proper steps t make the below changes .

Hoping for a early Reply



Regards

Praveen

Aris JAVIER RAMOS wrote:
Hello,

When I frist came to the Hapi distribution list, I had the same problem than you
I was using the parse HAPI 0.4.2.

To solve my problem I modified the jar archive of api.

In thad jar i found à text file called ca/uhn/hl7v2/parser/eventmap/2.3.properties
(I was using the 2.3 version of the HL7 norm) and i modified this sequence of line :
ORM_O01 ORM_O01
ORM_O01 OMD_O01
ORM_O01 OMN_O01
ORM_O01 OMS_O01
ORM_O01 RDO_O01 <---
like this :
ORM_O01 ORM_O01
#ORM_O01 OMD_O01
#ORM_O01 OMN_O01
#ORM_O01 OMS_O01
#ORM_O01 RDO_O01

and it worked

good look.

Aris

PS if you are using 2.3.1 version, modifie the file "2.3.1.properties" and so on.

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

>>> Praveen Kumar 
03/22 11:21 >>>

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




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



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

Thanks Aris,
                       The Problem is resolved.I am getting ORM_O01 after parsing
  
 
Thanks a lot.It's working fine.
Thanks Steven for ur suggestion.
 
The Problem is resolved.I am getting ORM_O01 after parsing
 
If any body has latest source for HAPI hl7 v2.5 pls send it across to me or is there a way to access it.???If so Pls tell me How to do it???
 
Waiting for ur reply
 
Regards
Praveen Kumar.A

Aris JAVIER RAMOS <Ari...@hc...> wrote:
yes the archive is hapi-0.4.2.jar

You must uncompress the entire archive before (with winzip letting the option user folder names).
go to the file to modifie. and after modification compress it again, it will create à .zip file, you can change
the .zip in .jar.

have you let the line mapping ORM_O01 ORM_O01 uncommented ?

regards

Aris

>>> Praveen Kumar 
03/22 2:15 >>>
Hi All,
Iin which jar file i need to comment the lines.
is it in hapi-0.4.2.jar????
I have changed 2.3.1 .properties in the jar file.
After I changed the .properties file as per ur instructuions.it gave me that folder will be lost.

After that I ran the same program which I had sent earlier .
It is giving the following error.


log4j:WARN No appenders could be found for logger (ca.uhn.hl7v2.parser.Parser).

log4j:WARN Please initialize the log4j system properly.

ca.uhn.hl7v2.HL7Exception: Couldn't create Message object of type ORM_O01

at ca.uhn.hl7v2.parser.PipeParser.parse(PipeParser.java:218)

at org.srit.hl7.TestORM.main(TestORM.java:34)

Caused by: ca.uhn.hl7v2.HL7Exception: No map found for version 2.3.1

at ca.uhn.hl7v2.parser.Parser.getMessageStructureForEvent(Parser.java:390)

at ca.uhn.hl7v2.parser.Parser.findMessageClass(Parser.java:263)

at ca.uhn.hl7v2.parser.PipeParser.parse(PipeParser.java:205)

... 1 more

java.lang.NullPointerException

at org.srit.hl7.TestORM.main(TestORM.java:43)

Exception in thread "main" 



What is the correct way of modfiying the file.

Please give me the proper steps t make the below changes .

Hoping for a early Reply



Regards

Praveen

Aris JAVIER RAMOS wrote:
Hello,

When I frist came to the Hapi distribution list, I had the same problem than you
I was using the parse HAPI 0.4.2.

To solve my problem I modified the jar archive of api.

In thad jar i found à text file called ca/uhn/hl7v2/parser/eventmap/2.3.properties
(I was using the 2.3 version of the HL7 norm) and i modified this sequence of line :
ORM_O01 ORM_O01
ORM_O01 OMD_O01
ORM_O01 OMN_O01
ORM_O01 OMS_O01
ORM_O01 RDO_O01 <---
like this :
ORM_O01 ORM_O01
#ORM_O01 OMD_O01
#ORM_O01 OMN_O01
#ORM_O01 OMS_O01
#ORM_O01 RDO_O01

and it worked

good look.

Aris

PS if you are using 2.3.1 version, modifie the file "2.3.1.properties" and so on.

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

>>> Praveen Kumar 
03/22 11:21 >>>

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




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


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

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

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

Thanks Aris,
                       The Problem is resolved.I am getting ORM_O01 after parsing
  
 
Thanks a lot.It's working fine.
Thanks Steven for ur suggestion.
 
The Problem is resolved.I am getting ORM_O01 after parsing
 
If any body has latest source for HAPI hl7 v2.5 pls send it across to me or is there a way to access it.???If so Pls tell me How to do it???
 
Waiting for ur reply
 
Regards
Praveen Kumar.A

Aris JAVIER RAMOS <Ari...@hc...> wrote:
yes the archive is hapi-0.4.2.jar

You must uncompress the entire archive before (with winzip letting the option user folder names).
go to the file to modifie. and after modification compress it again, it will create à .zip file, you can change
the .zip in .jar.

have you let the line mapping ORM_O01 ORM_O01 uncommented ?

regards

Aris

>>> Praveen Kumar 
03/22 2:15 >>>
Hi All,
Iin which jar file i need to comment the lines.
is it in hapi-0.4.2.jar????
I have changed 2.3.1 .properties in the jar file.
After I changed the .properties file as per ur instructuions.it gave me that folder will be lost.

After that I ran the same program which I had sent earlier .
It is giving the following error.


log4j:WARN No appenders could be found for logger (ca.uhn.hl7v2.parser.Parser).

log4j:WARN Please initialize the log4j system properly.

ca.uhn.hl7v2.HL7Exception: Couldn't create Message object of type ORM_O01

at ca.uhn.hl7v2.parser.PipeParser.parse(PipeParser.java:218)

at org.srit.hl7.TestORM.main(TestORM.java:34)

Caused by: ca.uhn.hl7v2.HL7Exception: No map found for version 2.3.1

at ca.uhn.hl7v2.parser.Parser.getMessageStructureForEvent(Parser.java:390)

at ca.uhn.hl7v2.parser.Parser.findMessageClass(Parser.java:263)

at ca.uhn.hl7v2.parser.PipeParser.parse(PipeParser.java:205)

... 1 more

java.lang.NullPointerException

at org.srit.hl7.TestORM.main(TestORM.java:43)

Exception in thread "main" 



What is the correct way of modfiying the file.

Please give me the proper steps t make the below changes .

Hoping for a early Reply



Regards

Praveen

Aris JAVIER RAMOS wrote:
Hello,

When I frist came to the Hapi distribution list, I had the same problem than you
I was using the parse HAPI 0.4.2.

To solve my problem I modified the jar archive of api.

In thad jar i found à text file called ca/uhn/hl7v2/parser/eventmap/2.3.properties
(I was using the 2.3 version of the HL7 norm) and i modified this sequence of line :
ORM_O01 ORM_O01
ORM_O01 OMD_O01
ORM_O01 OMN_O01
ORM_O01 OMS_O01
ORM_O01 RDO_O01 <---
like this :
ORM_O01 ORM_O01
#ORM_O01 OMD_O01
#ORM_O01 OMN_O01
#ORM_O01 OMS_O01
#ORM_O01 RDO_O01

and it worked

good look.

Aris

PS if you are using 2.3.1 version, modifie the file "2.3.1.properties" and so on.

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

>>> Praveen Kumar 
03/22 11:21 >>>

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




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


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

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

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

Thanks Aris,
                        Thanks a lot.It's working fine.
Thanks Steven for ur suggestion.
 
The Problem is resolved.I am getting ORM_O01 after 
 
If any body has latest source for HAPI hl7 v2.5 pls send it across to me or is there a way to access it.???If so Pls tell me How to do it???
 
Waiting for ur reply
 
Regards
Praveen Kumar.A

Aris JAVIER RAMOS <Ari...@hc...> wrote:
yes the archive is hapi-0.4.2.jar

You must uncompress the entire archive before (with winzip letting the option user folder names).
go to the file to modifie. and after modification compress it again, it will create à .zip file, you can change
the .zip in .jar.

have you let the line mapping ORM_O01 ORM_O01 uncommented ?

regards

Aris

>>> Praveen Kumar 
03/22 2:15 >>>
Hi All,
Iin which jar file i need to comment the lines.
is it in hapi-0.4.2.jar????
I have changed 2.3.1 .properties in the jar file.
After I changed the .properties file as per ur instructuions.it gave me that folder will be lost.

After that I ran the same program which I had sent earlier .
It is giving the following error.


log4j:WARN No appenders could be found for logger (ca.uhn.hl7v2.parser.Parser).

log4j:WARN Please initialize the log4j system properly.

ca.uhn.hl7v2.HL7Exception: Couldn't create Message object of type ORM_O01

at ca.uhn.hl7v2.parser.PipeParser.parse(PipeParser.java:218)

at org.srit.hl7.TestORM.main(TestORM.java:34)

Caused by: ca.uhn.hl7v2.HL7Exception: No map found for version 2.3.1

at ca.uhn.hl7v2.parser.Parser.getMessageStructureForEvent(Parser.java:390)

at ca.uhn.hl7v2.parser.Parser.findMessageClass(Parser.java:263)

at ca.uhn.hl7v2.parser.PipeParser.parse(PipeParser.java:205)

... 1 more

java.lang.NullPointerException

at org.srit.hl7.TestORM.main(TestORM.java:43)

Exception in thread "main" 



What is the correct way of modfiying the file.

Please give me the proper steps t make the below changes .

Hoping for a early Reply



Regards

Praveen

Aris JAVIER RAMOS wrote:
Hello,

When I frist came to the Hapi distribution list, I had the same problem than you
I was using the parse HAPI 0.4.2.

To solve my problem I modified the jar archive of api.

In thad jar i found à text file called ca/uhn/hl7v2/parser/eventmap/2.3.properties
(I was using the 2.3 version of the HL7 norm) and i modified this sequence of line :
ORM_O01 ORM_O01
ORM_O01 OMD_O01
ORM_O01 OMN_O01
ORM_O01 OMS_O01
ORM_O01 RDO_O01 <---
like this :
ORM_O01 ORM_O01
#ORM_O01 OMD_O01
#ORM_O01 OMN_O01
#ORM_O01 OMS_O01
#ORM_O01 RDO_O01

and it worked

good look.

Aris

PS if you are using 2.3.1 version, modifie the file "2.3.1.properties" and so on.

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

>>> Praveen Kumar 
03/22 11:21 >>>

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




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

		
---------------------------------
Do you Yahoo!?
 Yahoo! Sports -  Sign up for Fantasy Baseball.

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

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

Thanks Aris,
                        Thanks a lot.It's working fine.
Thanks Steven for ur suggestion.
 
The Problem is resolved.I am getting ORM_O01 
 
If any body has latest source for HAPI hl7 v2.5 pls send it across to me or is there a way to access it.???If so Pls tell me How to do it???
 
Waiting for ur reply
 
Regards
Praveen Kumar.A

Aris JAVIER RAMOS <Ari...@hc...> wrote:
yes the archive is hapi-0.4.2.jar

You must uncompress the entire archive before (with winzip letting the option user folder names).
go to the file to modifie. and after modification compress it again, it will create à .zip file, you can change
the .zip in .jar.

have you let the line mapping ORM_O01 ORM_O01 uncommented ?

regards

Aris

>>> Praveen Kumar 
03/22 2:15 >>>
Hi All,
Iin which jar file i need to comment the lines.
is it in hapi-0.4.2.jar????
I have changed 2.3.1 .properties in the jar file.
After I changed the .properties file as per ur instructuions.it gave me that folder will be lost.

After that I ran the same program which I had sent earlier .
It is giving the following error.


log4j:WARN No appenders could be found for logger (ca.uhn.hl7v2.parser.Parser).

log4j:WARN Please initialize the log4j system properly.

ca.uhn.hl7v2.HL7Exception: Couldn't create Message object of type ORM_O01

at ca.uhn.hl7v2.parser.PipeParser.parse(PipeParser.java:218)

at org.srit.hl7.TestORM.main(TestORM.java:34)

Caused by: ca.uhn.hl7v2.HL7Exception: No map found for version 2.3.1

at ca.uhn.hl7v2.parser.Parser.getMessageStructureForEvent(Parser.java:390)

at ca.uhn.hl7v2.parser.Parser.findMessageClass(Parser.java:263)

at ca.uhn.hl7v2.parser.PipeParser.parse(PipeParser.java:205)

... 1 more

java.lang.NullPointerException

at org.srit.hl7.TestORM.main(TestORM.java:43)

Exception in thread "main" 



What is the correct way of modfiying the file.

Please give me the proper steps t make the below changes .

Hoping for a early Reply



Regards

Praveen

Aris JAVIER RAMOS wrote:
Hello,

When I frist came to the Hapi distribution list, I had the same problem than you
I was using the parse HAPI 0.4.2.

To solve my problem I modified the jar archive of api.

In thad jar i found à text file called ca/uhn/hl7v2/parser/eventmap/2.3.properties
(I was using the 2.3 version of the HL7 norm) and i modified this sequence of line :
ORM_O01 ORM_O01
ORM_O01 OMD_O01
ORM_O01 OMN_O01
ORM_O01 OMS_O01
ORM_O01 RDO_O01 <---
like this :
ORM_O01 ORM_O01
#ORM_O01 OMD_O01
#ORM_O01 OMN_O01
#ORM_O01 OMS_O01
#ORM_O01 RDO_O01

and it worked

good look.

Aris

PS if you are using 2.3.1 version, modifie the file "2.3.1.properties" and so on.

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

>>> Praveen Kumar 
03/22 11:21 >>>

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




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

		
---------------------------------
Do you Yahoo!?
 Make Yahoo! your home page   

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

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

Thanks Aris,
                        Thanks a lot.It's working fine.
Thanks Steven for ur suggestion.
 
The Problem is resolved.I am getting 
 
If any body has latest source for HAPI hl7 v2.5 pls send it across to me or is there a way to access it.???If so Pls tell me How to do it???
 
Waiting for ur reply
 
Regards
Praveen Kumar.A

Aris JAVIER RAMOS <Ari...@hc...> wrote:
yes the archive is hapi-0.4.2.jar

You must uncompress the entire archive before (with winzip letting the option user folder names).
go to the file to modifie. and after modification compress it again, it will create à .zip file, you can change
the .zip in .jar.

have you let the line mapping ORM_O01 ORM_O01 uncommented ?

regards

Aris

>>> Praveen Kumar 
03/22 2:15 >>>
Hi All,
Iin which jar file i need to comment the lines.
is it in hapi-0.4.2.jar????
I have changed 2.3.1 .properties in the jar file.
After I changed the .properties file as per ur instructuions.it gave me that folder will be lost.

After that I ran the same program which I had sent earlier .
It is giving the following error.


log4j:WARN No appenders could be found for logger (ca.uhn.hl7v2.parser.Parser).

log4j:WARN Please initialize the log4j system properly.

ca.uhn.hl7v2.HL7Exception: Couldn't create Message object of type ORM_O01

at ca.uhn.hl7v2.parser.PipeParser.parse(PipeParser.java:218)

at org.srit.hl7.TestORM.main(TestORM.java:34)

Caused by: ca.uhn.hl7v2.HL7Exception: No map found for version 2.3.1

at ca.uhn.hl7v2.parser.Parser.getMessageStructureForEvent(Parser.java:390)

at ca.uhn.hl7v2.parser.Parser.findMessageClass(Parser.java:263)

at ca.uhn.hl7v2.parser.PipeParser.parse(PipeParser.java:205)

... 1 more

java.lang.NullPointerException

at org.srit.hl7.TestORM.main(TestORM.java:43)

Exception in thread "main" 



What is the correct way of modfiying the file.

Please give me the proper steps t make the below changes .

Hoping for a early Reply



Regards

Praveen

Aris JAVIER RAMOS wrote:
Hello,

When I frist came to the Hapi distribution list, I had the same problem than you
I was using the parse HAPI 0.4.2.

To solve my problem I modified the jar archive of api.

In thad jar i found à text file called ca/uhn/hl7v2/parser/eventmap/2.3.properties
(I was using the 2.3 version of the HL7 norm) and i modified this sequence of line :
ORM_O01 ORM_O01
ORM_O01 OMD_O01
ORM_O01 OMN_O01
ORM_O01 OMS_O01
ORM_O01 RDO_O01 <---
like this :
ORM_O01 ORM_O01
#ORM_O01 OMD_O01
#ORM_O01 OMN_O01
#ORM_O01 OMS_O01
#ORM_O01 RDO_O01

and it worked

good look.

Aris

PS if you are using 2.3.1 version, modifie the file "2.3.1.properties" and so on.

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

>>> Praveen Kumar 
03/22 11:21 >>>

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




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

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

Thanks Aris,
                        Thanks a lot.It's working fine.
Thanks Steven for ur suggestion.
 
The Problem is resolved.I am getting ORM_O01 after 
 
If any body has latest source for HAPI hl7 v2.5 pls send it across to me or is there a way to access it.???If so Pls tell me How to do it???
 
Waiting for ur reply
 
Regards
Praveen Kumar.A

Aris JAVIER RAMOS <Ari...@hc...> wrote:
yes the archive is hapi-0.4.2.jar

You must uncompress the entire archive before (with winzip letting the option user folder names).
go to the file to modifie. and after modification compress it again, it will create à .zip file, you can change
the .zip in .jar.

have you let the line mapping ORM_O01 ORM_O01 uncommented ?

regards

Aris

>>> Praveen Kumar 
03/22 2:15 >>>
Hi All,
Iin which jar file i need to comment the lines.
is it in hapi-0.4.2.jar????
I have changed 2.3.1 .properties in the jar file.
After I changed the .properties file as per ur instructuions.it gave me that folder will be lost.

After that I ran the same program which I had sent earlier .
It is giving the following error.


log4j:WARN No appenders could be found for logger (ca.uhn.hl7v2.parser.Parser).

log4j:WARN Please initialize the log4j system properly.

ca.uhn.hl7v2.HL7Exception: Couldn't create Message object of type ORM_O01

at ca.uhn.hl7v2.parser.PipeParser.parse(PipeParser.java:218)

at org.srit.hl7.TestORM.main(TestORM.java:34)

Caused by: ca.uhn.hl7v2.HL7Exception: No map found for version 2.3.1

at ca.uhn.hl7v2.parser.Parser.getMessageStructureForEvent(Parser.java:390)

at ca.uhn.hl7v2.parser.Parser.findMessageClass(Parser.java:263)

at ca.uhn.hl7v2.parser.PipeParser.parse(PipeParser.java:205)

... 1 more

java.lang.NullPointerException

at org.srit.hl7.TestORM.main(TestORM.java:43)

Exception in thread "main" 



What is the correct way of modfiying the file.

Please give me the proper steps t make the below changes .

Hoping for a early Reply



Regards

Praveen

Aris JAVIER RAMOS wrote:
Hello,

When I frist came to the Hapi distribution list, I had the same problem than you
I was using the parse HAPI 0.4.2.

To solve my problem I modified the jar archive of api.

In thad jar i found à text file called ca/uhn/hl7v2/parser/eventmap/2.3.properties
(I was using the 2.3 version of the HL7 norm) and i modified this sequence of line :
ORM_O01 ORM_O01
ORM_O01 OMD_O01
ORM_O01 OMN_O01
ORM_O01 OMS_O01
ORM_O01 RDO_O01 <---
like this :
ORM_O01 ORM_O01
#ORM_O01 OMD_O01
#ORM_O01 OMN_O01
#ORM_O01 OMS_O01
#ORM_O01 RDO_O01

and it worked

good look.

Aris

PS if you are using 2.3.1 version, modifie the file "2.3.1.properties" and so on.

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

>>> Praveen Kumar 
03/22 11:21 >>>

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




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

		
---------------------------------
Do you Yahoo!?
 Make Yahoo! your home page   

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

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

Thanks Aris,
                        Thanks a lot.It's working fine.
Thanks Steven for ur suggestion.
 
The Problem is resolved.I 
 
If any body has latest source for HAPI hl7 v2.5 pls send it across to me or is there a way to access it.???If so Pls tell me How to do it???
 
Waiting for ur reply
 
Regards
Praveen Kumar.A

Aris JAVIER RAMOS <Ari...@hc...> wrote:
yes the archive is hapi-0.4.2.jar

You must uncompress the entire archive before (with winzip letting the option user folder names).
go to the file to modifie. and after modification compress it again, it will create à .zip file, you can change
the .zip in .jar.

have you let the line mapping ORM_O01 ORM_O01 uncommented ?

regards

Aris

>>> Praveen Kumar 
03/22 2:15 >>>
Hi All,
Iin which jar file i need to comment the lines.
is it in hapi-0.4.2.jar????
I have changed 2.3.1 .properties in the jar file.
After I changed the .properties file as per ur instructuions.it gave me that folder will be lost.

After that I ran the same program which I had sent earlier .
It is giving the following error.


log4j:WARN No appenders could be found for logger (ca.uhn.hl7v2.parser.Parser).

log4j:WARN Please initialize the log4j system properly.

ca.uhn.hl7v2.HL7Exception: Couldn't create Message object of type ORM_O01

at ca.uhn.hl7v2.parser.PipeParser.parse(PipeParser.java:218)

at org.srit.hl7.TestORM.main(TestORM.java:34)

Caused by: ca.uhn.hl7v2.HL7Exception: No map found for version 2.3.1

at ca.uhn.hl7v2.parser.Parser.getMessageStructureForEvent(Parser.java:390)

at ca.uhn.hl7v2.parser.Parser.findMessageClass(Parser.java:263)

at ca.uhn.hl7v2.parser.PipeParser.parse(PipeParser.java:205)

... 1 more

java.lang.NullPointerException

at org.srit.hl7.TestORM.main(TestORM.java:43)

Exception in thread "main" 



What is the correct way of modfiying the file.

Please give me the proper steps t make the below changes .

Hoping for a early Reply



Regards

Praveen

Aris JAVIER RAMOS wrote:
Hello,

When I frist came to the Hapi distribution list, I had the same problem than you
I was using the parse HAPI 0.4.2.

To solve my problem I modified the jar archive of api.

In thad jar i found à text file called ca/uhn/hl7v2/parser/eventmap/2.3.properties
(I was using the 2.3 version of the HL7 norm) and i modified this sequence of line :
ORM_O01 ORM_O01
ORM_O01 OMD_O01
ORM_O01 OMN_O01
ORM_O01 OMS_O01
ORM_O01 RDO_O01 <---
like this :
ORM_O01 ORM_O01
#ORM_O01 OMD_O01
#ORM_O01 OMN_O01
#ORM_O01 OMS_O01
#ORM_O01 RDO_O01

and it worked

good look.

Aris

PS if you are using 2.3.1 version, modifie the file "2.3.1.properties" and so on.

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

>>> Praveen Kumar 
03/22 11:21 >>>

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




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

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

Thanks Aris,
                        Thanks a lot.It's working fine.
Thanks Steven for ur suggestion.
 
The Problem is resolved.I am 
 
If any body has latest source for HAPI hl7 v2.5 pls send it across to me or is there a way to access it.???If so Pls tell me How to do it???
 
Waiting for ur reply
 
Regards
Praveen Kumar.A

Aris JAVIER RAMOS <Ari...@hc...> wrote:
yes the archive is hapi-0.4.2.jar

You must uncompress the entire archive before (with winzip letting the option user folder names).
go to the file to modifie. and after modification compress it again, it will create à .zip file, you can change
the .zip in .jar.

have you let the line mapping ORM_O01 ORM_O01 uncommented ?

regards

Aris

>>> Praveen Kumar 
03/22 2:15 >>>
Hi All,
Iin which jar file i need to comment the lines.
is it in hapi-0.4.2.jar????
I have changed 2.3.1 .properties in the jar file.
After I changed the .properties file as per ur instructuions.it gave me that folder will be lost.

After that I ran the same program which I had sent earlier .
It is giving the following error.


log4j:WARN No appenders could be found for logger (ca.uhn.hl7v2.parser.Parser).

log4j:WARN Please initialize the log4j system properly.

ca.uhn.hl7v2.HL7Exception: Couldn't create Message object of type ORM_O01

at ca.uhn.hl7v2.parser.PipeParser.parse(PipeParser.java:218)

at org.srit.hl7.TestORM.main(TestORM.java:34)

Caused by: ca.uhn.hl7v2.HL7Exception: No map found for version 2.3.1

at ca.uhn.hl7v2.parser.Parser.getMessageStructureForEvent(Parser.java:390)

at ca.uhn.hl7v2.parser.Parser.findMessageClass(Parser.java:263)

at ca.uhn.hl7v2.parser.PipeParser.parse(PipeParser.java:205)

... 1 more

java.lang.NullPointerException

at org.srit.hl7.TestORM.main(TestORM.java:43)

Exception in thread "main" 



What is the correct way of modfiying the file.

Please give me the proper steps t make the below changes .

Hoping for a early Reply



Regards

Praveen

Aris JAVIER RAMOS wrote:
Hello,

When I frist came to the Hapi distribution list, I had the same problem than you
I was using the parse HAPI 0.4.2.

To solve my problem I modified the jar archive of api.

In thad jar i found à text file called ca/uhn/hl7v2/parser/eventmap/2.3.properties
(I was using the 2.3 version of the HL7 norm) and i modified this sequence of line :
ORM_O01 ORM_O01
ORM_O01 OMD_O01
ORM_O01 OMN_O01
ORM_O01 OMS_O01
ORM_O01 RDO_O01 <---
like this :
ORM_O01 ORM_O01
#ORM_O01 OMD_O01
#ORM_O01 OMN_O01
#ORM_O01 OMS_O01
#ORM_O01 RDO_O01

and it worked

good look.

Aris

PS if you are using 2.3.1 version, modifie the file "2.3.1.properties" and so on.

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

>>> Praveen Kumar 
03/22 11:21 >>>

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




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

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

[HAPI-devel] RE: XML ORU_R01 Message not validating against schema

[Jim K. <ji...@ho...>]

Hi-

Just a quick follow up to my last message on this topic.

I should have mentioned that the interface I send to requires the use of the 
HL7 batch protocol.  I had to write a few new "containing" classes in order 
to get HAPI to generate messages the way I needed them.  In doing this, I 
think that I threw off an implicit asssumption on the part of the XMLParser, 
namely that everything after the root (which in my case is now the BATCH 
message) is a group and should be treated as such.  So when it gets around 
to the ORU_R01 message class, its already assuming that its processing only 
AbstractGroups.

Any thoughts on this?

Thanks.

Jim

[HAPI-devel] XML ORU_R01 Message not validating against schema

[Jim K. <ji...@ho...>]

Hey All-

I know that updating the XML generation is on tap for the next release 
(0.4.4?) and you probably already came across this, but just in case you're 
still making lists:

I'm generating ORU messages and I noticed that the root node is being 
rendered as ORU.R01 instead of the expected ORU_R01.  This is being done by 
the makeGroupElementName method and I assume that its done to accomodate 
SUPPGRP type classes like ORU_R01_ORCOBRNTEOBXNTECTI where it is legitimate 
to replace the first underscore with a period.  However, since the method 
doesn't differentiate between AbstractGroup implementers and AbstractMessage 
implementers, AbstraceMessages have their XML representations mangled.

    protected static String makeGroupElementName(String className) {
        String ret = null;
        int loc = className.lastIndexOf('_');
        if (loc >= 0) {
            StringBuffer elementName = new StringBuffer();
            elementName.append(className.substring(0, loc));
            elementName.append('.');
            elementName.append(className.substring(loc + 1));
            ret = elementName.toString();
        }
        else {
            ret = className;
        }
        return ret;
    }

Maybe its possible to put the check in the encode method?

    private void encode(ca.uhn.hl7v2.model.Group groupObject, 
org.w3c.dom.Element groupElement) throws HL7Exception {
        String[] childNames = groupObject.getNames();
        try {
            for (int i = 0; i < childNames.length; i++) {
                Structure[] reps = groupObject.getAll(childNames[i]);
                for (int j = 0; j < reps.length; j++) {
                    Element childElement =
                        
groupElement.getOwnerDocument().createElement(makeGroupElementName(childNames[i]));
                    groupElement.appendChild(childElement);
                    if (reps[j] instanceof Group) {
                        encode((Group) reps[j], childElement);
                    }
                    else if (reps[j] instanceof Segment) {
                        encode((Segment) reps[j], childElement);
                    }
                }
            }
        }
        catch (DOMException e) {
            throw new HL7Exception(
                "Can't encode group " + groupObject.getClass().getName(),
                HL7Exception.APPLICATION_INTERNAL_ERROR,
                e);
        }
    }