RGS 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
The shape of one line
required required in some cases optional
RGS-3 and its value arrives as RGS-2, so the receiver stores Resource Group ID as Segment Action Code.This page carries the RGS field table as published and nothing beyond it. The field notes, vendor behaviour, FHIR mapping and parsing guidance that thePID page has are still to be written for RGS.
Every field
| SEQ | LEN | DT | OPT | RP/# | TBL# | ITEM# | Element name | Cardinality |
|---|---|---|---|---|---|---|---|---|
| RGS-1 | 4 | SI | R | 01203 | Set ID - RGS | 1..1 | ||
| RGS-2 | 3 | ID | C | 0206 | 00763 | Segment Action Code | 0..1 | |
| 250 | CE | O | 01204 | Resource Group ID | 0..1 | |||
| ||||||||
Related
Message types carrying RGS
RGS appears in 5 message structures, belonging to 5 message types.