You can use a mapping template instead of creating a mapping from scratch.
Mapping templates are divided into the categories: Integration, Cleansing, Warehousing, and Industry Solutions.
The following image shows some of the mapping templates in the New Asset dialog box:
When you select a mapping template in the New Asset dialog box, you create a mapping that uses a copy of the mapping template.
The template mapping contains pre-populated transformations. Click on each of the transformations in the mapping to see the purpose of the transformation, how the transformation is configured, and which parameters are used.
The following image shows the Augment data with Lookup template with the Source transformation selected. The Description field shows how the Source transformation is configured:
You can use a mapping template as is or you can reconfigure the mapping. For example, the Augment data with Lookup template uses the p_scr_conn parameter for the source connection. You can use the parameter to specify a different connection each time you run the mapping task that uses this mapping. You might want to use the same source connection every time you run the mapping task. You can replace the parameter p_scr_conn with a specific connection, as shown in the following image:
When you save the mapping, you save a copy of the template. You do not modify the template itself.
You can copy a template mapping to advanced mode. Mapping templates don't apply to mappings in SQL ELT mode.
Industry solutions templates
Use an industry solutions mapping template to create a mapping that processes incoming EDI, HL7, or HIPAA messages. The templates are pre-configured to use industry solutions data services to process your incoming messages.
The Industry Solutions category includes mapping templates for the following scenarios:
•Process incoming EDI X12 messages
•Process incoming HL7 messages
•Process incoming HL7 messages from a Kafka source
•Process incoming HL7 messages to a FHIR bundle
•Process incoming HIPAA X12 messages
Each template includes a pre-configured Expression transformation that extracts fields from your incoming messages and uses them to build the data service name according to the message type and version. It then passes the names to the Data Services transformation. The Expression transformation allows you to use a single mapping to process all of your incoming EDI, HL7, or HIPAA messages.
The Data Services transformation invokes data services from the data services repository. The data services parse the incoming messages and output an XML structure that represents the parsed messages.
Process incoming HL7 messages to a FHIR bundle
Use a mapping template instead of creating a mapping from scratch to process incoming HL7 messages and transform them into a FHIR-R4 bundle in XML format.
The template includes a Data Services transformation that invokes the HL7-FHIR mapper service. The mapper service maps HL7 message components to corresponding FHIR message components. The mapping between components is based on HL7 v2.6, and FHIR version 4.0.1. The resulting bundle is a collection of related FHIR resources. The template does not include the FHIR provenance resource.
Note: The FHIR standard is continuously developing. This template is based on the HL7 V2 to FHIR mapping implementation available as of the April 2023 release of Data Integration. Messages, segments, fields, data types, or code sets that you use may not be available. As new versions of FHIR are released, this template might be updated to reflect additional HL7 to FHIR mappings.
