Epic Bridges Exam Prep (2024) ||
Questions & 100% Accurate
Answers
Conceptial Researchers
, Epic Bridges Exam Prep (2024) ||
Questions & 100% Accurate Answers
When is duplicate prevention performed? - ANSWER - when an incoming interface
that can create patients does not find the patient by ID and ID type
What are the four possible outcomes of patient Identity Duplicate Checking and the
recommended actions for those outcomes? - ANSWER - 1) no match- create a new
patient and file message
2)Low threshold matches- create a new patient and file messages
3) Single high threshold match- file message to existing patient
4) Multiple high threshold matches- log a fatal error
When is patient validation performed? - ANSWER - when any patient-based
incoming interface finds the patient record by ID and ID type
What are the three types of validation an interface can use? - ANSWER - Basic
Validation, Advanced Validation, Identity Duplicate Configuration (IDC)
Which Identity Duplicate Configuration (IDC) threshold is used for patient validation?
- ANSWER - High Threshold
3 methods of migration for Bridges objects - ANSWER - 1) data courier
2) pack/unpack database record utilities
3) manual migration
Data Courier - ANSWER - tool that epic provides to facilitate the migration of objects
between environments
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
-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) - ANSWER - -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) - ANSWER - processed by the Filer
Daemon
Filer Daemon - ANSWER - 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 - ANSWER - 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 - ANSWER - -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
Questions & 100% Accurate
Answers
Conceptial Researchers
, Epic Bridges Exam Prep (2024) ||
Questions & 100% Accurate Answers
When is duplicate prevention performed? - ANSWER - when an incoming interface
that can create patients does not find the patient by ID and ID type
What are the four possible outcomes of patient Identity Duplicate Checking and the
recommended actions for those outcomes? - ANSWER - 1) no match- create a new
patient and file message
2)Low threshold matches- create a new patient and file messages
3) Single high threshold match- file message to existing patient
4) Multiple high threshold matches- log a fatal error
When is patient validation performed? - ANSWER - when any patient-based
incoming interface finds the patient record by ID and ID type
What are the three types of validation an interface can use? - ANSWER - Basic
Validation, Advanced Validation, Identity Duplicate Configuration (IDC)
Which Identity Duplicate Configuration (IDC) threshold is used for patient validation?
- ANSWER - High Threshold
3 methods of migration for Bridges objects - ANSWER - 1) data courier
2) pack/unpack database record utilities
3) manual migration
Data Courier - ANSWER - tool that epic provides to facilitate the migration of objects
between environments
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
-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) - ANSWER - -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) - ANSWER - processed by the Filer
Daemon
Filer Daemon - ANSWER - 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 - ANSWER - 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 - ANSWER - -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
