Industry Solutions for Healthcare

Back Next

Step 3. Configure the mapping

Data Integration

, use the mapping template called "Process incoming X12 HIPAA messages" and configure the mapping.

The mapping template uses a Data Services transformation that accesses a pre-built data service from the data services repository to parse HIPAA messages. You can populate the mapping template with source and target data using the source and target connections that you created.

The following image shows the transformations in the mapping template:

The mapping template contains the following transformations:

1. Source transformation: The Source transformation reads an HIPAA file as a source. You can use a flat file connection, an SFTP connection to a remote server, or a Kafka connection to access the HIPAA data.

The source can be one of the following types:

Single object
File list to process multiple files
Command if the files are stored on the same Linux machine that runs the Secure Agent
Parameter if you want to specify the source in the
mapping
task

The source is parameterized in the mapping template, so you can perform one of the following tasks:

Replace the parameter with a specific connection and source object in the Source transformation.
Leave the parameter in the Source transformation and specify a source in the
mapping
task or use a parameter file.
2. Expression transformation: The Expression transformation uses the data in the HIPAA file to construct the name of the data service.

Data services use the following naming convention:

<industry standard>_<version>_<message type>_<usage type>

For example, HIPAA_5010A1_270_Parser.
3. Filter transformation: The Filter transformation filters the incoming data from the Expression transformation to output only the final name of the data service that the Expression transformation constructs.
4. Data Services transformation to invoke a parser data service: The Data Services transformation uses the name of the HIPAA parser data service to access the data service in the data services repository. The HIPAA parser reads the incoming patient and health information in the HIPAA file and converts the data to XML format.

The mapping template sets the output type to buffer by default. If the output data is larger than the output precision, change the output type from buffer to file to avoid truncating the data.

The input fields include L1_Validation and L2_Validation. You can set the value of these fields to true to generate the corresponding validation reports.
5. Data Services transformation to generate acknowledgements: The Data Services transformation invokes the ACK_999_Generator data service from the data service repository. The acknowledgement generator parses the XML structure that the previous Data Services transformation generated, validates it, and create an acknowledgement message.
6. Target transformations: The Target transformations write the output, validation report, errors, and error flags to the target files. To write the data to the target files, you can use any target connection that writes XML data, such as a flat file or relational connection.

The target is parameterized in the mapping template, so you can perform one of the following tasks:

Replace the parameter with a specific connection and target object in the Target transformation.
Leave the parameter in the Target transformation and specify a target in the
mapping
task or use a parameter file.