Questions and CORRECT Answers
MSH-11 and MSH-12 are... - CORRECT 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.
Do all fields in Epic interfaces support deletion? - CORRECT ANSWER - No
Subcomponent - CORRECT ANSWER - The most discrete separator, which divides
information within an individual component. \T\
Repetition - CORRECT ANSWER - Used when there are multiple values to convey for
one kind of information, such as a patient with two different phone numbers. \R\
Escape - CORRECT ANSWER - Allows encoding characters to be indicated as textual
information and not as separators. \E\
Field - CORRECT ANSWER - The way to break a segment into discrete data elements
like provider or department. \F\
Component - CORRECT ANSWER - Allows multiple pieces for one concept to be
separated within a field, such as first name and last name \S\
True or False: Every HL7 message has to be encoded with the characters |^~\& - CORRECT
ANSWER - False. Any printable ASCII characters can serve as encoding characters.
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.
, What makes the NTE segment special? - CORRECT ANSWER - It is context-based
True or False: An incoming interface will treat an empty field || differently than |""|. - CORRECT
ANSWER - True. The interface treats |""| as a deletion indicator and ignores an empty
field.
Which standards are supported in Bridges? - CORRECT ANSWER - FHIR, NCPDP, HL7
v2, HL7 v3, and X12
Queue - CORRECT ANSWER - List of information
Daemon - CORRECT ANSWER - Background process that continually performs a
specific job.
Trigger - CORRECT ANSWER - Link between an action that a user or process takes and
an interface message being created. A trigger is generally an action in Hyperspace, like clicking
a button or closing an activity.
Outbound Message Flow - CORRECT ANSWER - Trigger->Event Queue->Event
Daemon(Grabbing from Chronicles)->Data + Control Queue->Comm Daemon->TCP/IP or other
connection.
Event Queue - CORRECT ANSWER - List of events triggered. An event consists of a
small set of information, just enough to find the data in Chronicles needed to build the message.
Event Daemon - CORRECT ANSWER - Processes the Event Queue by reading the next
event 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 and event string, onto the Data Queue and adds the message
number to the Control Queue.