HIPAA Accelerator Guide

10.2
- 10.5.3
- 10.5.0
- 10.4.0
- 10.2.3
- 10.2.2
- 10.2.1

Back Next

Inbound Process Overview

The HIPAA file is received at the landing zone. The file can contain no more than one ISA segment, with multiple GS groups and multiple ST transactions.

The HIPAA Accelerator receives the HIPAA file, validates the HIPAA file at the ISA level, generates a TA1 message, and sends the TA1 message to the sender based on the input ISA14 element.

If the file passes ISA level validation, the Accelerator splits the HIPAA file into separate files, for each GS, where each file contains one ISA segment with one GS segment. The GS segment can contain multiple ST segments of the same HIPAA document, such as transaction type 837D.

The Accelerator validates each file with one ISA segment and one GS segment at the GS level. When the "999 Acknowledgment" workflow parameter is enabled (default), the Accelerator creates and sends a 999 message to determine if the file is HIPAA compliant. If there is a validation error, an HTML report with error descriptions will be attached to the event.

If the file is HIPAA compliant, the Accelerator splits the input into files with one ISA segment, one GS segment and one ST segment. The accelerator then parses the files into Informatica HIPAA XML canonical format. For 837I, 837P, 837D, 277CA, and 835, each transaction is split to claims. Information is extracted and added to the event.

Rename Saved Search

Table of Contents

HIPAA Accelerator Guide

HIPAA Accelerator Guide

Inbound Process Overview

Inbound Process Overview