Filter
Top Products
1. Inbound HL7 V3 Immediate Collaboration
2. Inbound HL7 V3 Deferred Collaboration
3. Inbound HL7 V3 Queue Manager
4. Inbound HL7 V3 Message Publisher
Inbound HL7 V3 Immediate Collaboration Overview
The Inbound HL7 V3 Collaboration, jcdHL7V3Inbound, contains Message Libraries for the
HL7 V3 Resource Adapter, JMS Data, JMS Journal, and JMS Error, as well as the HL7 V3
Patient Administration Domain Interaction Event (PRPA_IN403001UV01) and the
corresponding HL7 V3 Acknowledgements (MCCI_IN000004UV01). The Collaboration
works with its own internal code and the properties conguration les.
Note – Immediate mode contains only one type of Acknowledgement Message Library,
MCCI_IN000004UV01.
The following topics describe the business logic dened in the jcdHL7V3Inbound
Collaboration:
■
“HL7 V3 Standard Inbound Message Mode Data Flow (For Immediate Mode of ACK
Process) — Part 1” on page 122
■
“HL7 V3 Standard Inbound Message Mode Data Flow (For Immediate Mode of ACK
Process) — Part 2” on page 125
HL7 V3 Standard Inbound Message Mode Data Flow (For Immediate
Mode of ACK Process) — Part 1
An HL7 V3 message triggers an inbound Collaboration received from an external system or an
outbound HL7 V3 client. The Collaboration calls the HL7 V3 user Collaboration rule by
executing receive().
The receive 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/IPHL7V3Collaborations
SunAdapterforTCP/IPHL7User's Guide • October2009122