Epic Bridges 101 Exam Questions and Answers Latest Update 2024-2025 135 Questions and 100% Verified Correct Answers Guaranteed
- Aside from HL7 Version 2, name two other standards supported in Bridges? -
CORRECT ANSWER: X12, FHIR, NCPDP, DICOM, and Direct.
- Does every HL7 message have to be encoded with the characters |^~\& ? -
CORRECT ANSWER: No, the encoding characters can be any printable character.
- Escape the contents of a field that contains an encoding character by replacing it with
the
appropriate escape sequence - CORRECT ANSWER: Make sure you can perform this
task.
2 General use cases for X12 interfaces and FHIR - CORRECT ANSWER: Real-time
eligibility and provider/patient facing apps
- Imagine that your message begins with MSH|^~\&|. How would you encode the string
"The result is positive & has a value of 2.7 x 10^3."? - CORRECT ANSWER: The result is positive \T\ has a value of 2.7 x 10\S\3.
- Perform basic parsing of an HL7 message, such as identifying the contents of a
specific field
or component - CORRECT ANSWER: Make sure you can perform this task.
2 The context of an NTE segment - CORRECT ANSWER: Varies based on segment
- The difference between a null field and the delete character - CORRECT ANSWER:
Null is ignored while delete will remove if allowed
2 The expectations of using Z-segments - CORRECT ANSWER: They have been
defined and coded for within Epic
2 The importance of MSH-11 and MSH-12 - CORRECT ANSWER: Epic will reject
message if invalid
- What is the difference between an empty field || and the delete character |""|? -
CORRECT ANSWER: An empty field is ignored by the interface, whereas the delete
character will delete information from the database, assuming the field in question supports the delete character.
- / 3
2 Which characters may be used as encoding characters - CORRECT ANSWER: Any
printable character
2 Why is the NTE segment special? - CORRECT ANSWER: Context; its meaning
depends on the segment it follows.
3 Are messages ever manually deleted from the Data Queue? - CORRECT ANSWER:
No, never. They are purged only by an automated purge job.
3 Communication Daemon - CORRECT ANSWER: Manages communications for an
interface (all types , e.g., TCP/IP, HTTPS, etc.) and processes messages on the Control Queue.
- Control Queue - CORRECT ANSWER: Essentially just a to-do list of messages in the
Data Queue and contains very little data.
3 Data Queue - CORRECT ANSWER: List of messages with metadata built by the
Event Demon waiting for messages to be sent. Messages are added to the Event Demon and deleted by the Control Demon.
- Describe the flow of messages in and out of Bridges for an interface using a TCP/IP
connection. - CORRECT ANSWER: See diagram on page 3-14
- Describe the flow of messages in and out of Bridges for an interface using
Interconnect. - CORRECT ANSWER: See diagram on page 3-15
3 Event - CORRECT ANSWER: An event consists of a small set of values with the
necessary information to build the message: the patient ID, the patient contact, the type of message, and other additional information.
3 Event Daemon - CORRECT ANSWER: Processes the Event Queue by pulling the
next event off and using the information in the event to build the message (pulling additional data for the message from Chronicles).
The Event Daemon then puts the message, along with some metadata including timestamp information, onto the Data Queue and adds an instruction to the Control Queue.
3 Event Queue - CORRECT ANSWER: List of events waiting for messages to be built
and sent outbound. The Event Queue is managed by the Event Demon.
3 Filer Daemon - CORRECT ANSWER: Filer Daemon pulls an instruction from the
Control Queue, retrieves the corresponding message from the Data Queue, and then attempts to file the message.
- / 3
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.
3 Holding Queue - CORRECT ANSWER: Messages pending the release of locking.
The Filer Daemon checks messages on the Holding Queue periodically to determine whether messages on the Holding Queue are ready to file.
Additionally, 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 added to the Holding Queue.
This ensures that the messages always file into Chronicles in the same order they were received for a patient.
- How information is added to and removed from the Control queue - CORRECT
ANSWER: Messages are added by Event Daemon (outbound), the Comm Daemon
(inbound) or Interconnect (inbound).
Messages are deleted by the Comm Daemon (outbound), the Filer Daemon (inbound).
- How information is added to and removed from the Data queue - CORRECT
ANSWER: Messages are added by the Event Daemon (outbound), the Comm Daemon
(inbound) or Interconnect (inbound).
Messages persist in the Data Queue until they are purged by an automated purge job based on how long they've been in the queue.
- How information is added to and removed from the Event queue - CORRECT
ANSWER: Events are created/added to the queue by triggers.
They are removed from when the Event Daemon after it has built the message and updated both the Data and Control queues.
- How information is added to and removed from the Holding queue - CORRECT
ANSWER: Messages are added by Filer Daemon when locks are present and deleted
by Filer Daemon after the locks have been released.
3 Locked Record - CORRECT ANSWER: A record is locked when a user or process is
updating it. This ensures that two people or processes aren't trying to update the same record at the same time and potentially corrupting the data.
- / 3