Warning message that keeps repeating in error log

[Robert Denny]

I am working on cleaning up our error logs.

In our pacs process we are getting many warnings that read

12/15/2009 00:09:04 [msg :RecP:WARN/0:   Pacs_xlate] [0.0.10803661] The # 2 segment encountered ‘PV1’ is not defined for message type ‘ORU_R01’.  Segment ignored.

12/15/2009 00:11:02 [msg :RecP:WARN/0:   Pacs_xlate] [0.0.10803826] The # 2 segment encountered ‘PV1’ is not defined for message type ‘ORU_R01’.  Segment ignored.

12/15/2009 00:12:54 [msg :RecP:WARN/0:   Pacs_xlate] [0.0.10803966] The # 2 segment encountered ‘PV1’ is not defined for message type ‘ORU_R01’.  Segment ignored.

I am not able to find any messages with the ORU_R01 text in any messages.

Any suggestions on what might be causing these warnings?

Topic

[Jim Kosloskey]

Did you find any messages with MSH-9 of ORU anything?

email: jim.kosloskey@jim-kosloskey.com 29+ years Cloverleaf, 59 years IT - old fart.

[Sam Craig]

Search the SMAT file for the message ID listed in the error message and see what is in MSH-9.  Is it setup as a Wildcard for ORU in Thread config?

[Gary Atkinson]

Also, check your variant and make sure the PV1 is in the schema and in the order of the inbound message.

[Ed Mastascusa]

Hi Robert,

Since the warning is saying that the #2 segment is the PV1 it looks like the root cause of the warnings is that you are receiving some messages where an MSH is followed by a PV1 instead of a PID segment.

[Author]

Replies