Which of the following are possible reasons that an incoming message might show as "waiting" in your message search results? (SELECT ALL THAT APPLY)
Answer : A, B, C
A message shows as 'waiting' when it has been received but not yet processed by the Filer. Common causes include:
High Volume: The Filer Daemon is working through a backlog.
Filer Daemon Stopped: If the Filer is not running, no messages can move from the queue to the database.
Holding Queue: The message is specifically waiting for a patient record lock to be released before it can file.
The Communications Daemon (Option D) is responsible for receiving the message; if it weren't running, the message wouldn't even be in the search results yet.
Question 2
Table translations can be either case sensitive or not case sensitive.
Answer : A
Bridges provides a configuration toggle for Case Sensitivity within translation tables. This is crucial because some external systems might send values like 'M' and 'm' interchangeably, while others might use case to distinguish between two different codes. Setting this correctly ensures that the interface accurately matches the incoming string to the intended internal value.
Question 3
Many interfaces that file patient information are required by default to use Patient Validation and may not start without documenting why the interface should skip validation.
Answer : A
Because of the high risk associated with misidentifying patients, Epic embeds 'hard stops' in the Bridges configuration. For many standard interface types, the system requires Patient Validation to be active. If an organization decides to disable it, the administrator must provide a formal justification within the system before the interface is permitted to start.
Question 4
Which of the following actions will mark an error as deleted? (SELECT ALL THAT APPLY)
Answer : B, C, D
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.
Question 5
From the following options, which is an action you cannot perform within the Error Resolution Planner activity?
Answer : C
As noted in the previous question, the Error Resolution Planner is used for documenting (Option A), triaging (Option B), and assigning (Option D) tasks related to errors. It does not have the functional authority to actually suppress an error code (Option C); that is a configuration change made at the Interface or System level.
Question 6
When changing a profile variable, you must restart the affected interface for the setting to take effect.
Answer : A
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.
Question 7
After opening a message in the messages activity, you find that you are unable to retrigger the message. What are some reasons that this might be the case? (SELECT ALL THAT APPLY)
Answer : A, B
Retriggering is the process of asking Epic to re-create an outgoing message based on current data. You cannot retrigger an incoming message because retriggering is an outgoing function (the equivalent for incoming is 'resubmit'). Furthermore, Bridges prevents 'recursive' retriggering---you cannot retrigger a message that was itself created by a retriggering action (Option A) to prevent duplicate processing loops.
All Official Question Types