The Demo site for our new HL7 Version 2+ (plus) Standard
visit the hl7 website

Draft Website - For Review Purposes Only

RGS - Resource Group Segment

The RGS segment is used to identify relationships between resources identified for a scheduled event. This segment can be used, on a site specified basis, to identify groups of resources that are used together within a scheduled event, or to describe some other relationship between resources. To specify related groups of resources within a message, begin each group with an RGS segment, and then follow that RGS with one or more of the Appointment Information segments (AIG, AIL, AIS, or AIP).

If a message does not require any grouping of resources, then specify a single RGS in the message, and follow it with all of the Appointment Information segments for the scheduled event. (At least one RGS segment is required in each message – even if no grouping of resources is required – to allow parsers to properly understand the message.)

HL7 Attribute Table - RGS - Resource Group Segment
Seq# DataElement Description Must Implement Flags Cardinality Length C.LEN Vocabulary DataType
RGS
1 01203 Set ID - RGS SHALL [1..1] [1..4] SI
2

00763 Segment Action Code MAY
True:
False:
C
[1..1]
[0..1]
[1..1] ID
3 01204 Resource Group ID [0..1] CWE

RGS-1: Set ID - RGS (SI) 01203

Definition: This field contains a number that uniquely identifies the information represented by this segment in this transaction for the purposes of addition, change or deletion.

RGS-2: Segment Action Code (ID) 00763

(Definition from OMC.2 in Ch. 8)

Definition:  This field indicates whether this repetition of the segment is being added, changed or deleted.  When using dynamic update mode (See Chapter 2, Section 2.23.4.2, "Action code/unique identifier mode update definition.")  OMC-2 and OMC-3 Segment Unique Key are used to establish the "unique key" and to determine the data subject to the action. Refer to HL7 Table 0206 – Segment action code for valid values.

If the transaction uses dynamic/action code messaging, the field must be valued. 

Condition Predicate: Required if OMC-3 is valued.

(Definition from LCH.2 in Ch. 8)

Definition: This field indicates whether this repetition of the segment is being added, changed or deleted. The action code adds a validation check to indicate, from the point of view of the sending system, whether this repetition of a segment is being added, changed or deleted. This and the following field are used to implement the "unique key" mode of updating repeating segments. (See Chapter 2, section 2.10.4.2, "Action code/unique identifier mode update definition.") Refer to HL7 Table 0206 - Segment Action Code in Chapter 2C, Code Tables, for valid values.

(Definition from LRL.2 in Ch. 8)

Definition: This field indicates whether this repetition of the segment is being added, changed or deleted. The action code adds a validation check to indicate, from the point of view of the sending system, whether this repetition of a segment is being added, changed or deleted. This and the following field are used to implement the "unique key" mode of updating repeating segments. (See Chapter 2, section 2.10.4.2, "Action code/unique identifier mode update definition.") Refer to HL7 Table 0206 - Segment Action Code in Chapter 2C, Code Tables, for valid values.

(Definition from RGS.2 in Ch. 10)

Definition: This field contains the action to be taken when updating or modifying information in this segment from previously sent interface transactions. Refer to HL7 Table 0206 - Segment Action Code in Chapter 2C, Code Tables, for valid values.

This field is conditionally required. It is required for all updating or modifying trigger events.

(Definition from AIS.2 in Ch. 10)

Definition: This field contains the action to be taken when updating or modifying information in this segment from previously sent interface transactions. Refer to HL7 Table 0206 - Segment Action Code in Chapter 2C, Code Tables, for valid values.

This field is conditionally required. It is required for all updating or modifying trigger events.

(Definition from AIG.2 in Ch. 10)

Definition: This field contains the action to be taken when updating or modifying information in this segment from previously sent interface transactions. Refer to HL7 Table 0206 - Segment Action Code in Chapter 2, Code Tables, for valid values.

This field is conditionally required. It is required for all updating or modifying trigger events.

(Definition from AIL.2 in Ch. 10)

Definition: This field contains the action to be taken when updating or modifying information in this segment from previously sent interface transactions. Refer to HL7 Table 0206 - Segment Action Code in Chapter 2C, Code Tables, for valid values

This field is conditionally required. It is required for all updating or modifying trigger events.

(Definition from AIP.2 in Ch. 10)

Definition: This field contains the action to be taken when updating or modifying information in this segment from previously sent interface transactions. Refer to HL7 Table 0206 - Segment Action Code in Chapter 2C, Code Tables, for valid values.

This field is conditionally required. It is required for all updating or modifying trigger events.

RGS-3: Resource Group ID (CWE) 01204

Definition: This field contains an identifier code describing the group of resources following this RGS segment.