EDI101 CEE: Bridges Interfaces Application Essentials Exam (2026 Version) Questions and Answers

Bridges uses a hierarchical approach for profile variables. The system first looks at the specific Interface record; if that is null, it looks at the Interface Specification; if that is also null, it falls back to the Interface System Defaults . Since the specific transcription interface has no value, it inherits the ' 8 ' defined at the system level.

Even in a fictional scenario, the rule remains: if you are mapping record-level identifiers (the unique ID for each individual robot record), you must use Identity . Translation Tables would only be appropriate for the " robot types " (since there are only a dozen), but for the thousands of individual robot records themselves, Identity provides the necessary cross-referencing between Epic and external systems.

Both Message Search and the Message Companion are patient-centric tools. Message Search allows for broad criteria including patient identifiers and timestamps across various interfaces. The Message Companion is a specialized tool often accessed directly from patient clinical records, allowing users to see all incoming and outgoing messages specifically for that patient within a defined timeframe.

The Criteria tab allows for precise filtering of logs. Analysts can search for errors associated with a specific message (Option B), filter for specific error codes to investigate a known issue (Option C), or isolate critical issues by filtering for a severity of " Failure " (Option D). Severity overrides (Option A) are a configuration setting rather than a standard search filter for the log report itself.

To efficiently manage investigation documentation, Epic provides the Error Steps Copy Utility within the Bridges Text-based menus. This utility allows administrators to take a set of resolution steps defined for one error/interface and copy them to others, preventing the need for manual duplicate entry.

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.

Workqueue rules in Bridges are generally not retroactive by default. Once you update a rule, only future occurrences of the error will be caught by the new logic (Option A). Any errors that were already in the workqueue from previous rules will remain there (Option C). To get past occurrences of the new error into the workqueue, you would need to run the Maintenance utility described in Question 26.

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.

In Bridges, an error is tied to a specific instance of a message. Resubmitting or retriggering a message (Options B and D) essentially tells the system to try again or create a new message, which clears or " deletes " the error status associated with the previous failed attempt. Additionally, users can manually select Delete Error within an Error Log Report (Option C) to administratively clear an error that no longer requires action. Releasing an error from a workqueue (Option A) merely removes it from that specific list; it does not delete the error from the system logs.

Retriggering is specifically an outgoing interface action. Therefore, Incoming messages (Option D) cannot be retriggered. Additionally, to maintain a clear audit trail and prevent logic errors, Bridges does not allow you to retrigger a message that was already the result of a retrigger (Option A).

Similar to profile variables, purge settings follow a hierarchy where the more specific configuration overrides the more general one. Because the Interface Specification is more specific than the System Definitions, its value of 45 days takes precedence. Messages for interfaces using that specification will be eligible for purging after 45 days.

If an incoming message arrives for a patient whose record is currently being edited by a user in Hyperspace, the record is " locked. " Bridges cannot file to a locked record, so it places the message in the Holding Queue . Once the user finishes their work and the lock is released, the message is moved back to the Data Queue to be filed.