HL7v3-based components do not mandate any special data model. Web Service metadata (WSDL documens) reflects
this by declaring all message parts to be
What the components deliver to a Camel route, is always an HL7 v3 message as String. Groovy DSL extensions for XML processing can be efficiently used to handle and prepare request and response messages.
In addition, starting with the version 4.1.0, IPF introduces model classes for request and response messages of selected HL7v3 transactions (ongoing work), as well as Camel type converters for transforming instances of these classes into Strings and back again. Currently, the following model classes are available:
What the components expect to obtain from a Camel route (e.g. outgoing requests on producer side and outgoing responses on consumer side) is an XML String containing an HL7 v3 message, or something that can be transformed into such String by the means of Camel type converters — e.g. byte array, input stream, stream reader, DOM document, XSLT source, model class instance, etc.