Trading Partners and Agreements

A trading partner is a business entity that sends or receives data from the Data Exchange Cloud Service. This could be an employer group, a government authority such as the Centers for Medicare and Medicaid Services (CMS), a doctor’s office or hospital system, or a health insurance company that is, the payer itself.

A trading partner agreement defines the specifics of the data exchange between two Trading Partners. This agreement dictates how the data will be received or sent, what kind of data will be exchanged, and how that data will be converted into or from the Data Exchange Cloud Service Canonical data model internally.

In the Data Exchange Cloud Service context, the trading partner agreement combines all the Data Exchange Cloud Service Designer Workbench entities listed below to define a specific data exchange. You can then link an inbound trading partner agreement with an outbound trading partner Agreement to design end-to-end data exchange to meet your business requirements.

Entity	Description
Line of Business	Trading Partner Agreement is linked to a specific, user-defined LOB to allow the exchange of data with Transaction Types only allowed under that specific LOB. For more details, see Line of Business.
Transmission Model	Transmission Model defines a specific way of exchanging data and internally consists of Transaction Type, Data Format, and Direction of Data Flow. For more details, see Transmission Model.
Data Enrichment Lookups	The inbound data might not always match the expectations of the outbound trading partner or the Data Exchange Cloud Service Canonical data model. To ensure that the data meets the business requirements of the receiving partner, Data Exchange Cloud Service lookups can be used to enrich and modify incoming data as necessary. This is only applicable for Inbound Trading Partner Agreements.
Data Validation Rules	User-defined data validation rules to ensure inbound transaction data meets your business requirements. This is only applicable to Inbound Trading Partner Agreements.
Threshold Conditions	Allows transmission to be pended for manual user review when exceptions logged against all the transactions within a transmission exceed configured threshold counts.

Entity

Description

Line of Business

Trading Partner Agreement is linked to a specific, user-defined LOB to allow the exchange of data with Transaction Types only allowed under that specific LOB. For more details, see Line of Business.

Transmission Model

Transmission Model defines a specific way of exchanging data and internally consists of Transaction Type, Data Format, and Direction of Data Flow. For more details, see Transmission Model.

Data Enrichment Lookups

The inbound data might not always match the expectations of the outbound trading partner or the Data Exchange Cloud Service Canonical data model. To ensure that the data meets the business requirements of the receiving partner, Data Exchange Cloud Service lookups can be used to enrich and modify incoming data as necessary.

This is only applicable for Inbound Trading Partner Agreements.

Data Validation Rules

User-defined data validation rules to ensure inbound transaction data meets your business requirements.

This is only applicable to Inbound Trading Partner Agreements.

Threshold Conditions

Allows transmission to be pended for manual user review when exceptions logged against all the transactions within a transmission exceed configured threshold counts.