Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

attempting to process ORU message

136 views
Skip to first unread message

Vibol Hou

unread,
Jun 17, 2004, 7:26:56 PM6/17/04
to
Hi,

I was able to complete the tutorial successfully. Now I'm attempting to
reproduce the steps for the following sample data that I found on the
hl7.org website.

MSH|^~\&|COSTELLO|ORCHARD SOFTWARE|||19990221112417||ORU|325|P|2.1
PID|1|3566|3566||SUNLIGHT^CREE||19790701|F|||14987 Pixie Pt
Cir^^Naperville^IL^00000||||||||
OBR|1|27102|58|CMETABOLIC^CMetabol|R||19990221112415|||^Bahamonde^Toodie||||199902211124||D1^Welby^Marcus||||||199902211124|||F||||||||||
OBX|1|NM|20951-2^NA+||142|MMOL/L|135-145||||F
OBX|2|NM|2823-3^K+||3.3|MMOL/L|3.5-5.5|L|||F
OBX|3|NM|2075-0^CL-||102|MMOL/L|95-105||||F
OBX|4|NM|2028-9^CO2||25|MEQ/L|22-27||||F
OBX|5|NM|2339-0^GLU||115|MG/DL|65-110|H|||F
OBX|6|NM|3094-0^BUN||16|MG/DL|5-20||||F
OBX|7|NM|2160-0^CREA||1.1|MG/DL|0.8-1.4||||F
OBX|8|NM|1751-7^ALBUM||4.0|G/DL|3.5-5.0||||F
OBX|9|NM|1975-2^TBILI||0.6|MG/DL|0.0-1.0||||F
OBX|10|NM|1783-0^ALK P||62|IU/L|25-125||||F
OBX|11|NM|2885-2^T PROT||6.9|G/DL|6.6-7.8||||F
OBX|12|NM|1920-8^AST||39|IU/L|25-45||||F
OBX|13|NM|2000-8^CALC||8.7|MG/DL|8.4-10.6||||F

I've reproduced all the steps up to creating the body project using the
appropriate HL7 version (2.1). I found that the sample message does not
contain a trigger event for the ORU message type. However, the
available schema requires the trigger to be either R01 or R03. I've
also noticed that a sample ORU from another company I'm working with on
HL7 integration does not specify a trigger event. What would the
standard approach be to addressing this issue?

Thanks,
Vibol

Oliver Nee

unread,
Jun 18, 2004, 4:23:18 AM6/18/04
to
>What would the standard approach be to addressing this issue?

I would override the MSH field 9 (that contains the message type and
the trigger event) for the receiving party using the BTAHL7 Configuration
Explorer. First sequence should be ORU, second one R01.

HTH,
Oliver

--

Vibol Hou

unread,
Jun 22, 2004, 5:54:48 PM6/22/04
to
> I would override the MSH field 9 (that contains the message type and
> the trigger event) for the receiving party using the BTAHL7 Configuration
> Explorer. First sequence should be ORU, second one R01.

Oliver, thanks for your reply. I have attempted to override the fields
you've mentioned for the 'COSTELLO' party, but it does not appear to work.
I still receive the following error in the event log:

Error happened in body during parsing
Error # 1

Alternate Error Number: 301
Alternate Error Description: Schema
http://microsoft.com/HealthCare/HL7/2X#ORU__21_GLO_DEF not found
Alternate Encoding System: HL7-BTA

Overriding those values for that party should have triggered the
http://microsoft.com/HealthCare/HL7/2X#ORU_R01_21_GLO_DEF schema, but it
didn't. Do you have any ideas what might be happening?

-Vibol


Vibol Hou

unread,
Jun 22, 2004, 5:57:18 PM6/22/04
to
> I would override the MSH field 9 (that contains the message type and
> the trigger event) for the receiving party using the BTAHL7 Configuration
> Explorer. First sequence should be ORU, second one R01.

I should also mention that I did restart BizTalk after the changes.

-Vibol


Jonathan Kruljac [MSFT]

unread,
Jun 22, 2004, 6:42:23 PM6/22/04
to
Have you tried

MSH|^~\&|COSTELLO|ORCHARD SOFTWARE|||19990221112417||ORU^R01|325|P|2.1

MSH9 needs the message type and the event code and it is sperated by this ^
field delimeter.

This is how dynamic schema resolution is done and is the only way I can see
this being performed. There may be a issue with the instance.

This posting is provided "AS IS" with no warranties, and confers no rights.

EBusiness Server Team
--------------------
From: "Vibol Hou" <vi...@remove-this.webedoctor.com>
References: <OuN3UKMV...@TK2MSFTNGP11.phx.gbl>
<OPazC2QV...@TK2MSFTNGP09.phx.gbl>
Subject: Re: attempting to process ORU message
Date: Tue, 22 Jun 2004 14:54:48 -0700
Lines: 23
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.3790.0
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.132
Message-ID: <uz2JFQKW...@TK2MSFTNGP10.phx.gbl>
Newsgroups: microsoft.public.biztalk.accelerator.hl7
NNTP-Posting-Host: 64-60-93-133.cust.telepacific.net 64.60.93.133
Path:
cpmsftngxa10.phx.gbl!TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP10
.phx.gbl
Xref: cpmsftngxa10.phx.gbl microsoft.public.biztalk.accelerator.hl7:169
X-Tomcat-NG: microsoft.public.biztalk.accelerator.hl7

Vibol Hou

unread,
Jun 23, 2004, 4:52:46 PM6/23/04
to
Hi Jonathan, I have tried as you've suggested and it now runs the instance
through the schema, but now I have a different type of error message in the
Event Log as described below. I believe I've deployed the appropriate
projects: V2XCommon, V21Common, V21Body.

Also, when does field overriding from the BTAHL7 Configuration Explorer
occur in this process?

Thanks,
Vibol

Errors from Event Log:

Error happened in body during parsing
Error # 1

Segment Id: PID_PatientIdentification
Sequence Number: 1
Field Number: 2
Error Number: 102
Error Description: Data type error
Encoding System: HL7nnnn


Error # 2
Segment Id: PID_PatientIdentification
Sequence Number: 1
Field Number: 3
Error Number: 102
Error Description: Data type error
Encoding System: HL7nnnn


Error # 3
Segment Id: OBX_Result
Sequence Number: 1
Field Number: 2
Error Number: 103
Error Description: Table value not found
Encoding System: HL7nnnn


Error # 4
Segment Id: OBX_Result
Sequence Number: 2
Field Number: 2
Error Number: 103
Error Description: Table value not found
Encoding System: HL7nnnn


Error # 5
Segment Id: OBX_Result
Sequence Number: 2
Field Number: 8
Error Number: 102
Error Description: Data type error
Encoding System: HL7nnnn


Error # 6
Segment Id: OBX_Result
Sequence Number: 3
Field Number: 2
Error Number: 103
Error Description: Table value not found
Encoding System: HL7nnnn


Error # 7
Segment Id: OBX_Result
Sequence Number: 4
Field Number: 2
Error Number: 103
Error Description: Table value not found
Encoding System: HL7nnnn


Error # 8
Segment Id: OBX_Result
Sequence Number: 5
Field Number: 2
Error Number: 103
Error Description: Table value not found
Encoding System: HL7nnnn


Error # 9
Segment Id: OBX_Result
Sequence Number: 6
Field Number: 2
Error Number: 103
Error Description: Table value not found
Encoding System: HL7nnnn


Error # 10
Segment Id: OBX_Result
Sequence Number: 7
Field Number: 2
Error Number: 103
Error Description: Table value not found
Encoding System: HL7nnnn


Error # 11
Segment Id: OBX_Result
Sequence Number: 8
Field Number: 2
Error Number: 103
Error Description: Table value not found
Encoding System: HL7nnnn


Error # 12
Segment Id: OBX_Result
Sequence Number: 9
Field Number: 2
Error Number: 103
Error Description: Table value not found
Encoding System: HL7nnnn


Error # 13
Segment Id: OBX_Result
Sequence Number: 10
Field Number: 2
Error Number: 103
Error Description: Table value not found
Encoding System: HL7nnnn


Error # 14
Segment Id: OBX_Result
Sequence Number: 11
Field Number: 2
Error Number: 103
Error Description: Table value not found
Encoding System: HL7nnnn


Error # 15
Segment Id: OBX_Result
Sequence Number: 12
Field Number: 2
Error Number: 103
Error Description: Table value not found
Encoding System: HL7nnnn


Error # 16
Segment Id: OBX_Result
Sequence Number: 13
Field Number: 2
Error Number: 103
Error Description: Table value not found
Encoding System: HL7nnnn


Error # 17
Segment Id: PID_PatientIdentification
Sequence Number: 1
Field Number: 19
Error Number: 207
Error Description: Application internal error
Encoding System: HL7nnnn
Alternate Error Number: Z100
Alternate Error Description: Trailing delimiter found
Alternate Encoding System: HL7-BTA


Error # 18
Segment Id: OBR_ObservationRequest
Sequence Number: 1
Field Number: 8
Error Number: 101
Error Description: Required field is missing
Encoding System: HL7nnnn


Error # 19
Segment Id: OBR_ObservationRequest
Sequence Number: 1
Field Number: 9
Error Number: 101
Error Description: Required field is missing
Encoding System: HL7nnnn


Error # 20
Segment Id: OBR_ObservationRequest
Sequence Number: 1
Field Number: 10
Error Number: 102
Error Description: Data type error
Encoding System: HL7nnnn


Error # 21
Segment Id: OBR_ObservationRequest
Sequence Number: 1
Field Number: 16
Error Number: 102
Error Description: Data type error
Encoding System: HL7nnnn


Error # 22
Segment Id: OBR_ObservationRequest
Sequence Number: 1
Field Number: 35
Error Number: 207
Error Description: Application internal error
Encoding System: HL7nnnn
Alternate Error Number: Z100
Alternate Error Description: Trailing delimiter found
Alternate Encoding System: HL7-BTA

Vibol Hou

unread,
Jun 23, 2004, 8:29:36 PM6/23/04
to
I've resolved most of these issues. Thanks for the assistance folks.

-Vibol

"Vibol Hou" <vi...@remove-this.webedoctor.com> wrote in message
news:##hhCjWWE...@TK2MSFTNGP12.phx.gbl...

0 new messages