EPIC BRIDGES FINAL EXAM 2026/2027 QUESTIONS AND
SOLUTIONS RATED A+
✔✔Time since last message( Interface Monitor Column) - ✔✔Elapsed time since a
message was last sent (for an outgoing interface) or received (for an incoming interface)
✔✔Queued Messages (Interface Monitor Column) - ✔✔number of messages waiting to
be sent (outgoing) or processed (incoming)
✔✔Queued Events (Interface Monitor Column) - ✔✔number of events waiting to be
processed from the Event Queue (outgoing only)
✔✔Waiting Messages (Interface Monitor Column) - ✔✔Number of messages waiting to
be processed from the Holding Queue
✔✔Filer/Event Status (Interface Monitor Column) - ✔✔Whether the Event Daemon
(outgoing) or Filer Daemon (incoming) is stopped or running
✔✔Background Monitor - ✔✔takes care of many tasks including determining whether
interfaces are running
✔✔Interface Monitor Definition - ✔✔Allows you to specify which interfaces should be
displayed in the Interface Monitor activity
✔✔Interface Monitor - ✔✔displays the interfaces from the definition. There are several
pieces of information available about each interface displayed:
-AIP ID
-Interface
-Queue
-Time since last message
-Total recv;d/sent
-Last recv'dsent
-queued messages
-queued events
-waiting messages
-communication status
-filer/event status
-time since comm start
-time since filer/event start
✔✔Message Purging Hierarchy - ✔✔1) Interface Level
2) Background Monitor Level
3) System Default of 30 Days
,If purge days are not specified for a given interface, the number of days in the
Background moniotr will be used. When neither of those purge days are specified, then
a system-wide default of 30 days is used.
✔✔Message Viewer - ✔✔Allows you to view the contents of an interface message in
the Data Queue
✔✔Radar - ✔✔provides a centralized location for important reporting tools and metrics
inside Hyperspace
✔✔Dashboard - ✔✔screen of information that pulls data from multiple sources into one
centralized location for a group of end users
✔✔Components - ✔✔units of conent that compose a dashboard Dashboards present
information from multiple components in one location instead of multiple acitivities
✔✔After you create an alert rule you need to.... - ✔✔Add it to the Background Monitor
alerts
✔✔When a rule is checking for a time, use the___operator - ✔✔greater than . If you use
equal, the rule will be true only if the the rule is evaluated at exactly the correct time
interval
✔✔Path to create an alert rule - ✔✔Epic>Admin>Interface Admin> Background Monitor
Definition
✔✔Rule Editor - ✔✔allows you to create conditions that are best for your organization.
Also contains an alert email message section to configure what text is included in the
body of the email sent for the alert.
✔✔Three options for starting interfaces after planned downtime - ✔✔1) manually start
your interfaces in the order you desire
2) automatically start all of your interfaces at once when the backgroun monitor is
started
3) automatically start all of your interfaces with rules to determine the order that
interfaces are started
✔✔For an interface to be eligible for either auto-start option: - ✔✔the autostart on
system startup must be checked on the startup.shutdown tab of the interface
specification
✔✔Autostart Blocking Conditions in the Background Monitor - ✔✔Allows you to specify
additional criteria that delays the startup of some interfaces
Path: Epic>Admin>Interface Admin>Background Monitor Definition> Autostart
, ✔✔Epic App for monitoring interfaces on mobile device - ✔✔Haiku
✔✔With Haiku, you can access what details about an interface? - ✔✔-ID and name
-Daemon status
-Date and time of last message activity
-Queue depth
✔✔Data Queue - ✔✔used to store messages that are received by Bridges or that are
created by Bridges to send out
contains the full text of the message along with some additional metadata
✔✔Message Viewer - ✔✔allows you to view the contents of an interface mesage in the
Data Queue
Path: Epic>Tools>Interface Utilities>View Messages
✔✔Message Viewer Tree - ✔✔the interface message selected is displayed in a tree in
the upper half of the Message Viewer.
Each segment in the message is displayed in its own branch of the tree.
✔✔Lower half of Message Viewer - ✔✔tabbed display window that can show you
several things about the message (i.e. message text, logged errors, message
submission details, and sesion history)
✔✔Message Editor - ✔✔similar to the Message Viewer but has the additional power of
allowing you to make changes to the message and subit your edited version
path: Epic>Tools>Interface Utilities>Edit Message
✔✔Create new message option - ✔✔only available for HL7 version 2 interfaces
✔✔Resubmit feature - ✔✔creates a new message that is added to the data queue and
the control queue to be processed
-marks any errors on the original message as resolved. If an error still holds true on an
incoming message, then a new instance of that error will be logged on the new
message as it is processed by the Filer Daemon
✔✔Resubmitting an Outgoing message - ✔✔sends the message directly out the
Communications Daemon, and no additional validation is done on the message content.
If a problem still exists on an outgoing message the error on the original message will
be marked as resolved, but a new error will not reappear on the new message
SOLUTIONS RATED A+
✔✔Time since last message( Interface Monitor Column) - ✔✔Elapsed time since a
message was last sent (for an outgoing interface) or received (for an incoming interface)
✔✔Queued Messages (Interface Monitor Column) - ✔✔number of messages waiting to
be sent (outgoing) or processed (incoming)
✔✔Queued Events (Interface Monitor Column) - ✔✔number of events waiting to be
processed from the Event Queue (outgoing only)
✔✔Waiting Messages (Interface Monitor Column) - ✔✔Number of messages waiting to
be processed from the Holding Queue
✔✔Filer/Event Status (Interface Monitor Column) - ✔✔Whether the Event Daemon
(outgoing) or Filer Daemon (incoming) is stopped or running
✔✔Background Monitor - ✔✔takes care of many tasks including determining whether
interfaces are running
✔✔Interface Monitor Definition - ✔✔Allows you to specify which interfaces should be
displayed in the Interface Monitor activity
✔✔Interface Monitor - ✔✔displays the interfaces from the definition. There are several
pieces of information available about each interface displayed:
-AIP ID
-Interface
-Queue
-Time since last message
-Total recv;d/sent
-Last recv'dsent
-queued messages
-queued events
-waiting messages
-communication status
-filer/event status
-time since comm start
-time since filer/event start
✔✔Message Purging Hierarchy - ✔✔1) Interface Level
2) Background Monitor Level
3) System Default of 30 Days
,If purge days are not specified for a given interface, the number of days in the
Background moniotr will be used. When neither of those purge days are specified, then
a system-wide default of 30 days is used.
✔✔Message Viewer - ✔✔Allows you to view the contents of an interface message in
the Data Queue
✔✔Radar - ✔✔provides a centralized location for important reporting tools and metrics
inside Hyperspace
✔✔Dashboard - ✔✔screen of information that pulls data from multiple sources into one
centralized location for a group of end users
✔✔Components - ✔✔units of conent that compose a dashboard Dashboards present
information from multiple components in one location instead of multiple acitivities
✔✔After you create an alert rule you need to.... - ✔✔Add it to the Background Monitor
alerts
✔✔When a rule is checking for a time, use the___operator - ✔✔greater than . If you use
equal, the rule will be true only if the the rule is evaluated at exactly the correct time
interval
✔✔Path to create an alert rule - ✔✔Epic>Admin>Interface Admin> Background Monitor
Definition
✔✔Rule Editor - ✔✔allows you to create conditions that are best for your organization.
Also contains an alert email message section to configure what text is included in the
body of the email sent for the alert.
✔✔Three options for starting interfaces after planned downtime - ✔✔1) manually start
your interfaces in the order you desire
2) automatically start all of your interfaces at once when the backgroun monitor is
started
3) automatically start all of your interfaces with rules to determine the order that
interfaces are started
✔✔For an interface to be eligible for either auto-start option: - ✔✔the autostart on
system startup must be checked on the startup.shutdown tab of the interface
specification
✔✔Autostart Blocking Conditions in the Background Monitor - ✔✔Allows you to specify
additional criteria that delays the startup of some interfaces
Path: Epic>Admin>Interface Admin>Background Monitor Definition> Autostart
, ✔✔Epic App for monitoring interfaces on mobile device - ✔✔Haiku
✔✔With Haiku, you can access what details about an interface? - ✔✔-ID and name
-Daemon status
-Date and time of last message activity
-Queue depth
✔✔Data Queue - ✔✔used to store messages that are received by Bridges or that are
created by Bridges to send out
contains the full text of the message along with some additional metadata
✔✔Message Viewer - ✔✔allows you to view the contents of an interface mesage in the
Data Queue
Path: Epic>Tools>Interface Utilities>View Messages
✔✔Message Viewer Tree - ✔✔the interface message selected is displayed in a tree in
the upper half of the Message Viewer.
Each segment in the message is displayed in its own branch of the tree.
✔✔Lower half of Message Viewer - ✔✔tabbed display window that can show you
several things about the message (i.e. message text, logged errors, message
submission details, and sesion history)
✔✔Message Editor - ✔✔similar to the Message Viewer but has the additional power of
allowing you to make changes to the message and subit your edited version
path: Epic>Tools>Interface Utilities>Edit Message
✔✔Create new message option - ✔✔only available for HL7 version 2 interfaces
✔✔Resubmit feature - ✔✔creates a new message that is added to the data queue and
the control queue to be processed
-marks any errors on the original message as resolved. If an error still holds true on an
incoming message, then a new instance of that error will be logged on the new
message as it is processed by the Filer Daemon
✔✔Resubmitting an Outgoing message - ✔✔sends the message directly out the
Communications Daemon, and no additional validation is done on the message content.
If a problem still exists on an outgoing message the error on the original message will
be marked as resolved, but a new error will not reappear on the new message
