Use the Data Services transformation to invoke data services from the data services repository, including industry-standard services, such as HL7 and HIPAA, and customized services. For example, you can use the transformation to invoke data services to process HIPAA messages that you exchange with your healthcare partners.
By default, the data services repository includes out-of-the-box data services that process industry standards. You can create customized services in the data services repository and use the Data Services transformation to invoke them, as well. For more information about the data services and the data services repository, see Data Services Repository in the Administrator help.
When you add the transformation to a mapping, you define the data services that the transformation invokes. You can choose one of the following options:
•Use a single data service to process a single message type for a specific standard and a specific usage type. For HIPAA messages, you can also select a data service that sends messages and validation messages to your partners.
•Use a dynamic service name to process messages for multiple message types from different standards and usage types. When you use a dynamic service name, you pass the data service names to the transformation as parameters.
The Data Services transformation passes message data to the downstream transformation in a file or as a buffer, based on your selection. The transformation might create additional output fields, based on the status tracing level that you select for the transformation and on the data service usage type. You can add more Target transformations to the mapping and configure the Data Services transformation to send different output types to different targets. For example, send message data to one target and send status tracing reports to another target.