1. InboundHL7 V3 Immediate Collaboration
2. InboundHL7 V3 Deferred Collaboration
3. InboundHL7 V3 Queue Manager
4. InboundHL7 V3 Message Publisher
Inbound HL7V3 Immediate Collaboration Overview
TheInbound HL7 V3 Collaboration, jcdHL7V3Inbound, contains Message Libraries for the
HL7V3 Resource Adapter, JMS Data, JMS Journal, and JMS Error, as well as the HL7 V3
PatientAdministration Domain Interaction Event (PRPA_IN403001UV01)and the
correspondingHL7 V3 Acknowledgements (MCCI_IN000004UV01). The Collaboration
workswith its own internal code and the properties conguration les.
Note– Immediate mode contains only one type of Acknowledgement Message Library,
MCCI_IN000004UV01.
Thefollowing topics describe the business logic dened in the jcdHL7V3Inbound
Collaboration:
■“HL7V3 Standard Inbound Message Mode Data Flow (For Immediate Modeof ACK
Process)— Part 1” on page 122
■“HL7V3 Standard Inbound Message Mode Data Flow (For Immediate Modeof ACK
Process)— Part 2” on page 125

HL7V3 Standard Inbound Message Mode Data Flow (For Immediate

Modeof ACK Process) — Part 1

AnHL7 V3 message triggers an inbound Collaboration received from an external system or an
outboundHL7 V3 client. The Collaboration calls the HL7 V3 user Collaboration rule by
executingreceive().
Thereceive method is the entry point to the HL7 V3 User Collaboration, with the following
signature:
public void
receive(com.stc.connector.appconn.tcpip.hl7.HL7ServerApplication input,
com.stc.connectors.jms.JMS otdJMS_DATA,
xsd.hl7v3.PRPA_IN403001UV01.PRPA_IN403001UV01_ otd_PRPA_IN403001UV01_1
xsd.hl7v3.MCCI_IN000004UV01.MCCI_IN000004UV01_ otd_MCCI_IN000004UV01
otdHL7_ACK_1,com.stc.connectors.jms.JMS otdJMS_JOURNAL,
com.stc.connectors.jms.JMS otdJMS_ERROR) throws Throwable.
AboutTCP/IPHL7 V3 Collaborations
SunAdapterfor TCP/IP HL7 User's Guide •October 2009122