Uploaded image for project: 'V2 Specification Feedback'
  1. V2 Specification Feedback
  2. V2-25353

ERL-2 (Segment Sequence) component note refers to field position

    XMLWordPrintableJSON

Details

    • Icon: Technical Correction Technical Correction
    • Resolution: Persuasive
    • Icon: Medium Medium
    • V2.x Message Specification (V2)
    • V2.9
    • Infrastructure & Messaging
    • ERROR LOCATION (ERL)
    • Data Types (Chapter 2A)
    • 2A.3.28.2
    • Hide

      Replace the text in 2a.3.28.2 note with:

      Note: This number refers to the absolute position of the referenced instance of the segment type in the message – it is not synonymous with the Set-ID of the segment – For example if ERL.1 = OBX and ERL.2 = 5 that means it is the 5th OBX segment in the message.

      Chapter and implementation guide authors SHOULD choose the Set-ID numbering scheme for the segments in their message definitions in the same manner. ** 

      Show
      Replace the text in 2a.3.28.2 note with: Note: This number refers to the absolute position of the referenced instance of the segment type in the message – it is not synonymous with the Set-ID of the segment – For example if ERL.1 = OBX and ERL.2 = 5 that means it is the 5th OBX segment in the message. Chapter and implementation guide authors SHOULD choose the Set-ID numbering scheme for the segments in their message definitions in the same manner. ** 
    • Correction
    • Non-substantive

    Description

      The description note states, "for example if the referenced element is OBX in field position 5, that means it is the 5th OBX segment in the message" but this is not correct. OBX is a segment and thus can't be in a field position. I recommend rephrasing it as, "for example if the first component is OBX and the second component is 5, that means it is the 5th OBX segment in the message".

      Attachments

        Activity

          People

            Unassigned Unassigned
            nradov Nick Radov
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: