





















Study with the several resources on Docsity
Earn points by helping other students or get them with a premium plan
Prepare for your exams
Study with the several resources on Docsity
Earn points to download
Earn points by helping other students or get them with a premium plan
A comprehensive overview of the various components and processes involved in managing interfaces within the epic healthcare system. It delves into the different types of errors that can occur during interface communication, the steps to resolve them, and the tools available for monitoring and troubleshooting. Topics such as the event queue, data queue, control queue, comm daemon, filer daemon, interconnect, and chronicles, as well as the different levels of error logging and the actions that can be taken to address them. It also discusses the interface monitor, which allows users to track the status and performance of their interfaces. This document would be particularly useful for healthcare it professionals, epic system administrators, and anyone involved in the management and maintenance of epic interfaces.
Typology: Exams
1 / 29
This page cannot be seen from the preview
Don't miss anything!






















Quiz :Trigger - Answer : Serves 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 Quiz :An interface message contains.... - Answer : Data about an event (like a patient being admitted to the hospital) Quiz :MSH-11 and MSH-12 are... - Answer : the HL7 processing ID and version; Epic checks these values on an incoming message and rejects the message if they do not match the expected values Quiz :Segment Identifier - Answer : Three character code that identifies what kind of data that segment contains Quiz :PID-5 - Answer : patient name Quiz :NTE segment - Answer : can follow many different segments Quiz :Z-segment - Answer : custom segment for a specific implementation
Quiz :Is it necessary to send empty fields following the last valued field? - Answer : No Quiz :Within a field do you need to send all components? - Answer : Only as many as are valued Quiz :Blank fields... - Answer : don't file anything Quiz :Delete character HL7 - Answer : double quotes " "--- tells the receiving system to delete a piece of info it has Quiz :FHIR - Answer : specifies RESTful exchange method via HTTPs to access data Quiz :Other standards supported by Bridges - Answer : X12, FHIR, NCPDP, DICOM, and Direct Quiz :Event (in context of outgoing message flow) - Answer : small set of values with the necessary info to build the message: patient ID, patient contact, type of message, and additional info -contains directions for where the interface should pull the information it needs from the database Quiz :Queue - Answer : storage location outside of Chronicles database structure Quiz :Event Queue is procesed by... - Answer : the Event Daemon
-sends or receives acknowledgments over a TCP/IP connection Quiz :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 Quiz :Control Queue (Incoming Message Flow) - Answer : processed by the Filer Daemon Quiz :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
Quiz :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
-constantly listening for messages coming into the system -most incoming interconnect interfaces don't require a separate Comm Daemon, since the Interconnect server handles all of the communication in this direction. Quiz :Chronicles - Answer : contains all the information for a patient in the form of records Quiz :What are stored in the Event Queue, Data Queue, and Control Queue? - Answer : Event Queue: info needed to build a message (i.e. patient ID, encounter date, type of message, etc.) Data Queue: text of HL7 message and additional metadata Control Queue: to-do list with instructions to send or file messages stored in the Data Queue Quiz :What are two ways that interface messages are sent and received - Answer : TCP/IP with an interface engine is the most common. Interconnect is used for HTTPS or other communication outside your local network Quiz :What does it mean for an interface to process a message? - Answer : the incoming interface's Filer Daemon tries to find the correct patient and file the data in the message into Chronicles the outgoing interface's Event Daemon creates an HL7 message, based on information in Chronicles, and sends it out through the port defined in the Comm Daemon.
Quiz :Are messages ever manually deleted from the Data Queue? - Answer : No, never. They are purged only by an automated purge job. Quiz :Communication Status (Interface Monitor Column) - Answer : whether the comm daemon is stopped or running Quiz :Total Recv'd/Sent (Interface Monitor Column) - Answer : total number of messages sent (outgoing) or received (incoming) i.e. count Quiz :Last Recv'd/Sent (Interface Monitor Column) - Answer : Number of the Last message sent (outgoing) or received (incoming) i.e. message number Quiz :Time since last message( Interface Monitor Column) - Answer : Elapsed time since a message was last sent (for an outgoing interface) or received (for an incoming interface) Quiz :Queued Messages (Interface Monitor Column) - Answer : number of messages waiting to be sent (outgoing) or processed (incoming) Quiz :Queued Events (Interface Monitor Column) - Answer : number of events waiting to be processed from the Event Queue (outgoing only) Quiz :Waiting Messages (Interface Monitor Column) - Answer : Number of messages waiting to be processed from the Holding Queue
Quiz :Rule Editor - Answer : allows you to create conditions that are best for your organization. Also contains an alert email message section to configure what text is included in the body of the email sent for the alert. Quiz :Three options for starting interfaces after planned downtime - Answer :
-marks any errors on the original message as resolved. If an error still holds true on an incoming message, then a new instance of that error will be logged on the new message as it is processed by the Filer Daemon Quiz :Resubmitting an Outgoing message - Answer : sends the message directly out the Communications Daemon, and no additional validation is done on the message content. If a problem still exists on an outgoing message the error on the original message will be marked as resolved, but a new error will not reappear on the new message Quiz :Resubmit feature - Answer : submits your new copy of the interface message Quiz :Message Search - Answer : allows you to specify an interface, a string to look for, and a time period. The activity then returns all messages that match that criteria -allows you to take action on messages that are returned in your search: edit, resubmit, save search path: epic>tools>interface utilities>message search Quiz :Reasons to search for messages - Answer : - if there is an error on a message for a patient -if there is a problem with a given procedure
Quiz :Detailed Message Report - Answer : provides all the information related to a message in a single location -can also be viewed in the bottom report pane of the Message Search results -there are many links DMR to perform actions or jump to records, including the table associated with a table mapping error, or the patient to which the message is associated Quiz :How to get the most out of Message Search - Answer : - limit the time period of your search to as small of a window as possible -use unique identifiers like MRN, CSN, or order ID for your message content criteria as opposed to non-unique values like patient name -include multiple search values to limit your results even further Quiz :Reasons why an interface daemon might stop unexpectedly - Answer :
Any changes to the data in Chronicles or to interface configuration will not be reflected in the resubmitted message Quiz :Retriggering Messages - Answer : - copies the original event and puts it back on the event queue. -the event is then processed by the event daemon, applying any changes made in Chronicles or through interface configuration modifications -the event daemon will generate a new message that will be put on the data queue as well as an instruction for the control queue for the communications daemon to process -only outgoing interface messages can be retriggered Quiz :Can resubmitted messages be retriggered? - Answer : No because they no longer have an event string to put pack on the event queue Quiz :XML Bridges Utilities - Answer : The following bridges utilities also support interfaces that use an XML message structure: -message search -message viewer -message editor Quiz :Does the message editor perform validation to ensure that the value entered is appropriate? - Answer : No. The message editor is a free text editor. It has no idea how the message should look Quiz :In message viewer, what information is available besides the text of the message? - Answer : You can see errors associated with that message, message submission details such as timestamps of when the message was added to the data queue and processed
Quiz :Are you deleting a message from the data queue with the Skip message feature? - Answer : No. You can never manually delete a message with any bridges utility. This utility removes the entry only from the Control Queue Quiz :If you are running a message search, what best practices could you use to reduce the amount of messages returned by your search or finish your search quicker? - Answer : -limit the time period searched -search for unique identifiers (CSN, MRN, order ID) as opposed to patient name -include multiple search values in your search criteria Quiz :Bridges Error Codes - Answer : Each error logged by bridges includes a discrete numeric error code that allows us to group multiple occurrences of the same problem Errors sharing the same error code also include additional information specific to the occurrence of that error Quiz :Bridges Error Severities - Answer : Epic supports five error severities: critical, fatal, warning, notification, and none Quiz :Critical error - Answer : indicates that the problem is serious enough to prevent the content from being processed Quiz :Fatal error - Answer : indicates that the problem is serious enough to prevent the content from being processed Quiz :Notification error - Answer : presents information that might be of interest; logs an error but content is still processed Quiz :Warning error - Answer : something went wrong, but not enough to prevent content from being processed
Quiz :"Fix" errors - Answer : problems that can be eliminated by a change to the system to permanently elimnate the problem Quiz :"Suppress" errors - Answer : some errors are benign and require no further action, so those you can simply suppress Quiz :"Work" errors - Answer : errors you expect to happen periodically and will require manual intervention as part of the ongoing maintenance of the interface Quiz :Possible steps one might take to resolve a "Fix" or "Work" error - Answer : -correct a data mapping issue within Epic -resubmit or retrigger the message in Bridges -edit the message content in Bridges and then resubmit it -update a value or setting in the sending system and retrigger the message to Epic -change the handling of messages in your interface engine -manually change a data value in Chronicles -search for messages filed to the same patient Quiz :Deleting an Error - Answer : marks the error as resolved; happens if: you already made a change in the system to correct the issue, the error is innocuous -a later message has filed and rendered the message with the error obsolete Quiz :Deleted error - Answer : still exists in a resolved state
can always access details about the error in Bridges, so long as the corresponding message exists in the Data Queue Quiz :Error Workqueues - Answer : tool for managing and assigning errors that fall into the ongoing maintenance category -each wq has a list of rules that describes the kinds of errors it should collect -whenever an interface logs an error that meets one of those rules, the error is automatically assigned to that wq -proactively collects all errors that meet criteria from pre-built rules path: epic>tools>interface utilities>workqueue list Quiz :Collect an error workqueue if: - Answer : 1) the error has a defined resolution path