EPIC BRIDGES COMPREHENSIVE STUDY
GUIDE 2026 INTERFACE BUILDING
CONCEPTS SOLUTIONS VERIFIED A+
◉ An interface message contains....
Answer: Data about an event (like a patient being admitted to the
hospital)
◉ MSH-11 and MSH-12 are...
Answer: the HL7 processing ID and version; Epic checks these
values on an incoming message and rejects the message if they do
not match the expected values
◉ Segment Identifier
Answer: Three character code that identifies what kind of data that
segment contains
◉ PID-5
Answer: patient name
◉ NTE segment
,Answer: can follow many different segments
◉ Z-segment
Answer: custom segment for a specific implementation
◉ Is it necessary to send empty fields following the last valued field?
Answer: No
◉ Within a field do you need to send all components?
Answer: Only as many as are valued
◉ Blank fields...
Answer: don't file anything
◉ Delete character HL7
Answer: double quotes " "--- tells the receiving system to delete a
piece of info it has
◉ FHIR
Answer: specifies RESTful exchange method via HTTPs to access
data
,◉ Other standards supported by Bridges
Answer: X12, FHIR, NCPDP, DICOM, and Direct
◉ Event (in context of outgoing message flow)
Answer: small set of values with the necessary info to build the
message: patient ID, patient contact, type of message, and additional
info
-contains directions for where the interface should pull the
information it needs from the database
◉ Queue
Answer: storage location outside of Chronicles database structure
◉ Event Queue is procesed by...
Answer: the Event Daemon
◉ Daemon (Outgoing Message Flow)
Answer: process that runs in the background without any direct
user action
◉ Event Daemon (Outgoing Message Flow)
, Answer: 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)
Answer: contains the full text of the message along with some
additional metadata (i.e. timestamp) about message processing
◉ Control Queue (Outgoing Message Flow)
Answer: 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)
Answer: 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
GUIDE 2026 INTERFACE BUILDING
CONCEPTS SOLUTIONS VERIFIED A+
◉ An interface message contains....
Answer: Data about an event (like a patient being admitted to the
hospital)
◉ MSH-11 and MSH-12 are...
Answer: the HL7 processing ID and version; Epic checks these
values on an incoming message and rejects the message if they do
not match the expected values
◉ Segment Identifier
Answer: Three character code that identifies what kind of data that
segment contains
◉ PID-5
Answer: patient name
◉ NTE segment
,Answer: can follow many different segments
◉ Z-segment
Answer: custom segment for a specific implementation
◉ Is it necessary to send empty fields following the last valued field?
Answer: No
◉ Within a field do you need to send all components?
Answer: Only as many as are valued
◉ Blank fields...
Answer: don't file anything
◉ Delete character HL7
Answer: double quotes " "--- tells the receiving system to delete a
piece of info it has
◉ FHIR
Answer: specifies RESTful exchange method via HTTPs to access
data
,◉ Other standards supported by Bridges
Answer: X12, FHIR, NCPDP, DICOM, and Direct
◉ Event (in context of outgoing message flow)
Answer: small set of values with the necessary info to build the
message: patient ID, patient contact, type of message, and additional
info
-contains directions for where the interface should pull the
information it needs from the database
◉ Queue
Answer: storage location outside of Chronicles database structure
◉ Event Queue is procesed by...
Answer: the Event Daemon
◉ Daemon (Outgoing Message Flow)
Answer: process that runs in the background without any direct
user action
◉ Event Daemon (Outgoing Message Flow)
, Answer: 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)
Answer: contains the full text of the message along with some
additional metadata (i.e. timestamp) about message processing
◉ Control Queue (Outgoing Message Flow)
Answer: 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)
Answer: 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
