Transmission Model

The Transmission Model defines a unique way of exchanging data between Trading Partners and Data Exchange Cloud Services. It decides the type of transmissions to be processed in the Operations Workbench.

Transmission Model combines the following Data Exchange Cloud Service entities to define a specific data exchange process:

Entity	Description
Line of Business	The use of system-defined Lines of Business, such as Commercial, Medicare, or Medicaid, allows the Transmission Model to have variations specific to that Line of Business for the same transaction type and data format.
Direction	The direction of data flow: Inbound to Data Exchange Cloud Service or Outbound from Data Exchange Cloud Service.
Transaction Type	This transmission model processes specific types of health insurance operational data, such as enrollment, claim professional, claim institutional, and so on. In this first release, Data Exchange Cloud Service supports Enrollment Transaction Type.
Data Format	Describes the format in which data is comes in or goes out of Data Exchange Cloud Service under this Transmission Model. In this first release, Data Exchange Cloud Service supports X12 HIPAA Electronic Data Interchange 834 (EDI 834), Centers for Medicare and Medicaid Services Online Enrollment Center (CMS OEC), and any proprietary Comma Separated Value (CSV), and Oracle Health Insurance Policy Administration system’s Oracle Health Insurance Policy XML formats.
Transport Mechanism	The type of transport mechanism used, such as File or REST API.
Change Level	This describes whether data is Incremental in nature i.e., it is to be applied on top of previously sent data or Full replacement of previously sent data. In the first release, Data Exchange Cloud Service supports Incremental change levels.

Data Exchange Cloud Service includes a template Oracle Integration Cloud (OIC) Integration for each possible Transmission Model. These templates come with pre-defined data mapping from the inbound data format to the Data Exchange Cloud Service canonical data model, and from the Data Exchange Cloud Service Canonical data model to the outbound data format. When a new Transmission Model is created in the Data Exchange Cloud Service Designer Workbench, a corresponding template OIC Integration is cloned in the background for use with that transmission model.

Once a transmission model is created, you can either continue using ready-to-use mapping or change it to meet your business requirements. Furthermore, you can clone an existing transmission model to create a new one and inherit the mapping changes of that existing model.

For example, after creating a transmission model for Inbound EDI 834 data format for enrollment transactions for Florida Medicaid Line of Business, you can change the out-of-the-box mapping of the standard EDI 834 to Data Exchange Cloud Service Canonical to meet Florida Medicaid LOB’s business requirement.

Later on, you can clone this existing transmission model to create a new one that inherits all the mapping changes made for Florida Medicaid, so you only have to make a few additional changes to meet another LOB’s business requirements.

Before creating trading partner agreements, the user must create a transmission model to use in that agreement.