The standard outbound process converts an XML representation of a HIPAA document to a HIPAA-formatted document.
The input document that is sent to the channel may not be in XML format. It can be any input document that should first be converted to the XML representation of the HIPAA document, which is then processed by the channel and transformed to a HIPAA document.
In a basic message flow, outbound 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 Outbound Processing: XML to HIPAA.
Route / Process Flow
Rules processing runs against the XML-formatted HIPAA document to validate its structure and content. The published HIPAA standards and user implementation guides define element types (for example, numeric, alpha, or date) and describe business rules to apply for validation.
The XMLToHIPAATransformationAgent obtains the message type and version from the XML-formatted HIPAA document. The appropriate transformation template is applied from the Ebix. The transformation converts the XML-formatted HIPAA document to HIPAA format.
The XDHIPAAValidationReportAgent creates a report (an XML document) containing the XML-formatted HIPAA document and resulting HIPAA formatted data, as well as the validation status.
If the HIPAA document did not contain any errors during the rules processing stage, it is emitted and continues to its next destination. The validation report is always emitted. In the sample process flow that is described later in this chapter, good validation reports are written with a file name prefix of validation. All other validation reports are written with a file name prefix of error. Information in the error validation reports can be routed accordingly for repair and reprocessing.