EPIC BRIDGES EXAM SCRIPT 2026/2027 QUESTIONS
AND SOLUTIONS RATED A+
✔✔When the filer daemon attempts to process a message, there are three things that
can happen - ✔✔1) it files the message into Chronicles, possibly with one or more
warning or notification errors
2) its unable to file the entire message because there is something critically wrong with
the message. This is indicated by a fatal or critical error
3) it's unable to file the message because part of the record to which the message
needs to file is locked
✔✔Resequencing - ✔✔-a record is locked when a user or process is updating it
-IF a filer daemon receives a message for a patient, but that patient's record is already
being updated with an active lock, then the Filer stores the instruction for that message
on another queue- the Holding Queue.
-the message remains on the Holding Queue until the lock is released, so that the Filer
Daemon can move onto the next message in the Control Queue for processing
The filer Daemon checks messages on the Holding Queue periodically to determine
whether messages on the Holding Queue are ready to file
If the Filer Daemon encounters a message on the Control Queue that needs the same
locks as a message already on the Holding Queue, that message is also added to the
Holding Queue. This ensures that the messages always file into Chronicles in the same
order they were received for a patient
✔✔Holding QUeue - ✔✔Acts as a waiting area for messages that cannot get a lock to
store information to the database
✔✔Interconnect - ✔✔Epic's web services framework
-enables Epic applications to initiate and receive web service requests with an external
application
-sometimes used as an alternate communication method to TCP/IP for interfaces
-communicates messages securely using an HTTPS framework
✔✔An interface requires interconnect if one or more of the following are true: - ✔✔1) the
message uses an XML framework
2) communication requires HTTPS (web) protocol to reach securely outside your firewall
,3) the interface handles a job in a windows .NET framework, such as extracting an
embedded PDF from an HL7 v2 message and storing it to a BLOB server
✔✔Common uses of interconnect include - ✔✔e-Prescribing, Care Everywhere,
Meaningful Use interfaces to state registries (i.e. immunizations, results and cancer
reporting), Eligibility and X12 interfaces, EMFI and CHart Sunch interfaces, Research
Protocol interfaces, Real Time Location System Tracking, IHE interfaces, country-
speciifc interfaces
✔✔Outgoing Message Flow with Interconnect - ✔✔Comm daemon sends the content of
the data queue to Interconnect, wehre the message is packaged and sent
✔✔Incoming Message Flow with Interconnect - ✔✔-Exists within the firewall;
-constantly listening for messages coming into the system
-most incoming interconnect interfaces don't require a separate Comm Daemon, since
the Interconnect server handles all of the communication in this direction.
✔✔Chronicles - ✔✔contains all the information for a patient in the form of records
✔✔What are stored in the Event Queue, Data Queue, and Control Queue? - ✔✔Event
Queue: info needed to build a message (i.e. patient ID, encounter date, type of
message, etc.)
Data Queue: text of HL7 message and additional metadata
Control Queue: to-do list with instructions to send or file messages stored in the Data
Queue
✔✔What are two ways that interface messages are sent and received - ✔✔TCP/IP with
an interface engine is the most common.
Interconnect is used for HTTPS or other communication outside your local network
✔✔What does it mean for an interface to process a message? - ✔✔the incoming
interface's Filer Daemon tries to find the correct patient and file the data in the message
into Chronicles
the outgoing interface's Event Daemon creates an HL7 message, based on information
in Chronicles, and sends it out through the port defined in the Comm Daemon.
✔✔Are messages ever manually deleted from the Data Queue? - ✔✔No, never. They
are purged only by an automated purge job.
✔✔Communication Status (Interface Monitor Column) - ✔✔whether the comm daemon
is stopped or running
, ✔✔Total Recv'd/Sent (Interface Monitor Column) - ✔✔total number of messages sent
(outgoing) or received (incoming)
i.e. count
✔✔Last Recv'd/Sent (Interface Monitor Column) - ✔✔Number of the Last message sent
(outgoing) or received (incoming)
i.e. message number
✔✔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
AND SOLUTIONS RATED A+
✔✔When the filer daemon attempts to process a message, there are three things that
can happen - ✔✔1) it files the message into Chronicles, possibly with one or more
warning or notification errors
2) its unable to file the entire message because there is something critically wrong with
the message. This is indicated by a fatal or critical error
3) it's unable to file the message because part of the record to which the message
needs to file is locked
✔✔Resequencing - ✔✔-a record is locked when a user or process is updating it
-IF a filer daemon receives a message for a patient, but that patient's record is already
being updated with an active lock, then the Filer stores the instruction for that message
on another queue- the Holding Queue.
-the message remains on the Holding Queue until the lock is released, so that the Filer
Daemon can move onto the next message in the Control Queue for processing
The filer Daemon checks messages on the Holding Queue periodically to determine
whether messages on the Holding Queue are ready to file
If the Filer Daemon encounters a message on the Control Queue that needs the same
locks as a message already on the Holding Queue, that message is also added to the
Holding Queue. This ensures that the messages always file into Chronicles in the same
order they were received for a patient
✔✔Holding QUeue - ✔✔Acts as a waiting area for messages that cannot get a lock to
store information to the database
✔✔Interconnect - ✔✔Epic's web services framework
-enables Epic applications to initiate and receive web service requests with an external
application
-sometimes used as an alternate communication method to TCP/IP for interfaces
-communicates messages securely using an HTTPS framework
✔✔An interface requires interconnect if one or more of the following are true: - ✔✔1) the
message uses an XML framework
2) communication requires HTTPS (web) protocol to reach securely outside your firewall
,3) the interface handles a job in a windows .NET framework, such as extracting an
embedded PDF from an HL7 v2 message and storing it to a BLOB server
✔✔Common uses of interconnect include - ✔✔e-Prescribing, Care Everywhere,
Meaningful Use interfaces to state registries (i.e. immunizations, results and cancer
reporting), Eligibility and X12 interfaces, EMFI and CHart Sunch interfaces, Research
Protocol interfaces, Real Time Location System Tracking, IHE interfaces, country-
speciifc interfaces
✔✔Outgoing Message Flow with Interconnect - ✔✔Comm daemon sends the content of
the data queue to Interconnect, wehre the message is packaged and sent
✔✔Incoming Message Flow with Interconnect - ✔✔-Exists within the firewall;
-constantly listening for messages coming into the system
-most incoming interconnect interfaces don't require a separate Comm Daemon, since
the Interconnect server handles all of the communication in this direction.
✔✔Chronicles - ✔✔contains all the information for a patient in the form of records
✔✔What are stored in the Event Queue, Data Queue, and Control Queue? - ✔✔Event
Queue: info needed to build a message (i.e. patient ID, encounter date, type of
message, etc.)
Data Queue: text of HL7 message and additional metadata
Control Queue: to-do list with instructions to send or file messages stored in the Data
Queue
✔✔What are two ways that interface messages are sent and received - ✔✔TCP/IP with
an interface engine is the most common.
Interconnect is used for HTTPS or other communication outside your local network
✔✔What does it mean for an interface to process a message? - ✔✔the incoming
interface's Filer Daemon tries to find the correct patient and file the data in the message
into Chronicles
the outgoing interface's Event Daemon creates an HL7 message, based on information
in Chronicles, and sends it out through the port defined in the Comm Daemon.
✔✔Are messages ever manually deleted from the Data Queue? - ✔✔No, never. They
are purged only by an automated purge job.
✔✔Communication Status (Interface Monitor Column) - ✔✔whether the comm daemon
is stopped or running
, ✔✔Total Recv'd/Sent (Interface Monitor Column) - ✔✔total number of messages sent
(outgoing) or received (incoming)
i.e. count
✔✔Last Recv'd/Sent (Interface Monitor Column) - ✔✔Number of the Last message sent
(outgoing) or received (incoming)
i.e. message number
✔✔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
