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 properties

Data Services properties

Configure data services properties to define the input and output types, the data services that the transformation invokes, and the status tracing level on the
Data Services
tab.
Configure the following properties:
Property
Description
Input Type
Type of input that the Data Services transformation receives from the upstream transformation. Select one of the following options:
  • Buffer. The Data Services transformation receives source data in the inputBuffer input field.
  • File. The Data Services transformation receives a source file path in the inputBuffer input field.
Default is Buffer.
Output Type
Type of output that the transformation passes on to the downstream transformation. Select one of the following options:
  • Buffer. The Data Services transformation passes the data to the outputBuffer output field.
  • File. The Data Services transformation writes the output to the outputBuffer output field as an output.xml file.
Default is Buffer.
Service Type
Type of service that the Data Services transformation uses. Select one of the following options:
  • Data Services. The transformation uses the parser, serializer, and restricted serializer data services in the data services repository.
  • FHIR Validation. The transformation uses a built-in FHIR validation service to validate incoming FHIR bundles and messages in XML or JSON format. You can configure the FHIR version and the terminology server.
  • Hierarchical Mapper. The transformation uses a hierarchical mapper to convert hierarchical input to hierarchical output, such as the XML output from a parser data service to a target XSD file.
Service Name
Select a data service from the data services that reside in the data services repository. Choose this option for a mapping that processes a single message type for a specific standard and usage type.
Click
Populate Fields
to automatically populate the input and output fields based on the data service.
Applies when the service type is
Data Services
and you don't use a dynamic service name.
Dynamic Service Name
Select this option to pass service names to the downstream transformation as parameters. Choose this option for a mapping that processes messages for multiple message types from different standards and usage types.
Applies when the service type is
Data Services
.
Message Discovery Service
Select this option to enable the Message Discovery Service to detect the name of a parser data service.
Applies when
Dynamic Service Name
is enabled.
Mode
Select the environment that the data service runs in. The environment can be either development or production.
Applies when
Message Discovery Service
is enabled.
Type
Select the data service type. The type can be either custom or out-of-the-box. Custom data services are services that you customize and upload to the data services repository. Out-of-the-box data services are services that are available in the data services repository by default.
Applies when
Message Discovery Service
is enabled.
Operation
Operation that the data service performs. By default, the transformation uses a parser data service.
Applies when
Message Discovery Service
is enabled.
Status Tracing Level
Detail level of job status that the Data Services transformation writes to output fields. Select one of the following options:
  • None. The transformation doesn't write the status to output fields. You can view the information in the job the session log.
  • Description only. The transformation writes a status code and a short description to the UDT_Status_Code output field.
  • Full status (XML). The transformation writes a status code to the UDT_Status_Code output field and a detailed XML status message to the UDT_Status_Mesage output field.
Default is none.
Applies when the service type is
Data Services
or
Hierarchical Mapper
.
FHIR Version
FHIR version that the FHIR validation service uses to validate FHIR bundles and messages.
Applies when the service type is
FHIR Validation
.
Terminology Server
URL to the terminology server that the FHIR validation service uses to validate FHIR bundles and messages. If you leave the field blank or the value is n/a, the transformation doesn't use a terminology server to validate the resources.
Applies when the service type is
FHIR Validation
.
Hierarchical Mapper
Hierarchical mapper that the transformation uses to convert hierarchical input to hierarchical output.
Applies when the service type is
Hierarchical Mapper
.

0 COMMENTS

We’d like to hear from you!