When an interface uses Interconnect (Epic ' s HTTPS-based framework) for incoming data, Interconnect receives the message directly via a web service call. Because it is an HTTPS connection rather than a standard TCP/IP socket, Interconnect handles the initial receipt and places the message directly onto the Bridges Data Queue for the Filer Daemon to process.

The Event Queue is the first stop for outgoing data. When an action occurs in Epic (like a discharge), a trigger is placed in the Event Queue. The Event Daemon then picks up this trigger to build the actual message.
Incoming interfaces do not use an Event Queue because the message is already built by the external system when it arrives.

The primary purpose of the Error Log Report is to provide a granular list of individual Error instances.
While these errors are linked to messages, the report result list displays the errors themselves, allowing analysts to see the specific failure reason, time, and error code for every occurrence.

When mapping data that exists as an Epic category list (such as Marital Status or Gender), the Auto-lookup feature significantly reduces manual build. When enabled, Bridges automatically pulls in the internal Epic values from the linked category list. The analyst then only needs to provide the corresponding external values from the vendor, rather than manually typing out every possible Epic internal ID and title.

In HL7 v2 messaging, a standard naming convention is used to identify specific data locations. The format follows Segment-Field.Component.Subcomponent. For example, PID-5 represents the Patient Name field. To specify a component within that field (like the Given Name, which is the 2nd component), a dot is used as a separator. Therefore, PID-5.2 correctly identifies the 2nd component of the 5th field.