EPIC BRIDGES Exam | Updated Questions
and Answers | Most Recent 2026 Edition
• An interface message contains... -✓✓ Data about an event (like a patient being
admitted to the hospital)
• MSH-11 -✓✓ HL7 Processing ID
• MSH-12 -✓✓ HL7 Version ID
• Segment Identifier -✓✓ Three character code that identifies the kind of data the
segment contains
• PID-3 -✓✓ Patient ID
• PID-5 -✓✓ Patient Name
• PID-7 -✓✓ Patient Date of Birth
• Encoding Character -✓✓ Break HL7 message down into smaller pieces
FCRES
1. Field Separator |
2. Component Separator ^
3. Repetition Separator ~
4. Escape Character \
,5. Subcomponent Separator &
• Escape Sequence (assumes Escape character is \) -✓✓ 1. Field Separator \F\
2. Component Separator \S\
3. Repetition Separator \R\
4. Escape Character \E\
5. Subcomponent Separator \T\
• NTE Segment -✓✓ "Note" segment containing custom data that relates to the
segment it follows.
• Z Segment -✓✓ Custom segment
• Are empty fields needed following the final entered value in an HL7 message? -
✓✓ No
• Blank Fields -✓✓ These are not filed
• HL7 Delete Character -✓✓ Defined by information between double quotations
("-")
• FHIR -✓✓ Specifies RESTful exchange method via HTTPs to access data.
Developed to address limitations of HL7.
• Bridges supports these standards -✓✓ HL7, X12, FHIR, NCPDP, and Direct
, • Event -✓✓ Small set of values. Contains needed info to build a message (like
Patient ID) and contains directions for where Interface should pull contents to
build a message.
• Queue -✓✓ Storage location outside Chronicles database structure.
• Event Daemon -✓✓ Processes the Event Queue
Outgoing: Pulls from Event Queue, builds message, and removes the event from
the event Queue
Incoming:
• Daemon (Outgoing) -✓✓ Background process that does not require user action.
• Data Queue -✓✓ Outgoing: Contains the full text of the message along with
additional metadata (i.e. timestamp)
• Control Queue -✓✓ Outgoing: Contains very little data. Processed by
Communications Daemon. Maintains list of messages waiting to be processed.
Incoming: Processed by Filer Daemon.
• Comm Daemon -✓✓ Outgoing: TCP/IP. Reads instruction from Control Queue
and copies corresponding message from Data Queue. Sends message out of Epic
and waits for ACK. Deletes instruction from Control Queue.
Incoming: TCP/IP. Constantly listens for incoming messages. Validates MSH-11
and MSH-12 before accepting.
and Answers | Most Recent 2026 Edition
• An interface message contains... -✓✓ Data about an event (like a patient being
admitted to the hospital)
• MSH-11 -✓✓ HL7 Processing ID
• MSH-12 -✓✓ HL7 Version ID
• Segment Identifier -✓✓ Three character code that identifies the kind of data the
segment contains
• PID-3 -✓✓ Patient ID
• PID-5 -✓✓ Patient Name
• PID-7 -✓✓ Patient Date of Birth
• Encoding Character -✓✓ Break HL7 message down into smaller pieces
FCRES
1. Field Separator |
2. Component Separator ^
3. Repetition Separator ~
4. Escape Character \
,5. Subcomponent Separator &
• Escape Sequence (assumes Escape character is \) -✓✓ 1. Field Separator \F\
2. Component Separator \S\
3. Repetition Separator \R\
4. Escape Character \E\
5. Subcomponent Separator \T\
• NTE Segment -✓✓ "Note" segment containing custom data that relates to the
segment it follows.
• Z Segment -✓✓ Custom segment
• Are empty fields needed following the final entered value in an HL7 message? -
✓✓ No
• Blank Fields -✓✓ These are not filed
• HL7 Delete Character -✓✓ Defined by information between double quotations
("-")
• FHIR -✓✓ Specifies RESTful exchange method via HTTPs to access data.
Developed to address limitations of HL7.
• Bridges supports these standards -✓✓ HL7, X12, FHIR, NCPDP, and Direct
, • Event -✓✓ Small set of values. Contains needed info to build a message (like
Patient ID) and contains directions for where Interface should pull contents to
build a message.
• Queue -✓✓ Storage location outside Chronicles database structure.
• Event Daemon -✓✓ Processes the Event Queue
Outgoing: Pulls from Event Queue, builds message, and removes the event from
the event Queue
Incoming:
• Daemon (Outgoing) -✓✓ Background process that does not require user action.
• Data Queue -✓✓ Outgoing: Contains the full text of the message along with
additional metadata (i.e. timestamp)
• Control Queue -✓✓ Outgoing: Contains very little data. Processed by
Communications Daemon. Maintains list of messages waiting to be processed.
Incoming: Processed by Filer Daemon.
• Comm Daemon -✓✓ Outgoing: TCP/IP. Reads instruction from Control Queue
and copies corresponding message from Data Queue. Sends message out of Epic
and waits for ACK. Deletes instruction from Control Queue.
Incoming: TCP/IP. Constantly listens for incoming messages. Validates MSH-11
and MSH-12 before accepting.
