A Data Services transformation creates an outputBuffer output field for the messages that it processes. 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. For example, for a HIPAA restricted serialize service, the transformation creates output fields for error reports and for a validation report. If you use the Data Services transformation to validate incoming FHIR resources, the transformation creates output fields only for error reports and for a validation report.

If you use custom messages, configure additional output fields for custom message elements. To pass parameters to the output, create pass-through fields with an Input/Output field type and map them to output fields.

When you add a Target transformation to the mapping, the Data Services transformation maps all the output fields to the Target transformation. To receive the output in different targets, add more Target transformations to the mapping and configure field rules to exclude output fields that you don't want to send to the target. For example, to receive messages and validation reports in two different targets, add two Target transformations to the mapping. Exclude the validation report output fields from the target that receives the messages and exclude the outputBuffer output field from the target that receives the validation reports.