EPIC BRIDGES EXAM TEST BANK REAL EXAM 300 QUESTIONS
AND CORRECT ANSWERS(DETAILED ANSWERS)|AGRADE
Event Daemon - ANSWER: Builds HL7 messages based on data pulled from the
database
Control Queue - ANSWER: Maintains a list of messages waiting to be processed
Interconnect - ANSWER: Communicates messages securely using an HTTPS
framework
Chronicles - ANSWER: Contains all the information for a patient in the form of
records
Trigger - ANSWER: Serves as the integration point between the application workflow
and Bridges
Holding Queue - ANSWER: Acts as a waiting area for messages that cannot get a lock
to store information to the database
Data Queue - ANSWER: Contains HL7 messages along with timestamp information
about the message processing
Event - ANSWER: Contains directions for where the interface should pull the
information it needs from the database
Filer Daemon - ANSWER: Translate HL7 data into something that can be stored to the
database
Communication Daemon - ANSWER: Sends or receives acknowledgements over
TCP/IP connection
AIP ID - ANSWER: ID of the Interface Profile
Interface - ANSWER: Name of the Interface. This may be overridden in the Interface
Monitor Definition
Queue - ANSWER: Interface queue number where the messages for the interface are
stored. Typically this is the exact same number as the interface ID
Time Since Last Msg - ANSWER: Elapse time since a message was last sent or
received
Total Recv'd/Sent - ANSWER: Total number of messages sent or received
,Queued Messages - ANSWER: Number of messages waiting to be sent or processed
from the Control Queue
Queued Events - ANSWER: Number of events waiting to be processed from the Event
Queue
Waiting Messages - ANSWER: Number of messages waiting to be processed from the
Holding Queue
Communication Status - ANSWER: Whether the Communication Daemon is Stopped
or Running
Filer/Event Status - ANSWER: Whether the Event Daemon or Filer Daemon is
Stopped or Running
System Purge Default - ANSWER: 30 days
Edit Field - ANSWER: Edit the currently selected field; same effect as double clicking
on a field
Append Field - ANSWER: Append a blank field to the end of the currently selected
segment
Append Multiple Fields - ANSWER: Append several fields to the end of the currently
selected segment; a dialog box allows you to specify the number of fields to append
Edit Segment - ANSWER: Edit the currently selected segment; similar to editing a
field, but you can edit the entire segment at once
Insert Segment - ANSWER: Insert a new segment after the currently selected
segment; a dialog box allows you to specify the segment ID
Delete Segment - ANSWER: Delete the currently selected segment
Restore - ANSWER: Discard all changes you have made to the message and revert to
the original, unedited version
Resubmit - ANSWER: Submit your new copy of the interface message
Event Daemon - ANSWER: Builds HL7 messages based on data pulled from the
database
Control Queue - ANSWER: Maintains a list of messages waiting to be processed
Interconnect - ANSWER: Communicates messages securely using an HTTPS
framework
,Chronicles - ANSWER: Contains all the information for a patient in the form of
records (Epic's patient DB)
Trigger - ANSWER: Serves as the integration point between the application workflow
and Bridges
Holding Queue. The Filer Daemon bounces back and forth between the Holding and
Control/Data Queues. - ANSWER: Acts as a waiting area for messages that cannot get
a lock to store information to the database
Data Queue - ANSWER: Contains HL7 messages along with timestamp information
about the message processing
Event - ANSWER: Contains directions for where the interface should pull the
information it needs from the database
Filer Daemon - ANSWER: Translate HL7 data into something that can be stored to the
database
Communication Daemon - ANSWER: Sends or receives acknowledgements over
TCP/IP connection
AIP ID - ANSWER: ID of the Interface Profile
Queued Messages - ANSWER: Number of messages waiting to be sent or processed
from the Control Queue
Queued Events - ANSWER: Number of events waiting to be processed from the Event
Queue
Waiting Messages - ANSWER: Number of messages waiting to be processed from the
Holding Queue
Filer/Event Status - ANSWER: Whether the Event Daemon or Filer Daemon is
Stopped or Running
30 days - ANSWER: System Purge Default
Resubmit - ANSWER: Submit your new copy of the interface message
It is a note segment and is contextual. - ANSWER: Why is the NTE segment special?
The empty field will be ignored and not file to Chronicles. The delete character will
delete data from Chronicles for that field. - ANSWER: What is the difference between
an empty/null field ( || ) and the delete character ( |""| )?
, False. They are only auto-purged based on configuration (or 30 day default). -
ANSWER: T/F: Messages can be manually deleted from the data queue.
Profile Variable Audit Report - ANSWER: Compares settings of profile variables across
interfaces.
Interface Specification Audit Report - ANSWER: Tracks the changes to a profile
variable within a specific interface.
INTF_USER - ANSWER: Required profile variable used for associating a user with
interface audit trail entries if no user is present in the message.
Retrigger - ANSWER: Rebuilds the message and sends it out. Similar to Resubmit
except it rebuilds the message instead of sending out a copy.
Field Separator - \F\
Component Separator - \S\
Repetition Separator - \R\
Escape Character - \E\
Subcomponent Separator - \T\ - ANSWER: What are the HL7 message encoding
character escape sequences? (Assume the Escape character is backslash)
Field Separator - |
Component Separator - ^
Repetition Separator - ~
Escape Character - \
Subcomponent Separator - & - ANSWER: What are the conventional values for the
HL7 message encoding characters?
MSH-11 (Processing ID) & MSH-12 (Version) - ANSWER: Which MSH components
does Epic check to see if it should accept/reject an incoming message?
1) Message uses XML framework
2) Connection requires HTTPS
3) Interface uses Windows .NET framework to handle a job (eg, extracting an
embedded PDF from an HL7 v2 message and storing it to a server) - ANSWER: What
are the 3 main use cases for using Interconnect?
Trigger - ANSWER: Serves as the integration point between the application workflow
and Bridges
-generally an action in Hyperspace, like clicking a button or closing an activity
-a single, clearly defined action that a user or process can take that results in an
interface message being created and sent
AND CORRECT ANSWERS(DETAILED ANSWERS)|AGRADE
Event Daemon - ANSWER: Builds HL7 messages based on data pulled from the
database
Control Queue - ANSWER: Maintains a list of messages waiting to be processed
Interconnect - ANSWER: Communicates messages securely using an HTTPS
framework
Chronicles - ANSWER: Contains all the information for a patient in the form of
records
Trigger - ANSWER: Serves as the integration point between the application workflow
and Bridges
Holding Queue - ANSWER: Acts as a waiting area for messages that cannot get a lock
to store information to the database
Data Queue - ANSWER: Contains HL7 messages along with timestamp information
about the message processing
Event - ANSWER: Contains directions for where the interface should pull the
information it needs from the database
Filer Daemon - ANSWER: Translate HL7 data into something that can be stored to the
database
Communication Daemon - ANSWER: Sends or receives acknowledgements over
TCP/IP connection
AIP ID - ANSWER: ID of the Interface Profile
Interface - ANSWER: Name of the Interface. This may be overridden in the Interface
Monitor Definition
Queue - ANSWER: Interface queue number where the messages for the interface are
stored. Typically this is the exact same number as the interface ID
Time Since Last Msg - ANSWER: Elapse time since a message was last sent or
received
Total Recv'd/Sent - ANSWER: Total number of messages sent or received
,Queued Messages - ANSWER: Number of messages waiting to be sent or processed
from the Control Queue
Queued Events - ANSWER: Number of events waiting to be processed from the Event
Queue
Waiting Messages - ANSWER: Number of messages waiting to be processed from the
Holding Queue
Communication Status - ANSWER: Whether the Communication Daemon is Stopped
or Running
Filer/Event Status - ANSWER: Whether the Event Daemon or Filer Daemon is
Stopped or Running
System Purge Default - ANSWER: 30 days
Edit Field - ANSWER: Edit the currently selected field; same effect as double clicking
on a field
Append Field - ANSWER: Append a blank field to the end of the currently selected
segment
Append Multiple Fields - ANSWER: Append several fields to the end of the currently
selected segment; a dialog box allows you to specify the number of fields to append
Edit Segment - ANSWER: Edit the currently selected segment; similar to editing a
field, but you can edit the entire segment at once
Insert Segment - ANSWER: Insert a new segment after the currently selected
segment; a dialog box allows you to specify the segment ID
Delete Segment - ANSWER: Delete the currently selected segment
Restore - ANSWER: Discard all changes you have made to the message and revert to
the original, unedited version
Resubmit - ANSWER: Submit your new copy of the interface message
Event Daemon - ANSWER: Builds HL7 messages based on data pulled from the
database
Control Queue - ANSWER: Maintains a list of messages waiting to be processed
Interconnect - ANSWER: Communicates messages securely using an HTTPS
framework
,Chronicles - ANSWER: Contains all the information for a patient in the form of
records (Epic's patient DB)
Trigger - ANSWER: Serves as the integration point between the application workflow
and Bridges
Holding Queue. The Filer Daemon bounces back and forth between the Holding and
Control/Data Queues. - ANSWER: Acts as a waiting area for messages that cannot get
a lock to store information to the database
Data Queue - ANSWER: Contains HL7 messages along with timestamp information
about the message processing
Event - ANSWER: Contains directions for where the interface should pull the
information it needs from the database
Filer Daemon - ANSWER: Translate HL7 data into something that can be stored to the
database
Communication Daemon - ANSWER: Sends or receives acknowledgements over
TCP/IP connection
AIP ID - ANSWER: ID of the Interface Profile
Queued Messages - ANSWER: Number of messages waiting to be sent or processed
from the Control Queue
Queued Events - ANSWER: Number of events waiting to be processed from the Event
Queue
Waiting Messages - ANSWER: Number of messages waiting to be processed from the
Holding Queue
Filer/Event Status - ANSWER: Whether the Event Daemon or Filer Daemon is
Stopped or Running
30 days - ANSWER: System Purge Default
Resubmit - ANSWER: Submit your new copy of the interface message
It is a note segment and is contextual. - ANSWER: Why is the NTE segment special?
The empty field will be ignored and not file to Chronicles. The delete character will
delete data from Chronicles for that field. - ANSWER: What is the difference between
an empty/null field ( || ) and the delete character ( |""| )?
, False. They are only auto-purged based on configuration (or 30 day default). -
ANSWER: T/F: Messages can be manually deleted from the data queue.
Profile Variable Audit Report - ANSWER: Compares settings of profile variables across
interfaces.
Interface Specification Audit Report - ANSWER: Tracks the changes to a profile
variable within a specific interface.
INTF_USER - ANSWER: Required profile variable used for associating a user with
interface audit trail entries if no user is present in the message.
Retrigger - ANSWER: Rebuilds the message and sends it out. Similar to Resubmit
except it rebuilds the message instead of sending out a copy.
Field Separator - \F\
Component Separator - \S\
Repetition Separator - \R\
Escape Character - \E\
Subcomponent Separator - \T\ - ANSWER: What are the HL7 message encoding
character escape sequences? (Assume the Escape character is backslash)
Field Separator - |
Component Separator - ^
Repetition Separator - ~
Escape Character - \
Subcomponent Separator - & - ANSWER: What are the conventional values for the
HL7 message encoding characters?
MSH-11 (Processing ID) & MSH-12 (Version) - ANSWER: Which MSH components
does Epic check to see if it should accept/reject an incoming message?
1) Message uses XML framework
2) Connection requires HTTPS
3) Interface uses Windows .NET framework to handle a job (eg, extracting an
embedded PDF from an HL7 v2 message and storing it to a server) - ANSWER: What
are the 3 main use cases for using Interconnect?
Trigger - ANSWER: Serves as the integration point between the application workflow
and Bridges
-generally an action in Hyperspace, like clicking a button or closing an activity
-a single, clearly defined action that a user or process can take that results in an
interface message being created and sent
