Epic Bridges 101 Final Exam Questions With Verified Solutions - RATED 100%

What are stored in the Control Queue? The Control Queue is a to-do list with instrucIons to send or file messages stored in the Data Queue. 3 Are messages ever manually deleted from the Data Queue? No, never. They are purged only by an automated purge job. 3 What are two ways that interface messages are sent and received? TCP/IP with an interface engine is the most common communicaIon method. Interconnect is used for HTTPS or other communicaIon outside your local network. 3 Describe the flow of messages in and out of Bridges for an interface using a TCP/IP connecIon. See diagram on page 3-14 3 Describe the flow of messages in and out of Bridges for an interface using Interconnect. See diagram on page 3-15 3 Trigger A trigger is a single, clearly defined acIon that a user or process can take that can result in an interface message being created and sent. A trigger is generally an acIon in Hyperspace, like clicking a bujon or closing an acIvity. 3 Event An event consists of a small set of values with the necessary informaIon to build the message: the paIent ID, the paIent contact, the type of message, and other addiIonal informaIon. 3 Event Queue List of events waiIng for messages to be built and sent outbound. The Event Queue is managed by the Event Demon. 3 Data Queue List of messages with metadata built by the Event Demon waiIng for messages to be sent. Messages are added to the Event Demon and deleted by the Control Demon. 3 Control Queue EssenIally just a to-do list of messages in the Data Queue and contains very lijle data. 3 Event Daemon Processes the Event Queue by pulling the next event off and using the informaIon in the event to build the message (pulling addiIonal data for the message from Chronicles). The Event Daemon then puts the message, along with some metadata including Imestamp informaIon, onto the Data Queue and adds an instrucIon to the Control Queue. 3 Filer Daemon Filer Daemon pulls an instrucIon from the Control Queue, retrieves the corresponding message from the Data Queue, and then ajempts to file the message. Filing means that the Filer Daemon ajempts 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 CommunicaIon Daemon Manages communicaIons for an interface (all types , e.g., TCP/IP, HTTPS, etc.) and processes messages on the Control Queue. 3 Locked Record A record is locked when a user or process is updaIng it. This ensures that two people or processes aren't trying to update the same record at the same Ime and potenIally corrupIng the data. Epic supports parIal paIent locking so that only porIons of the paIent record need to be locked in order to file a message. For example, a lock on paIent demographics would not prevent a result from filing. 3 Message flows in and out of Bridges with TCP/IP See diagrams on 3-14 and 3-15 3 Resequencing using the Holding Queue If a Filer Daemon ajempts to file a message for a paIent, but that paIent's record is already being updated with an acIve lock, then the Filer Daemon stores the instrucIon for that message on another queue, the Holding Queue. The message remains on the Holding Queue unIl the lock is released, so that the Filer Daemon can move onto the next message in the Control Queue for processing. 3 Holding Queue 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. AddiIonally, 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 paIent. 3 What is stored in each of the queues Queues are: Event - List of events waiIng for messages to be built and sent outbound. Data - List of messages with metadata built waiIng for messages to be sent. Control - EssenIally just a to-do list of messages in the Data Queue and contains very lijle data. Holding - Messages pending the release of locking. 3 How informaIon is added to and removed from the Event queue Events are created/added to the queue by triggers. They are removed from when the Event Daemon aner it has built the message and updated both the Data and Control queues.