Section 2.5.2 Segments and segment groups

From HL7Wiki
Jump to navigation Jump to search

2.5.2 Segments and Segment Groups

  1. Original Text:Each segment is identified by a unique three-character code known as the Segment ID. Although the actual segments are defined in various chapters, the ID codes assigned to the various segments are listed in Appendix A.

All segment ID codes beginning with the letter Z are reserved for locally defined segments. No such codes will be defined within the HL7 Standard.

    1. Suggestion:Each segment is identified by a unique three-character code known as the Segment ID. Although the actual segments are defined in various chapters, the ID codes assigned to the various segments are listed in Appendix A. All segment ID codes beginning with the letter Z are reserved for locally defined segments. No such codes will be defined within the HL7 Standard.
    2. Governance #?:The segment identifier SHALL be a unique three(3) letter code known as the Segment ID.
    3. Governance #?:All segment ID codes beginning with the letter Z are reserved for locally defined segments. No such codes will be defined within the HL7 Standard.
    4. Governance #?:2.Governance #?:A segment id beginning with the letter "Z" SHALL NOT be defined within the HL7 Standard.
  1. Original Text:Two or more segments may be organized as a logical unit called a segment group. A segment group may be required or optional and might or might not repeat. As of v 2.5, the first segment in a newly defined segment group will be required to help ensure that unparsable messages will not be inadvertently defined. This required first segment is known as the anchor segment. A segment group is assigned a name that represents a permanent identifier that may not be changed.
    1. Suggestion:Two or more segments may be organized as a logical unit called a segment group. A segment group may be required or optional and might or might not repeat. A segment group is assigned a name that represents a permanent identifier that may not be changed.
    1. Governance #?:The first segment in a newly defined segment group SHALL be required to help ensure that unparsable messages will not be inadvertently defined as if V2.5. This required first segment is known as the anchor segment.
    2. Governance #?:A segment group SHALL be assigned a name that represents a permanent identifier that SHALL NOTbe changed.
  1. Original Text:A named segment X may occur more than once in an abstract message syntax. This differs from repetition described earlier in this section. When this occurs, the following rules must be adhered to:

If, within an abstract message syntax, a named segment X appears in two individual or group locations, and a) Either appearance is optional or repeating in an individual location or, either appearance is optinal or repeating in a group location ; a) or, either appearance is optional or repeating, in a group location b) then, the occurrences of segment X must be separated by at least one required segment of a different name so that no ambiguity can exist as to the individual or group location of any occurrence of segment X in a message instance

    1. Suggestion:A named segment X may occur more than once in an abstract message syntax. This differs from repetition described earlier in this section. When this occurs, the following rules must be adhered to:
    2. Governance #?:If, within an abstract message syntax, a named segment X appears in two individual or group locations, and

a) Either appearance is optional or repeating in an individual location or, either appearance is optinal or repeating in a group location ; a) or, either appearance is optional or repeating, in a group location b) then, the occurrences of segment X SHALL be separated by at least one required segment of a different name so that no ambiguity can exist as to the individual or group location of any occurrence of segment X in a message instance