A testcase would be great help.
From: rahul somasunderam [mailto:[email protected]]
Sent: Thursday, February 11, 2010 4:15 PM
To: Sharma, Niranjan K (GE Healthcare);
[email protected]
Subject: RE: [HAPI-devel] Getting non standard segments in a message
Niranjan,
It looks like a known bug:
This is what hl7api.sourceforge.net had to say about 1.0:
After a great deal of profiling and optimizing, the PipeParser is now
60-70% faster and the XML parser is at least 30% faster as well. The
changes involved in these optimizations also fixed a few long standing
bugs, such as the first repetition of a repeating segment always being
added to a message structure even when it wasn't present in the message,
and the fact that unexpected segments early in a message caused the rest
of the message to parse into generic segments instead of their correct
locations within the message structure.
So this might have been fixed in 1.0.
If you think it'll be helpful, I'll create a test case based on this and
submit it.
Regards,
rahul
From: Sharma, Niranjan K (GE Healthcare)
[mailto:[email protected]]
Sent: Thursday, February 11, 2010 3:04 PM
To: rahul somasunderam; [email protected]
Subject: RE: [HAPI-devel] Getting non standard segments in a message
Rahul,
Do you know why it is shifting the Group index from 0 to 1 in
PATIENT_RESULT.
Thanks.
Regards
-Niranjan.
From: rahul somasunderam [mailto:[email protected]]
Sent: Thursday, February 11, 2010 4:00 PM
To: Sharma, Niranjan K (GE Healthcare);
[email protected]
Subject: RE: [HAPI-devel] Getting non standard segments in a message
This is what the message looks like:
MSH|^~\&|RM|351|HBOCORM|351|20100209161723||ORU^R01|20100209161723887|P|
2.5|||AL|NE
EVN|R01|20100209161723
PID|||...
PV1||I|1NO||||...
ORC|RE|...
OBR||17615904|...
OBX|1|TX|R^REPORT^L||...
OBX|1|TX|R^REPORT^L||...
OBX|1|TX|R^REPORT^L||...
... more OBX ...
I realized that values supposed to be in PATIENT_RESULT(0) are in
PATIENT_RESULT(1).
For the moment I have put a filter that removes the EVN segment from the
message. It took me some time to note that problem though.
I want to be able to list out such problems in messages without having
to check each message manually.
BTW, I'm using HAPI 0.5.1.
Regards,
rahul
From: Sharma, Niranjan K (GE Healthcare)
[mailto:[email protected]]
Sent: Thursday, February 11, 2010 2:28 PM
To: rahul somasunderam; [email protected]
Subject: RE: [HAPI-devel] Getting non standard segments in a message
Rahul,
Not sure how you can get your processing messed up with EVN segment post
message construction.
By defining the custom validator you can define a mechanism to determine
unexpected segments and determine course of actions.
Hope this helps.
Thanks.
Regards
-Niranjan.
From: rahul somasunderam [mailto:[email protected]]
Sent: Thursday, February 11, 2010 2:47 PM
To: [email protected]
Subject: [HAPI-devel] Getting non standard segments in a message
Hi,
I am receiving messages from a system which is sending an EVN segment in
an ORU_R01 message.
That's completely messing up my logic for processing the message. I
would like to know when there is such an unexpected segment in a
message. Is there some way to know that?
Regards,
rahul
No virus found in this incoming message.
Checked by AVG - www.avg.com
Version: 8.5.435 / Virus Database: 271.1.1/2678 - Release Date: 02/11/10
07:35:00
No virus found in this incoming message.
Checked by AVG - www.avg.com
Version: 8.5.435 / Virus Database: 271.1.1/2678 - Release Date: 02/11/10
07:35:00
------------------------------------------------------------------------------
SOLARIS 10 is the OS for Data Centers - provides features such as DTrace,
Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW
http://p.sf.net/sfu/solaris-dev2dev
_______________________________________________
Hl7api-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/hl7api-devel
