Epic Bridges Exam Prep
1. TriggerServes 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
2. An interface mes- Data about an event (like a patient being
admitted to the hospital) sage contains....
3. MSH-11 and the HL7 processing ID and version; Epic
checks these values on an incoming MSH-12 are... message
and rejects the message if they do not match the expected
values
4. Segment Identifi- Three character code that identifies what
kind of data that segment contains
er
5. PID-5 patient name
6. NTE segment can follow many different segments
7. Z-segment custom segment for a specific implementation
8. Is it necessary No to send emp-
ty fields following
the last valued field?
, Epic Bridges Exam Prep
9. Within a field do Only as many as are valued you need to
send all components?
10. Blank fields... don't file anything
11. Delete character double quotes " "--- tells the receiving
system to delete a piece of info it has
HL7
12. FHIR specifies RESTful exchange method via HTTPs to
access data
13. Other standards X12, FHIR, NCPDP, DICOM, and Direct
supported by Bridges
14. Event (in context small set of values with the necessary info
to build the message: patient ID, patient of outgoing mes-
contact, type of message, and additional info sage flow)
-contains directions for where the interface should pull the
information it needs from the database
15. Queue storage location outside of Chronicles database
structure
16. Event Queue is the Event Daemon procesed by...
17. Daemon (Out- process that runs in the background without
any direct user action going Message Flow)
, Epic Bridges Exam Prep
18. Event Daemon pulls an event off the Event Queue, uses the
information in the event to build the (Outgoing Mes-
message and finally deletes the event from the event queue.
sage Flow)
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
19. contains the full text of the message along with some
additional metadata (i.e. timestamp) about message
processing
Data Queue
(Outgoing Message
Flow)
20. Control Queue a to-do list and contains very little data
(Outgoing Mes- -processed by the Communications
Daemon sage Flow) -maintains a list of messages waiting
to be processed
21. Comm Deamon reads an instruction from the Control Queue
and copies the appropriate message (Outgoing Mes- off the
Data Queue sage Flow)
-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
1. TriggerServes 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
2. An interface mes- Data about an event (like a patient being
admitted to the hospital) sage contains....
3. MSH-11 and the HL7 processing ID and version; Epic
checks these values on an incoming MSH-12 are... message
and rejects the message if they do not match the expected
values
4. Segment Identifi- Three character code that identifies what
kind of data that segment contains
er
5. PID-5 patient name
6. NTE segment can follow many different segments
7. Z-segment custom segment for a specific implementation
8. Is it necessary No to send emp-
ty fields following
the last valued field?
, Epic Bridges Exam Prep
9. Within a field do Only as many as are valued you need to
send all components?
10. Blank fields... don't file anything
11. Delete character double quotes " "--- tells the receiving
system to delete a piece of info it has
HL7
12. FHIR specifies RESTful exchange method via HTTPs to
access data
13. Other standards X12, FHIR, NCPDP, DICOM, and Direct
supported by Bridges
14. Event (in context small set of values with the necessary info
to build the message: patient ID, patient of outgoing mes-
contact, type of message, and additional info sage flow)
-contains directions for where the interface should pull the
information it needs from the database
15. Queue storage location outside of Chronicles database
structure
16. Event Queue is the Event Daemon procesed by...
17. Daemon (Out- process that runs in the background without
any direct user action going Message Flow)
, Epic Bridges Exam Prep
18. Event Daemon pulls an event off the Event Queue, uses the
information in the event to build the (Outgoing Mes-
message and finally deletes the event from the event queue.
sage Flow)
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
19. contains the full text of the message along with some
additional metadata (i.e. timestamp) about message
processing
Data Queue
(Outgoing Message
Flow)
20. Control Queue a to-do list and contains very little data
(Outgoing Mes- -processed by the Communications
Daemon sage Flow) -maintains a list of messages waiting
to be processed
21. Comm Deamon reads an instruction from the Control Queue
and copies the appropriate message (Outgoing Mes- off the
Data Queue sage Flow)
-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
