How pub.estd.hipaa.receive Handles Other HIPAA Transactions

All HIPAA transactions other than a TA1 technical acknowledgment are treated as regular EDI documents. When the client sends any HIPAA message other than a TA1 technical acknowledgment to Integration Server, the pub.estd.hipaa:receive service invokes the wm.tn:receive service, starting normal Trading Networks processing. Because the HIPAA message is an EDI document, Trading Networks passes the document to the EDI recognizer for processing. For more information about how EDI documents are processed in Trading Networks, see the documentation for Module for EDI.

The following diagram illustrates the processing when a client sends a HIPAA message that is not a TA1 technical acknowledgment to Integration Server. For more information, see the table below the diagram.

Step	Description
1	The client sends the HIPAA message with the content type application/EDIStream to Integration Server, which in turn passes the HIPAA message to the application/EDIStream content handler. The content handler performs initial processing, including forming the pipeline and placing the edidata variable in the pipeline. The edidata variable contains the HIPAA message data.
2	The content handler invokes the service specified by the client. For a HIPAA message, this should be the pub.estd.hipaa:receive service. The pub.estd.hipaa:receive service determines that the HIPAA message is not a TA1 technical acknowledgment, and therefore, invokes only the wm.tn:receive service.
3	The wm.tn:receive service is the start of normal Trading Networks processing. Because the variable, edidata, is in the pipeline, Trading Networks passes the document to the EDI recognizer for EDI specific handling.