The HL7 Binding Component includes the following features:
HL7 Version Support: Supports HL7 Versions 2.1, 2.2, 2.3, 2.3.1, 2.4, 2.5, 2.5.1, and 2.6.
Design Time WSDL Semantic Validation: Supports WSDL validation at design-time for issues such as attribute values, relationship between extensibility elements, and so forth.
Symmetrical WSDL For Service Definition: Both the service consumer and service provider use the same WSDL in their implementation of extensibility elements hl7:binding, hl7:operation, hl7:message, hl7:address, and hl7:protocolproperties.
Service Orchestration: Business orchestration can specified as a service consumer or service provider.
Lower Layer Protocols: Supports MLLP v1.0, MLLP v2.0, and HLLP Message Transport Protocols.
Transport Protocols: Supports the TCP/IP Transport Protocol.
Acknowledgment Modes: Supports both Original Mode Acknowledgement and Enhanced Mode Acknowledgement.
Message Validation and MSH Segment Validation: Validates messages for syntactical correctness and MSH segment fields for message acceptance.
Accept Acknowledgment Restraint in Enhanced Mode: Checks the payload (MSH.15) of incoming HL7 messages and determines whether an acknowledgment is required.
Journaling and Persistence Support: Supports default Axion database, Derby, MySQL 5.1, and Oracle 11g databases.
HL7 XML Messages Support: Supports processing the XML version of HL7 messages without depending on the HL7 Encoder when the “Literal” option in encoding details section is selected when the HL7 WSDL file is created.
HL7 Recourse Actions: Supports communication controls and recourse actions.
Sequence Number Protocol: Supports sequence number protocol when the binding component is set as a service consumer or service provider in the business orchestration.
Since the HL7 Binding Component uses the Service Unit path as the primary key in the database table, and a Service Unit is a collection of service endpoints, only one sequence number enabled service endpoint is supported for each Service Unit.