Table of Contents

Search

  1. Preface
  2. Transformations
  3. Source transformation
  4. Target transformation
  5. Access Policy transformation
  6. Aggregator transformation
  7. B2B transformation
  8. Chunking transformation
  9. Cleanse transformation
  10. Data Masking transformation
  11. Data Services transformation
  12. Deduplicate transformation
  13. Expression transformation
  14. Filter transformation
  15. Hierarchy Builder transformation
  16. Hierarchy Parser transformation
  17. Hierarchy Processor transformation
  18. Input transformation
  19. Java transformation
  20. Java transformation API reference
  21. Joiner transformation
  22. Labeler transformation
  23. Lookup transformation
  24. Machine Learning transformation
  25. Mapplet transformation
  26. Normalizer transformation
  27. Output transformation
  28. Parse transformation
  29. Python transformation
  30. Rank transformation
  31. Router transformation
  32. Rule Specification transformation
  33. Sequence transformation
  34. Sorter transformation
  35. SQL transformation
  36. Structure Parser transformation
  37. Transaction Control transformation
  38. Union transformation
  39. Vector Embedding transformation
  40. Velocity transformation
  41. Verifier transformation
  42. Web Services transformation

Transformations

Transformations

Data Services transformation

Data Services transformation

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.

0 COMMENTS

We’d like to hear from you!