The inbound process converts a HIPAA formatted document to an XML document.
In a basic message flow, inbound processing consists of the following components and steps. For an illustration of the components available in the construction of a message flow, see Using a Channel to Construct a Message Flow. You will define the components in the configuration instructions in Sample Configuration for Inbound Processing: HIPAA to XML.
The preparser ensures that the document is converted to a structurally correct HIPAA XML document. The transformation templates that are provided in the Ebix are used to transform the structure of the document.
The iWay Integration Solution for HIPAA ensures the validity of the HIPAA format and content of the XML document. The HIPAA level 1-5 validation tests are performed. The integration solution uses the rules provided in the Ebix for each transaction to apply rules in compliance with the HIPAA implementation guides to ensure that the resulting XML is HIPAA compliant.
For example, here is a typical date segment in an inbound HIPAA document:
The value in DTM01 ("001") is validated against an allowed code list. The value in DTM02 ("20080701") is validated as a properly formatted date.
In addition, the following business rule is applied: DTM02 is required if DTM01 is present (if there is a qualifier, there must be data).
In our basic message flow, the copy service redirects the output document to the destination.
For details on available services, see the iWay Service Manager User's Guide.
Outlets define how messages leave a channel at the end of a process. In our basic sample channel, two outlets are configured: