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.)
Figure 10-5. RGS attributes
SEQ |
LEN |
DT |
R/O/C |
RP/# |
TBL# |
ITEM# |
ELEMENT NAME |
1 |
4 |
SI |
R |
01203 |
Set ID - RGS |
||
2 |
3 |
ID |
C |
00763 |
Segment Action Code |
||
3 |
200 |
CE |
O |
01204 |
Resource Group ID |
10.5.3.0 RGS field definitions
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.
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, Section 2.23.4.2, "Action code/unique identifier mode update definition," for valid values.
This field is conditionally required. It is required for all updating or modifying trigger events.
Components: <identifier (ST)> ^ <text (ST)> ^ <name of coding system (ST)> ^ <alternate identifier (ST)> ^ <alternate text (ST)> ^ <name of alternate coding system (ST)>
Definition: This field contains an identifier code describing the group of resources following this RGS segment.