none
HL7 2.3.1 Error parsing repeating field ORC7 RRS feed

  • Question

  • I'm using HL7 2.3.1 and I get a datatype parsing error when there's a repeating ORC 7 field.  The ORC segment in the message is as follows:

     

     

    ORC|NW|800085|||||2^QD^4D^201008240000-0600^201008270000-0600^^^~1^QD^10D^201008280000-0600^201009060000-0600^^^||201008240000-0600|blah^blah^blah||blah^blah^blah

     

    Can anyone explain why I'm getting this error?  ~ is the correct repeat delimiter in MSH (MSH|^~\&|).  I can't find help anywhere so any would be appreciated!

     

    Error happened in body during parsing 

    Error # 1

    Segment Id: ORC_CommonOrderSegment

    Sequence Number: 1

    Field Number: 7

    Error Number: 102

    Error Description: Data type error

    Encoding System: HL7nnnn


     


     

    Thursday, September 2, 2010 8:56 PM

Answers

  • Hi,

    The error states the 1st occurance of ORC-7 (ORD message) is invalid based on it's data type.  (i.e. the data contained in the ORC-7 does not match what is defined in the schema.)

    The  ORC-7 data type is TQ. 

    Note :: Complex type made up of  the following;

    Type: TQ - Timing/quantity  (9 components)

    Category: Time Series

    Instructions: 2.8.43  For timing/quantity specifications for orders, see Chapter 4, Section 4.4.  <quantity (CQ)> ^ <interval (*)> ^ <duration (*)> ^ <start date/time (TS)> ^ <end date/time (TS)> ^ <priority (ST)> ^ <condition (ST)> ^ <text (TX)> ^ <conjunction (ID)> ^

           Component 1 [CQ] quantity

           Component 2 [ST] interval

           Component 3 [ST] duration

           Component 4 [TS] start date/time

           Component 5 [TS] end date/time

           Component 6 [ST] priority

           Component 7 [ST] condition

           Component 8 [TX] text

           Component 9 [ID] conjunction

    Confirm that your message matches what is expected for the data type.

     

    Thanks,

     

    William

     

    Friday, September 3, 2010 12:49 PM