Module for HIPAA 9.6.April 2016 | Understanding and Using HIPAA Module | Installing and Using HIPAA Module | Concepts | Process Overview | Receiver-Side Processing
 
Receiver-Side Processing
The following diagram illustrates receiver-side processing when using Trading Networks processing rules.
Receiver-Side Processing
Step
Description
1
Your trading partner creates a client that constructs a HIPAA standard message and sends the HIPAA message to your Integration Server.
2
Integration Server receives the HIPAA message and sends it to Trading Networks for processing. Because the HIPAA message is an EDI document, Trading Networks passes the document to Module for EDI.
The Module for EDI splits the HIPAA message into separate documents. Set a variable in an EDI trading partner agreement (EDITPA) to define the level of documents (Envelope, Group, or Transaction) that you want the HIPAA message split into. For HIPAA processing, you must split at least at the group level to form both Envelope and Group documents. For more information about EDITPAs and the EDITPA splitOption variable, see Configuring the webMethods Module for HIPAA in this guide and also see the webMethods Module for EDI Installation and User’s Guide .
3
Module for HIPAA supports the following TN document types:
*5010 270
*5010 271
*5010 276
*5010 277
*5010 278
*5010 820
*5010 834
*5010 835
*5010 837
*5010 999
For each document (Envelope, Group, or Transaction) split from the original HIPAA message, the Module for EDI uses the TN document types to determine the type of document (for example, X12 Envelope, X12 Group, or X12 5010 835).
After recognizing the type of document using TN document types, the EDI recognizer forms a BizDocEnvelope for the EDI document. The BizDocEnvelope is in the bizdoc pipeline variable. A BizDocEnvelope contains the original document (Envelope, Group, or Transaction) and includes additional information that Trading Networks requires for routing and processing the document. In other words, the BizDocEnvelope represents a routable Trading Networks transaction.
4
After the BizDocEnvelope is formed, the document undergoes regular Trading Networks processing. Trading Networks determines which processing rule to execute on the document. For example, set up processing for the Envelope document to validate the envelope and generate TA1 technical acknowledgments and 997 functional acknowledgments, if appropriate. For more information about defining processing rules, see Before You Can Process Inbound HIPAA Messages.
5
Acknowledgments (for example, 997 and TA1) can be returned to the sender using Trading Networks delivery features. For more information, see the webMethods Trading Networks Administrator’s Guide for your release.
Note:
When a received HIPAA transaction is split, the generated (Envelope, Group, and Transaction) document types are related and displayed in the My webMethods: Monitoring > Integration > B2B > Transactions > Related Documents column but the generated functional (997), implementation (999), and technical (TA1) acknowledgements are not related, by default.