Key details for this exam, checked against the published exam outline
Each question shows the correct answer and an explanation of why it is right
When changing a profile variable, you must restart the affected interface for the setting to take effect.
Profile variables are configuration settings that the interface daemons read when they initialize. If a change is made to a profile variable while the interface is running, the active daemon will not recognize the update. A restart of the Communications and Filer daemons is required to force the system to reload the new configuration from the database.
The VISIT_ITEM profile variable is set to '8' in the Interface System Defaults. Your "Incoming Transcription" interface doesn't have a value populated for the VISIT_ITEM profile variable. What value will the "Incoming Transcription" interface use for the value of the VISIT_ITEM profile variable?
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.
Which of the following actions will mark an error as deleted? (SELECT ALL THAT APPLY)
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.
A new error started logging to your interface and your team decides that this error should be worked on an existing workqueue. You properly update the workqueue rule to include the new error. Which of the following will your workqueue contain moving forward if you take no other actions? (SELECT ALL THAT APPLY)
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.
Which of the following are options in the Criteria tab of the Error Log Report? (SELECT ALL THAT APPLY)
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.
Which queue is unique to outgoing interfaces?
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.
All Triggers in Interface System Defaults can only be configured to trigger messages to a single interface.
Epic's trigger logic is highly flexible. A single event in Chronicles (such as a patient admission) can be configured within the System Defaults or specialized trigger tables to send data to multiple interfaces simultaneously. This is common when an admission needs to notify a Lab system, a Pharmacy system, and a Dietary system all at once.
5 domains from the Epic Systems EDI101 exam outline, with approximate weightings. Every sample question above is tagged with the domain it comes from
Understand Bridges architecture, message types, and the role of interfaces in Epic workflows. Learn core terminology such as inbound and outbound transactions, acknowledgments, and error handling processes.
Master initial configuration steps and application settings for Bridges interfaces. This domain covers environment preparation and the foundational setup work needed before interfaces can operate.
Sample question from this domain above: Q1
Map data fields between Epic and external systems, handle data transformations, and manage field validation. Work with real-world scenarios such as patient registration feeds, order transmission, and result imports.
Sample question from this domain above: Q2
Diagnose interface failures, interpret error logs, and resolve common transmission issues. Monitor queue status, restart failed transactions, and implement corrective actions without disrupting live operations.
Apply standards for interface naming, documentation, and change control. Design scalable solutions, plan maintenance windows, and coordinate with clinical and business teams to minimize downtime.
Common questions about the exam itself
