Ifa system does not conform to the HL7 specication, the Collaborations can be modied for
thattransaction by changing the Java code using the Collaboration Editor. The Collaborations
Javacode is designed to be available and “transparent” so you can easily reference the
predenedJava code to see how it currently handles HL7 transactions and make the
appropriatemodications.
TheCollaboration Editor allows you to create and edit Java code to modify a Collaboration for
yourspecic needs. In many cases this code can be created graphically (drag and drop), using
theCollaboration Editor’s Business Rules Designer. If you need to change the code of a prebuilt
Collaboration,you should duplicate the Collaboration rst and then modify it.
TheCollaborations are designed to target one unit of work at a time, meaning the resolution of
onemessage at a time. Once the current message transaction is resolved, the Collaboration is
freeto process the next HL7 message. The general form of the Collaborations is a state machine.
Basedon the state of the connection, the Collaboration performs the appropriate action.
AdditionalCollaborations can be added to a Project to increase message ow.
GenericHL7 Message Libraries
Thegeneric HL7 Message Libraries are version-agnostic structures used to send and receive
HL7messages, acknowledgements, and negative acknowledgements (NAKs). They provide the
Collaborationwith only the essential elds for implementing the HL7 protocol. If you need to
performfunctions that are specic to a version or message type, you can add the appropriate
MessageLibrary to the Collaboration.
SunJava Composite Application Suite Functionality
TheTCP/IP HL7 Adapter takes advantage of the Java CAPS facilities to provide journaling and
errormessaging, as well as monitoring, alerting, and logging. journaling and error messages are
sentto JMS queues, which allow exibility for postprocessing. For example, invalid messages
andtheir negative acknowledgements (NAKs) are sent to a JMS queue. This JMS queue can
thenbe set up to allow the invalid HL7 messages to be viewed, corrected, and resubmitted
automaticallyto the same Adapter.
■ErrorQueues
EachCollaboration automatically sends invalid messages that have incorrect data, have
invalidformatting, or are deemed unacceptable to a JMS error queue. The error generated
bythe message and, if appropriate, its associated NAK, are written as JMS properties of that
messagefor later processing. You can send errors to one common queue, to a specied
queuefor each Adapter, or to a combination of both.
■JournalingQueues
Whenjournaling is enabled, the HL7 message and its related acknowledgement (ACK) are
writtento a JMS journal queue. You determine the number of JMS error queues or journal
queuesused by a Project. From the JMS queue, these messages can be accessed and written
tole, sent to a database, sent to a Web application for processing, and so forth.
SunAdapterfor TCP/IP HL7 Overview
SunAdapterfor TCP/IP HL7 User's Guide 11