EPIC BRIDGES PRACTICE EXAM 2026/2027 QUESTIONS
AND SOLUTIONS RATED A+
✔✔Are you deleting a message from the data queue with the Skip message feature? -
✔✔No. You can never manually delete a message with any bridges utility. This utility
removes the entry only from the Control Queue
✔✔If you are running a message search, what best practices could you use to reduce
the amount of messages returned by your search or finish your search quicker? - ✔✔-
limit the time period searched
-search for unique identifiers (CSN, MRN, order ID) as opposed to patient name
-include multiple search values in your search criteria
✔✔Bridges Error Codes - ✔✔Each error logged by bridges includes a discrete numeric
error code that allows us to group multiple occurrences of the same problem
Errors sharing the same error code also include additional information specific to the
occurrence of that error
✔✔Bridges Error Severities - ✔✔Epic supports five error severities: critical, fatal,
warning, notification, and none
✔✔Critical error - ✔✔indicates that the problem is serious enough to prevent the
content from being processed
✔✔Fatal error - ✔✔indicates that the problem is serious enough to prevent the content
from being processed
✔✔Notification error - ✔✔presents information that might be of interest; logs an error
but content is still processed
✔✔Warning error - ✔✔something went wrong, but not enough to prevent content from
being processed
✔✔Error Scope - ✔✔indicates the context of a given error.
3 levels at which an error can be logged:
1) daemon,
2) message
3) local
✔✔The majority of errors logged by interfaces are ______in scope - ✔✔message-
scoped
✔✔Local-scope error - ✔✔error applies only to part of the message, and the rest of the
message might have been processed successfully
, ✔✔daemon-scoped error - ✔✔indicates problem with the interface configuration, and
might require that the interface be stopped so that the problem can be addressed
✔✔Error Log Report - ✔✔allows you to search for logged errors, display them, and take
actions to resolve them
Path: Epic>Tools>Interface Utilties>Error Log
✔✔PID-7 - ✔✔patient date of birth
✔✔Each type of error can be gathered into one of three possible actions: - ✔✔1) Fix
2) Work
3) Suppress
✔✔"Fix" errors - ✔✔problems that can be eliminated by a change to the system to
permanently elimnate the problem
✔✔"Suppress" errors - ✔✔some errors are benign and require no further action, so
those you can simply suppress
✔✔"Work" errors - ✔✔errors you expect to happen periodically and will require manual
intervention as part of the ongoing maintenance of the interface
✔✔Possible steps one might take to resolve a "Fix" or "Work" error - ✔✔-correct a data
mapping issue within Epic
-resubmit or retrigger the message in Bridges
-edit the message content in Bridges and then resubmit it
-update a value or setting in the sending system and retrigger the message to Epic
-change the handling of messages in your interface engine
-manually change a data value in Chronicles
-search for messages filed to the same patient
✔✔Deleting an Error - ✔✔marks the error as resolved;
happens if: you already made a change in the system to correct the issue,
the error is innocuous
-a later message has filed and rendered the message with the error obsolete
✔✔Deleted error - ✔✔still exists in a resolved state
can always access details about the error in Bridges, so long as the corresponding
message exists in the Data Queue
✔✔Error Workqueues - ✔✔tool for managing and assigning errors that fall into the
ongoing maintenance category
AND SOLUTIONS RATED A+
✔✔Are you deleting a message from the data queue with the Skip message feature? -
✔✔No. You can never manually delete a message with any bridges utility. This utility
removes the entry only from the Control Queue
✔✔If you are running a message search, what best practices could you use to reduce
the amount of messages returned by your search or finish your search quicker? - ✔✔-
limit the time period searched
-search for unique identifiers (CSN, MRN, order ID) as opposed to patient name
-include multiple search values in your search criteria
✔✔Bridges Error Codes - ✔✔Each error logged by bridges includes a discrete numeric
error code that allows us to group multiple occurrences of the same problem
Errors sharing the same error code also include additional information specific to the
occurrence of that error
✔✔Bridges Error Severities - ✔✔Epic supports five error severities: critical, fatal,
warning, notification, and none
✔✔Critical error - ✔✔indicates that the problem is serious enough to prevent the
content from being processed
✔✔Fatal error - ✔✔indicates that the problem is serious enough to prevent the content
from being processed
✔✔Notification error - ✔✔presents information that might be of interest; logs an error
but content is still processed
✔✔Warning error - ✔✔something went wrong, but not enough to prevent content from
being processed
✔✔Error Scope - ✔✔indicates the context of a given error.
3 levels at which an error can be logged:
1) daemon,
2) message
3) local
✔✔The majority of errors logged by interfaces are ______in scope - ✔✔message-
scoped
✔✔Local-scope error - ✔✔error applies only to part of the message, and the rest of the
message might have been processed successfully
, ✔✔daemon-scoped error - ✔✔indicates problem with the interface configuration, and
might require that the interface be stopped so that the problem can be addressed
✔✔Error Log Report - ✔✔allows you to search for logged errors, display them, and take
actions to resolve them
Path: Epic>Tools>Interface Utilties>Error Log
✔✔PID-7 - ✔✔patient date of birth
✔✔Each type of error can be gathered into one of three possible actions: - ✔✔1) Fix
2) Work
3) Suppress
✔✔"Fix" errors - ✔✔problems that can be eliminated by a change to the system to
permanently elimnate the problem
✔✔"Suppress" errors - ✔✔some errors are benign and require no further action, so
those you can simply suppress
✔✔"Work" errors - ✔✔errors you expect to happen periodically and will require manual
intervention as part of the ongoing maintenance of the interface
✔✔Possible steps one might take to resolve a "Fix" or "Work" error - ✔✔-correct a data
mapping issue within Epic
-resubmit or retrigger the message in Bridges
-edit the message content in Bridges and then resubmit it
-update a value or setting in the sending system and retrigger the message to Epic
-change the handling of messages in your interface engine
-manually change a data value in Chronicles
-search for messages filed to the same patient
✔✔Deleting an Error - ✔✔marks the error as resolved;
happens if: you already made a change in the system to correct the issue,
the error is innocuous
-a later message has filed and rendered the message with the error obsolete
✔✔Deleted error - ✔✔still exists in a resolved state
can always access details about the error in Bridges, so long as the corresponding
message exists in the Data Queue
✔✔Error Workqueues - ✔✔tool for managing and assigning errors that fall into the
ongoing maintenance category
