EDI 816 Organizational Relationships
Functional Group OR
X12M Supply Chain Subcommittee
This Draft Standard for Trial Use contains the format and establishes the data contents of the Organizational Relationships Transaction Set (816) within the context of an Electronic Data Interchange (EDI) environment. This transaction set can be used to transmit pertinent information about a parent organization, its members and the relationship of a member to another member, and/or to the parent organization. A parent organization could be an association, a multi-hospital system, a chain of retail stores, a holding company, etc. This transaction set can be used to convey the identity and relationship of members to a parent organization; identify eligibility to purchase under the terms and conditions negotiated by a parent organization on behalf of its members; and to update application databases.
Heading
- 010Transaction Set HeaderMandatoryMax 1
To indicate the start of a transaction set and to assign a control number
- 020Beginning of Hierarchical TransactionMandatoryMax 1
To define the business hierarchical structure of the transaction set and identify the business application purpose and reference data, i.e., number, date, and time
BHT03 and BHT04 are mandatory. - 030Date/Time ReferenceOptionalMax 10
To specify pertinent dates and times
- 035Reference IdentificationOptionalMax 12
To specify identifying information
- N1 Loop MandatoryRepeat >1
- 040NameMandatoryMax 1
To identify a party by type of organization, name, and code
The N1 loop shall identify the transaction set issuer and optionally provide contact information if necessary. - 050Additional Name InformationOptionalMax 2
To specify additional names or those longer than 35 characters in length
- 060Address InformationOptionalMax 2
To specify the location of the named party
- 070Geographic LocationOptionalMax 1
To specify the geographic place of the named party
- 080Administrative Communications ContactOptionalMax 3
To identify a person or office to whom administrative communications should be directed
- 090Reference IdentificationOptionalMax 12
To specify identifying information
- 040NameMandatoryMax 1
Detail
- HL Loop MandatoryRepeat >1
- 010Hierarchical LevelMandatoryMax 1
To identify dependencies among and the content of hierarchically related groups of data segments
- N1 Loop MandatoryRepeat >1
- 020NameMandatoryMax 1
To identify a party by type of organization, name, and code
N105, when used, defines the relationship of the entity designated in N102 or N104 to its parent organization. - 030Additional Name InformationOptionalMax 2
To specify additional names or those longer than 35 characters in length
- 040Address InformationOptionalMax 2
To specify the location of the named party
- 050Geographic LocationOptionalMax 1
To specify the geographic place of the named party
- 060Administrative Communications ContactOptionalMax >1
To identify a person or office to whom administrative communications should be directed
- 070Reference IdentificationOptionalMax 12
To specify identifying information
- 080QuantityOptionalMax 5
To specify quantity information
- 090Date/Time ReferenceOptionalMax 10
To specify pertinent dates and times
- 100Action or Status IndicatorOptionalMax 1
To indicate the action to be taken with the information provided or the status of the entity described
- 020NameMandatoryMax 1
- 010Hierarchical LevelMandatoryMax 1
- 110Transaction Set TrailerMandatoryMax 1
To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments)