In Data Integration, use the mapping template called "Process incoming HL7 messages to an FHIR bundle" and configure the mapping.
The mapping template uses Data Services transformations that access pre-built data services from the data services repository to parse HL7 messages, map the XML data to FHIR bundles, and validate the FHIR bundles. 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 HL7 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 HL7 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 HL7 file to construct the name of the data service.
Data services use the following naming convention:
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 (HL7 parser)
The Data Services transformation uses the name of the HL7 parser data service to access the data service in the data services repository. The HL7 parser reads the incoming patient and health information in the HL7 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.
5. Expression transformation
The Expression transformation constructs the name of the FHIR mapper service. It also creates fields for the base URL, bundle type, and event type to construct a FHIR bundle.
6. Data Services transformation (FHIR mapper service)
The Data Services transformation uses the FHIR mapper service in the data services repository to map the HL7 messages in XML format to FHIR bundles in XML format.
7. Data Services transformation (FHIR validation service)
The Data Services transformation uses the FHIR validation service in the data services repository to validate the FHIR bundles.
8. Target transformations
The Target transformations post the FHIR bundles to the FHIR server and include any errors and error flags. To write the data to the FHIR server, you use a FHIR 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.
