EPIC BRIDGES UPDATED EXAM SCRIPT QUESTIONS AND
ANSWERS GUARANTEE A+
✔✔Queue - ✔✔storage location outside of Chronicles database structure
✔✔Event Queue is procesed by... - ✔✔the Event Daemon
✔✔Daemon (Outgoing Message Flow) - ✔✔process that runs in the background without
any direct user action
✔✔Event Daemon (Outgoing Message Flow) - ✔✔pulls an event off the Event Queue,
uses the information in the event to build the message and finally deletes the event from
the event queue.
The event daemon puts the message it has built onto the data queue and adds an
instruction to the Control Queue
builds an HL7 message based on data pulled from Chronicles
✔✔Data Queue (Outgoing Message Flow) - ✔✔contains the full text of the message
along with some additional metadata (i.e. timestamp) about message processing
✔✔Control Queue (Outgoing Message Flow) - ✔✔a to-do list and contains very little
data
-processed by the Communications Daemon
-maintains a list of messages waiting to be processed
✔✔Comm Deamon (Outgoing Message Flow) - ✔✔reads an instruction from the Control
Queue and copies the appropriate message off the Data Queue
-sends the message out of Epic and waits for an ACK to be reutrned
-deletes instruction from the Control Queue and proceeds to the next instruction
-sends or receives acknowledgments over a TCP/IP connection
✔✔Comm Daemon (Incoming Message Flow) - ✔✔-listens constantly for messages
coming into the system
-validates MSH-11 and MSH-12 before accepting it, storing it in the data queue, and
adding instruction to the control queue
-sends or receives acknowledgments over a TCP/IP connection
✔✔Control Queue (Incoming Message Flow) - ✔✔processed by the Filer Daemon
,✔✔Filer Daemon - ✔✔pulls an instruction from the Control Queue, retrieves the
corresponding message from the Data Queue, and then attempts to file the message.
Filing means that the Filer Daemon attempts to store the data in Chronicles.
If the filer daemon is successful, the data is added to the appropriate records in
Chronicles.
When there is a problem, and the data in the message cannot be filed, an interface
error message is logged
Translates HL7 data into something that can be stored to the database
✔✔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
ANSWERS GUARANTEE A+
✔✔Queue - ✔✔storage location outside of Chronicles database structure
✔✔Event Queue is procesed by... - ✔✔the Event Daemon
✔✔Daemon (Outgoing Message Flow) - ✔✔process that runs in the background without
any direct user action
✔✔Event Daemon (Outgoing Message Flow) - ✔✔pulls an event off the Event Queue,
uses the information in the event to build the message and finally deletes the event from
the event queue.
The event daemon puts the message it has built onto the data queue and adds an
instruction to the Control Queue
builds an HL7 message based on data pulled from Chronicles
✔✔Data Queue (Outgoing Message Flow) - ✔✔contains the full text of the message
along with some additional metadata (i.e. timestamp) about message processing
✔✔Control Queue (Outgoing Message Flow) - ✔✔a to-do list and contains very little
data
-processed by the Communications Daemon
-maintains a list of messages waiting to be processed
✔✔Comm Deamon (Outgoing Message Flow) - ✔✔reads an instruction from the Control
Queue and copies the appropriate message off the Data Queue
-sends the message out of Epic and waits for an ACK to be reutrned
-deletes instruction from the Control Queue and proceeds to the next instruction
-sends or receives acknowledgments over a TCP/IP connection
✔✔Comm Daemon (Incoming Message Flow) - ✔✔-listens constantly for messages
coming into the system
-validates MSH-11 and MSH-12 before accepting it, storing it in the data queue, and
adding instruction to the control queue
-sends or receives acknowledgments over a TCP/IP connection
✔✔Control Queue (Incoming Message Flow) - ✔✔processed by the Filer Daemon
,✔✔Filer Daemon - ✔✔pulls an instruction from the Control Queue, retrieves the
corresponding message from the Data Queue, and then attempts to file the message.
Filing means that the Filer Daemon attempts to store the data in Chronicles.
If the filer daemon is successful, the data is added to the appropriate records in
Chronicles.
When there is a problem, and the data in the message cannot be filed, an interface
error message is logged
Translates HL7 data into something that can be stored to the database
✔✔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
