Epic Bridges 101 Exam Questions With Solutions | Latest Verified | Graded A+

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. 3 How informaIon is added to and removed from the Data queue Messages are added by the Event Daemon (outbound), the Comm Daemon (inbound) or Interconnect (inbound). Messages persist in the Data Queue unIl they are purged by an automated purge job based on how long they've been in the queue. 3 How informaIon is added to and removed from the Control queue 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). 3 How informaIon is added to and removed from the Holding queue Messages are added by Filer Daemon when locks are present and deleted by Filer Daemon aner the locks have been released. 3 Message flows with and use cases for Interconnect Outbound: Comm Daemon send to Interconnect and forwarded via HTTPs from there. Inbound: Interconnect receives messages via HTTPs and directly updates the Data Queue and the Control Queue. 4 Can you start more than one interface at a Ime with the interface monitor? Yes. You can start any or all of the interfaces in a given interface monitor. 4 What do you have to do before you can add an interface to an interface monitor definiIon? Make sure that interface is monitored by the Background Monitor. 4 What kinds of alerts can be set up in the Background Monitor? Rules-based alerts. For example, a rule can be configured to check if an interface daemon is on a specific monitor and has been stopped for a specific amount of Ime. Alerts can be used to send an email or even trigger out a page or text message. 4 Which properIes can be used to specify the interfaces evaluated by an alert rule? Interface ID and Is Interface On Monitor 4 Background Monitor Takes care of many tasks including determining whether interfaces are running. You need to add every interface to the background monitor in order to start or stop the interface. 4 Alert Rule Rules for alerIng someone if a problem occurs with an interface. The rules framework allows you to create rules for a specific interface, a list of interfaces or even for all interfaces on a parIcular interface monitor. 4 Threshold Time The length of Ime for which your rule needs to conInuously be true in order for an alert to be sent. You can also specify a Ime in the Repeat Aner column aner which your alert will be sent again if your rule's condiIons remain true. 4 Radar dashboard Provides a centralized locaIon for important reporIng tools and metrics inside Hyperspace. The content of individual dashboards can be personalized. 4 Determine whether an interface is running Path: Epic Tools Interface UIliIes Interface Monitor. Add the interface monitor to your Dashboard and review the CommunicaIon Status column for the CommunicaIons Daemon or the Filer/Event Status column for the Event Daemon (outgoing) or Filer Daemon (incoming) 4 Start and stop interfaces Highlight the Interface within the Interface Monitor and either right click or use the Interface AcIons secIon on the lower right hand side of the form. 4 Create an interface monitor definiIon Path: Epic Admin Interface Admin Interface Monitor DefiniIon to add/update/delete a monitor. 4 Add an interface to the Background Monitor The Background Monitor takes care of many tasks including determining whether interfaces are running. You need to add every interface to the background monitor in order to start or stop the interface. Click on the Alerts tab within the Background Monitor and add your alert rule. Aner adding the alert rule, select the rule to see the AddiIonal Details serngs where you will need to specify a From Address, Email Addresses to NoIfy, and Subject. 4 Create a rule to send an alert To create an alert, edit the Background Monitor and click Alert Rules. This will allow you to create a new rule. Aner the rule is created you will jump to the Rule Editor. The Rule Editor will allow you to create condiIons that are best for your organizaIon. To specify to which interfaces the rule applies, use one of the following properIes: 1. Interface ID - use this property if you would like to list out individual interfaces. 2. Is Interface On Monitor - use this property if you want the rule to apply to all interfaces grouped on an interface monitor. 4 Personalize a Radar dashboard Dashboard - a screen of informaIon that pulls data from mulIple sources into one centralized locaIon for a group of end users. Components - units of content that compose a dashboard. Dashboards present informaIon from mulIple components in one locaIon instead of mulIple acIviIes. Bridges has several released components that you can copy to personalize your dashboard. Some of the key interface components are: 30001-Interface Error Workqueue Summary 30002-Bridges Interface Monitor 30003-Bridges Interface Purge Results 30050-EDI Error Metric Component 5 Message resubmission Resubmirng a message on either an incoming or outgoing interface will create a new message on the Data Queue and also place an entry on the Control Queue. For an incoming interface, this forces the Filer Daemon to reprocess the message that was resubmijed, which allows a user to ajempt to file changes made directly to the message. In an outgoing flow, the Control Queue is aner the Event Daemon, so a message is simply processed by the CommunicaIons Daemon and sent out exactly as it appears when resubmijed. Any changes to the data in Chronicles or to interface configuraIon will not be reflected in the resubmijed message. 5 Message retrigger The Retrigger opIon in the Message Search results window that copies the original event and puts it back on the Event Queue. This event is then processed by the Event Daemon, applying any changes made in Chronicles or through interface configuraIon modificaIons. The Event Daemon will generate a new message that will be put on the Data Queue as well as an instrucIon for the Control Queue for the CommunicaIon Daemon to process. Only outgoing interface messages can be retriggered. Also, resubmijed messages cannot be retriggered because they no longer have an event string to put back on the Event Queue. 5 Message skip Although extremely rare, you might encounter an issue that causes one of the interface daemons to stop unexpectedly. If this occurs it is likely due to one of two causes: There is a major problem going on with the system in general. There is one unique message that the interface is unable to handle. The Skip opIon allows you to solve the second problem of messages being blocked by postponing the first problem of a message not being able to file. This opIon removes the problem message from the Control Queue so it will no longer be considered as a message to be processed and it logs a fatal error indicaIng which user skipped the message. AddiIonally, any messages that have been skipped using this opIon will show a Yes in the Skipped? column of a message search results screen. The skipped message can then be handled later, and you can restart the interface so the rest of the messages aner it can file normally. You can also skip the message from the detailed message report under the Take AcIon on Message secIon of the report. 5 Detailed message report Provides all of the informaIon related to a message in a single locaIon. 5 Edit and resubmit a message from the Message Editor These funcIons are available from the Message Search, Error Log and other screens with message level detail. 5 Run a message search Message Search is on Interface UIliIes. Add various selecIon criteria by tab. 5 Resubmit and edit a message from the Message Search acIvity Use Edit and/or Resubmit acIon bujons from any message level screen. 5 Create your own report definiIons for a message search My Reports/Reports Serngs/Add criteria by date/fields 5 Fine tune your message search for bejer results Can use both HL7 and Bridges Error code specific values 5 Be comfortable with using the Message Editor and Message Search with interfaces that use an XML format Under Message Search Criteria tab, select XML Message Content 5-27 6 What are two acIons you can take on the message associated with an error when running an error log report? Resubmit and retrigger 6 Can you delete a message in the Error Log Report acIvity? No. You can never manually delete a message from the Data Queue with any Bridges acIvity. 6 When encountering an error for the first Ime, what are the three buckets Epic recommends to choose from when determining how to address the error? Fix, Work, or Suppress 6 What are the three addiIonal acIons that only a Workqueue provides compared to the Error Log Report? Add a note, transfer, and release an error. 6 What types of errors should be added to a Workqueue? If the error requires ongoing maintenance and has a defined resoluIon path. It should be an error that can be assigned to a user, and is not already being collected in another workqueue. 6 What build is required to assign error resoluIon steps for a parIcular error? You need to create a group and add one or more steps to it. Finally, you will need to link the group to the interface for a parIcular error. 6 Error Code Each error logged by Bridges includes a discrete numeric error code that allows us to group mulIple occurrences of the same problem. Errors sharing the same error code also include addiIonal informaIon specific to that occurrence of the error. 6 Error Scope